On a Thursday in November, Microsoft's cloud began to falter across the world, and the mail, meetings, and assistants that millions rely on to organise their working lives stopped answering as they should. The company, after hours of trying to repair what it had called a surge of demand on part of its infrastructure, admitted that its repairs were not taking hold. It is a reminder, in an age when our correspondence and our colleagues live on distant servers, of how thin the thread can be between a routine morning and a silent screen. For now, the restoration of that connection remains a matter
Microsoft Says Outlook Outage Fixes Are Not Going 'As Expected' as Global Services Stay Down
Microsoft confirmed its first fix was not taking as expected
Mark
Microsoft says its fix isn't working. What does that actually tell us?
Mimi
That the first attempt to ease the strain on its infrastructure didn't take. The company said it confirmed the changes weren't taking as expected, and is now looking for alternate workstreams to add capacity.
Luke
Worth noting that's all we have. The cause is Microsoft's own description: elevated load. No independent confirmation of why the load rose.
Mark
And the scale? It went global quickly.
Mimi
Downdetector counted 74 countries and territories within an hour. That's a tracker's figure, based on user reports.
Luke
Right, so it shows reach, not the number of people affected. We don't have that.
Mark
Teams seems to have behaved oddly.
Mimi
Yes. Some people couldn't make or receive calls, while scheduled meetings still ran. Microsoft said core Teams functions were fine, but anything depending on Exchange Online was failing.
Luke
Which is why individual experiences differ so much. Someone saying it works for them isn't contradicting someone saying it's down.
Mark
What's the part people might overlook?
Mimi
Safe Links in Defender may be unable to verify URLs. That's a security function, not just an inconvenience.
Luke
And the big unknown is when it ends. Microsoft hasn't said.
El Pulso
- Microsoft's first repairs failed to take hold, and the company now admits it has no firm date for full restoration.
- Within an hour the outage spread to 74 countries, stranding email, calendars, and Teams users at once.
- Impact is uneven: some Teams calls fail while scheduled meetings go ahead, and colleagues see different realities on the same day.
- Schools, administrators, and security tools are caught in the fallout, with students unable to reach assignments and Safe Links unable to verify URLs.
- Engineers are searching for alternate capacity, and the next update will reveal whether that new approach succeeds where the first failed.
On a Thursday in November, Microsoft's cloud began to falter across the world, and the mail, meetings, and assistants that millions rely on to organise their working lives stopped answering as they should. The company, after hours of trying to repair what it had called a surge of demand on part of its infrastructure, admitted that its repairs were not taking hold. It is a reminder, in an age when our correspondence and our colleagues live on distant servers, of how thin the thread can be between a routine morning and a silent screen. For now, the restoration of that connection remains a matter of time that no one has yet been able to name.
On Thursday, Microsoft told its users that the repairs it had been making to a sprawling outage were not working as intended. The company said the changes it had applied to improve service were not taking effect as expected, and that it was now looking for alternate ways to increase capacity. It offered no date for when things would return to normal.
The disruption had already dragged on for hours. Microsoft blamed elevated load on part of its infrastructure, which it said was producing connectivity errors. Within an hour the problem had become global, with the outage tracker Downdetector reporting Microsoft products down in 74 countries and territories.
Outlook was the most visible casualty, but the damage ran deeper. Because so many Microsoft 365 services depend on Exchange Online, which carries email, calendars, contacts, and tasks, the failure rippled outward. Teams behaved unpredictably: some people could not place or receive calls, while planned meetings continued. Social media told the same story in fragments, with some workers still using their apps and others unable to open their inboxes.
The effects reached administrators, students, and AI tools too. Admin pages, recent files, education features such as Assignments, and Copilot's chat and work-material functions were all reported as unreliable. Security was affected as well, as Defender's Safe Links may have been unable to check web addresses.
The central question now is how long this will last. Microsoft has admitted its first fix fell short and has promised no timeline, so the next update will show whether its new approach can restore service.
On Thursday, Microsoft told its users that the repairs it had been making to a sprawling outage were not working. Writing on X, the company said it had monitored the changes it applied to improve serviceability and confirmed they were not taking as expected. It added that it was identifying alternate workstreams to increase capacity, but it did not say when service would be fully restored.
The disruption had already run for hours. Microsoft attributed it to elevated load on a portion of its infrastructure, which it said was likely contributing to connectivity errors. Within an hour of starting, the problem had gone global: the outage tracker Downdetector reported that Microsoft products were knocked out in 74 countries and territories.
Outlook was the headline casualty, but the trouble reached well beyond it. Microsoft said users might be unable to connect to multiple Microsoft 365 services, particularly those that interact with Exchange Online, the cloud-based messaging platform that handles email, calendars, contacts, and tasks for its users.
The experience on Microsoft Teams was split. Some users could not make or receive calls at all, while others found that meetings scheduled in advance went ahead as planned. Microsoft updated its website to say that most core Teams functionality was unaffected, but that tasks depending on Exchange Online were failing. Social media posts echoed the unevenness: some people said they could still use Microsoft apps at work, while others could not even view their email.
The list of affected services shows how far the effects spread. With the Microsoft 365 Admin Center affected, administrators might be unable to load key pages. With Apps down, many users could not see their recent files. In Microsoft 365 Education, students and teachers might be unable to use Assignments, Reading Progress, and Speaker Progress. Users of Microsoft 365 Copilot could have trouble loading Copilot Chat or getting responses in web and desktop apps, and using Copilot to reach work materials might be difficult.
Security tools were hit too. Microsoft said that with Defender for Office 365 not functioning as intended, Safe Links might be unable to verify URLs.
What remains open is the timeline. Microsoft has acknowledged that its first fix did not work and says it is looking for other ways to add capacity, but it has offered no restoration estimate. The next update from the company will show whether those alternate workstreams do what the first set of changes did not.
Citas Notables
We've monitored the status of the changes applied to improve serviceability and confirmed they're not taking as expected.— Microsoft, on X
We're identifying alternate workstreams that can be applied to increase capacity.— Microsoft, on X
Quieres la nota completa?
Lee el original en The Hindu ↗