Written November 14, 2026, from public reporting and Microsoft’s own status updates. We will update it when Microsoft publishes its full incident report.
If your team uses Microsoft 365, you probably noticed this one. Outlook stopped connecting, calendars and meeting scheduling failed in Teams, and Copilot stopped working. It lasted close to a full day. Here is what happened, and what to put in place so the next outage doesn’t stop your business.
What happened
Microsoft lists the start as 11:17 AM Eastern time on November 12 for its Exchange Online incident. At 1:26 PM it widened into a broader Microsoft 365 degradation. Microsoft confirmed that customers might be unable to connect to Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR. User reports of Outlook problems on Downdetector peaked at roughly 130,000. Disruption reached users in 74 countries. Microsoft 365 Outage, November 12, 2026: What Is Down and the Timeline +3
By that evening Microsoft reported limited recovery after returning some affected servers to service. The outage eased after nearly 24 hours, and some organisations were forced back to fax while at least one European bond repurchase was halted. As of 3:02 PM Eastern on November 13, access had largely recovered and Microsoft was still clearing queued mail. Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide +2
What Microsoft has said about the cause
Microsoft says it found no indication that the outage was caused by malicious or cyber activity. It called it a technical issue not related to cyber or AI agents, and promised a full post-incident report with the root cause after recovery. One report says Microsoft pointed to failed server health checks, but Microsoft had yet to confirm the root cause. We won’t guess beyond that. Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide +3
What it meant in the Philippines
Our own time conversion: the Exchange incident began around 12:17 AM Philippine time on Friday, November 13, and access was largely back around 4 AM on Saturday. That means a business on Microsoft 365 probably had trouble through the entire Friday workday.
Some things kept working. Teams chats and calls largely continued to work, and desktop Outlook could still show email that had already been downloaded. The parts that failed were the ones that depend on Exchange Online: email, calendars, scheduling, and anything built on top of them. Al Jazeera
One outage doesn’t mean leaving the cloud
Every large provider has outages, and Microsoft 365 had another notable one earlier this year. In January, Microsoft investigated an issue affecting Microsoft 365 services including Teams and Outlook. The real issue is that when so much of your business sits in one provider, you can’t fix it yourself and have to wait. A little planning makes the wait far less painful. tomsguide
A simple outage plan for a small business
Know where to check. Use the Service health page in your Microsoft 365 admin center, and follow the official Microsoft 365 Status account on X. Save the incident numbers when you see them (this one used EX1550543 and MO1550821). Remember that the admin center can be affected too, and the Microsoft 365 status page itself was reported offline for a time before coming back. techradar
Have a second way to reach your team. A Messenger, Viber or WhatsApp group, plus a printed or offline list of phone numbers, takes ten minutes to set up.
Have a second way to reach customers. Keep customer contacts outside your mailbox, and have a short holding message ready for your Facebook Page or website: “We are having email problems and will reply as soon as we can.”
Keep the essentials available offline. Key contracts, price lists, supplier numbers and bank contacts should not live only in email.
Decide in advance when to switch to plan B, for example after 30 minutes of no email, so nobody waits for permission.
Check what depends on email. If a system sends login codes, password resets or approvals by email, an email outage can lock you out of other tools too.
Expect delayed and duplicate mail. After recovery, queued messages arrive late. Don’t resend invoices or payment instructions without checking, or you may create duplicates.
Watch for scams. Outages create confusion, and fake “restore your access” emails and texts follow. Be suspicious of any message during an outage that asks you to sign in or reset a password.
For whoever manages IT
Read the incident entries in the Microsoft 365 admin center, set up alerts for service health, review Microsoft’s post-incident report when it is published, check mail queues after recovery, and ask yourself how many of your tools quietly depend on Exchange Online. Larger organization's can also look at an email continuity option that keeps mail flowing during an outage.
Want a continuity plan?
At Northgate IT Consultancy we help Philippine startups and small businesses review their cloud and infrastructure, and build a simple plan for the day something goes down. Send us a message at northgate-it.com.ph/contact. A short call is free.