The outage began around 17:25 UTC on Thursday, November 12, 2026, according to Ookla, as cited by Deutsche Welle and Reuters. That is about 1:25 AM on Friday, November 13, in Manila time. Outlook, Teams, Copilot, and services that depend on Exchange Online were affected. Microsoft first acknowledged trouble accessing Exchange Online mailboxes at 17:54 UTC, which is 1:54 AM Friday in Manila, and shortly afterwards warned that users in any region could be hit.
Microsoft said on Saturday, November 14, that it had completed work on the underlying issue and restored service to the remaining affected customers and regions. Deutsche Welle, The Times of India, and The Hindu all describe an outage of more than 24 hours, with full restoration on Saturday. Consumer products had already recovered at 16:10 UTC on Friday, according to The Hindu, citing Reuters, while enterprise recovery continued into Saturday.
What Microsoft Says Went Wrong
A Microsoft spokesperson told The Times of India that the incident “was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.” The company called it “a technical issue not related to cyber or AI/agents.” Deutsche Welle, reporting with Reuters, said Microsoft was “not aware” of any outside interference and blamed server issues. Those are company statements, and Microsoft has promised a full post-incident report once its review is complete.
Early public updates pointed to elevated load. Microsoft later said traffic itself had not risen. The Times of India said a number of servers became unexpectedly unavailable after failing automated health checks, which pushed work onto the machines still running and strained those too. A core process that handles secure connections became overwhelmed, and those servers stopped processing requests. An Associated Press report republished by The Hindu also described servers becoming unexpectedly unavailable after failing automated checks.
As servers came back, they faced a backlog of retried mail from outside systems. Microsoft extended its email timeout window to 48 hours so queued messages would have more time to get through, and by the afternoon of November 13 UTC it said queues were approaching normal levels. Teams chats and meetings returned earlier in many places, while calendar features that rely on Exchange Online stayed patchy for longer. Outlook.com, OneDrive, OneNote, and Microsoft To Do on personal accounts were also affected, The Times of India reported.
How Wide The Disruption Ran
The Times of India reported that the disruption reached users in at least 74 countries. Downdetector recorded a peak of nearly 200,000 user reports across Microsoft services shortly after 1 p.m. New York time on Thursday, according to The Hindu. An earlier Associated Press dispatch republished by The Hindu put the Outlook-only peak at nearly 130,000 reports just after 1 p.m. Eastern Time. Deutsche Welle, reporting with Reuters, said Downdetector logged more than 7.4 million reports of problems worldwide over the course of the incident.
Britain’s National Health Service was among those hit, with staff turning to paper records, according to Deutsche Welle and The Times of India. The Times of India also reported pharmacy warnings of prescription delays in the UK, a judge in Manchester sending jurors home, and a Colorado sheriff’s office asking people to post bond in person because online payments relied on Outlook notifications. In India, the same report said the outage hit email support at IndiGo and Akasa Air, while Air India rerouted emails and said its flights ran as usual. Deutsche Welle cited Germany’s Federal Ministry for Digital Transformation and Government Modernization, which said federal government functions were not hit in a major way, though German businesses were significantly affected. The Times of India also reported that OpenAI and Anthropic ran into problems with their Microsoft 365 connectors.
Current Status On Sunday Morning
At a check at 10:34 AM Asia/Manila on Sunday, November 15, 2026, which is 02:34 UTC, the public Azure status page said there are currently no active events. The Microsoft service health page said no Azure issues were detected at that time. Microsoft 365’s public status page is a limited view. For a current picture, check the Azure status page and Microsoft 365 status updates, including the Microsoft 365 Status account on X.
What Small Businesses And Creators Can Set Up Now
Keep a backup communications channel ready before the next outage. That can be a phone tree, a shared SMS or messaging group that does not depend on Microsoft 365, or a voice bridge you can open from a mobile phone. Write down who gets contacted first, and store those numbers outside Outlook and Teams.
Set up a second email path, such as a mailbox at another provider, a forwarding rule you test twice a year, or a shared address that still works if Exchange Online is down. Tell regular clients how to reach you if mail is delayed. During this outage, Microsoft extended the timeout window so queued messages would have more time to arrive, and some delivered mail carried the time it landed, which can differ from the time it was sent. If a deal or a ticket depends on a timestamp, keep your own record of what you sent.
Turn on offline access to the files and calendars you need to keep working. Download the week’s key documents, keep a local copy of upcoming appointments, and make sure at least one laptop or phone can open those copies without a live Microsoft 365 connection. If booking links, invoices, or two-factor codes arrive only by email, add a second method, such as an authenticator app or a phone contact.
Make a habit of checking status pages and Downdetector when something feels off. Bookmark the Azure status page, the Microsoft 365 service health views you can access, and Downdetector. A spike in reports can be an early warning, but official Microsoft updates are still the place to check when service is actually back.
Keep a short incident checklist on paper or in a local file. Confirm the outage on a status page. Switch the team to the backup channel. Tell clients how to reach you. Pause anything that must arrive by email, including invoices, password resets, and calendar invites. Note the time you first saw the problem, in Manila time and in UTC. When service returns, watch for a mail backlog and delayed meeting updates before you assume the day is back to normal.
Jamoraquai Take
When Outlook, Teams, Exchange Online, and Copilot go dark together, a small business or a solo creator can lose email, meetings, calendars, and the AI helper all at once. That is the risk of keeping so much of the workday in one place. Microsoft has said this was a technical fault after a network capacity upgrade, unrelated to a cyberattack or to AI agents, and it has promised a fuller report. While we wait for that report, the useful step is a simple one. Have a second channel, a second mailbox path, and offline copies of the files and dates you cannot afford to lose. Check a status page when something feels wrong, and write down what you will do next time, while the tools are still working.
