StoryFirst seen
Engineers moved legacy Exchange systems to Azure in a forward fix, which slowed recovery.
Everything it touches
2 names 1 voices 1 source posts
The story’s neighborhood
Explore the graph, or choose a connection below.
Follow the evidence
This brief comes from Tech Twitter’s edited headlines. The posts below are the sources grouped with the story; statements in them belong to their authors.
After 20 hours, the outage finally being mitigated Talking with Microsoft devs, the issue was NOT DNS (like many guessed), but it WAS networking I'm told the fix took so long because it had to be a forward fix... moving stuff from the legacy Exchange system over to... 🥁 ...drumrol... 🥁 Azure!! (impressive)Read original on X
Microsoft outage was networking, not DNS, and took 20 hours to fix
Microsoft outage was networking, not DNS, and took 20 hours to fix
Microsoft Outlook outage was networking, took 20 hours to fix, sources say
Microsoft says Outlook outage was networking, took 20 hours to fix
Microsoft says Outlook outage was networking, not DNS, and took 20 hours
Microsoft says 20-hour Outlook outage was networking, not DNS
Microsoft says 20-hour outage stemmed from networking, not DNS
Shared connections
The two-seat robotaxi requires the ongoing self-driving subscription to operate, bringing its effective hourly cost below $10.
Idle apps cost close to nothing, so teams can build many internal dashboards on the same cloud machine as their code.
Shares rose more than 15% after hours, showing investor reaction to the quarterly results and the cloud partnership.
The chipmaker says its own systems show no sign of compromise while it investigates the leak.