Quick answer: During a Microsoft 365 outage, confirm the scope in Service health (incident IDs EX1550543 and MO1550821 for the 12 November 2026 event), tell users early through a channel that does not depend on Microsoft, freeze your own changes, keep a timestamped log, and verify mail flow with test messages after Microsoft marks the incident resolved.
Checklist
- Confirm scope. Open the Microsoft 365 admin center, go to Health, then Service health, and find EX1550543 and MO1550821. Reports said some admin center pages might fail to load, so keep the Microsoft 365 Status account on X as a second source.
- Set up communication outside Microsoft. Use a phone tree, SMS or a messaging group for staff and key clients.
- Send a holding statement early. Say what is affected, what you know, when the next update comes and how to reach you. Template below.
- Freeze your own changes. Do not change DNS, mail routing or access policies unless you have clear evidence of a local fault. Microsoft itself paused deployments and configuration changes during this incident.
- Keep a timestamped log. Record when the issue began for you, what failed and the business impact. It helps with post-incident reviews and any service credit request.
- Protect critical work. List payments, approvals and customer support tasks that depend on email or Teams, and agree manual fallbacks.
- Warn users about phishing. Outages are a common cover for fake “restore access” messages. Tell staff to rely only on official channels.
- After recovery, verify. Send test messages in and out, check queued and delayed mail, confirm Teams calling and meetings, and ask a few users to check Outbox and calendars. Microsoft warned during this incident that restored servers could become unresponsive again, so recheck after a few hours.
- Review the report. Microsoft normally publishes a post-incident report for major incidents in the admin center. Compare it with your log.
- Fix your own gaps. Keep an offline contact list, a documented backup channel, someone responsible for communication, and a short outage runbook that has been tested once.
Holding statement template
“We are aware of a Microsoft 365 outage affecting email and Teams. This is on Microsoft’s side and does not appear to be a problem with our systems. For urgent matters please call [number]. Next update at [time].”
Need help building a continuity plan?
Our IT support in the UAE, Microsoft 365 support and IT AMC pages explain how we help businesses prepare for incidents like this.
Frequently asked questions
Where do I find incident details for this outage?
In the Microsoft 365 admin center under Service health. The incident IDs are EX1550543 for Exchange Online and MO1550821 for the broader Microsoft 365 incident. If the admin center will not load, check the Microsoft 365 Status account on X.
Should I change DNS or mail routing during the outage?
Not unless you have clear evidence of a fault on your side. Changes during a provider outage can make recovery harder, and Microsoft itself paused its own changes in this incident.
Should I open a support ticket?
First check whether your problem matches the published incident. Open a ticket if your impact looks different from what Microsoft describes.
How do I prepare for the next outage?
Keep an offline contact list, agree a backup communication channel, assign one person to send updates and test a short runbook once.
Sources
- Tom’s Guide: live updates on the Outlook and Microsoft 365 outage
- ABC News Australia: live coverage of the Microsoft outage
- SecurityWeek: Microsoft 365 outage disrupts Outlook, Exchange Online and Teams
Last checked: 13 November 2026, about 10:00 UAE time. The latest reports we could verify ran to late 12 November (US time) and described the incident as not fully resolved. For the live state, check the Microsoft 365 admin center (incident IDs EX1550543 and MO1550821) or the Microsoft 365 Status account on X.

