On Thursday, 12 November 2026, millions of people opened Outlook and found an empty, spinning inbox. Over the next several hours the problem spread beyond email: Teams calendars, SharePoint, Microsoft 365 Copilot, Defender, Power BI and more all reported trouble, because so much of Microsoft 365 depends on the same mail service underneath.
This article explains what happened, in plain language: when it started (in Indian time), which apps were hit, what Microsoft has said about the cause, what you should and shouldn't do while Outlook is down, and the lessons every business can take from it.
Last updated: 13 November 2026. Microsoft had reported improving stability but had not yet declared full recovery or published its official root cause report. We will update this post when it does.
The outage at a glance
- When: started on 12 November 2026, around 9:45 PM IST (16:17 UTC), and continued into 13 November.
- What broke: access to Exchange Online mailboxes, so Outlook on the web, the Outlook desktop app, mobile mail apps and other mail connections stopped working for many users.
- Knock-on effects: Teams calendars and meeting scheduling, SharePoint features linked to email, Microsoft 365 Copilot, Defender for Office 365, Purview, Microsoft Graph, Power BI, Power Apps, Planner, To Do and more.
- Scale: Outlook problem reports on Downdetector peaked at roughly 130,000 in the United States alone.
- Microsoft's incident numbers: EX1550543 (Exchange Online) and MO1550821 (Microsoft 365 services that depend on it).
- Cyberattack? No. Microsoft said there was no indication of malicious activity.
Timeline in Indian Standard Time (IST)
Microsoft posted its updates in other time zones. Here are the key moments converted to IST, based on Microsoft 365 Status updates reported by Azure Blog and SecurityWeek.
- 12 Nov, 8:15 PM: a separate, shorter Teams issue (chat and presence delays for users in the Americas) begins. It is fixed by about 9:20 PM.
- 12 Nov, 9:47 PM: the main incident starts. Users can't open their mailboxes, and Microsoft starts investigating.
- Around 11:30 PM: Downdetector reports for Outlook hit their peak.
- 11:49 PM: Microsoft reports high load across multiple regions and begins restarting servers. A second incident is opened for services that depend on email.
- 13 Nov, around 12:30 AM: Microsoft pauses deployments and configuration changes. It explains that traffic hadn't increased: servers had become unavailable, and their work fell onto the servers that were left.
- 1:13 AM: affected servers are failing automated health checks and being taken out of service, which shrinks capacity further. Microsoft starts testing a different health-check method.
- 3:30 AM: Microsoft says its fixes haven't brought the expected relief, and starts isolating and restarting parts of the infrastructure.
- Early morning: Microsoft begins rolling back a recent network configuration change that lines up with the start of the problem. Some servers are rebuilt on an older software configuration.
- Through the morning: partial recovery in some regions, but not sustained. Microsoft throttles and reroutes traffic and adds capacity.
- 12:59 PM: Microsoft reports better server stability after patching an upstream authentication and routing component on part of its infrastructure, and starts rolling the fix out more widely.
Which apps and services were affected?
The core of the outage was Exchange Online, the service behind Outlook mailboxes. Because many Microsoft 365 apps lean on it, the impact spread wider:
- Outlook (web, desktop, mobile): mailboxes wouldn't load, and email could be delayed.
- Microsoft Teams: core chat and meetings mostly kept working, but calendars, meeting scheduling and some chat creation failed.
- SharePoint Online: features linked to email were affected; files could still be opened.
- Microsoft 365 Copilot: chat might not load, or couldn't reach mail, calendar and files.
- Defender for Office 365: Safe Links sometimes couldn't check links, so normal links could show errors.
- Defender XDR and Purview: portal pages and compliance features such as DLP and auto-labelling were affected.
- Others: Microsoft Graph (mail, calendar and contacts requests), Power BI and Fabric, Power Apps mobile sign-in, Planner, To Do, Intune, Windows 365 (for some tenants), Universal Print and parts of the admin centre.
Some people using Google Workspace through the Outlook app also reported trouble, because the Outlook client itself was affected.
What caused the Microsoft 365 outage?
Microsoft has not published a confirmed root cause yet. That comes in a Post-Incident Report, usually a few days after recovery. Its explanation also changed during the incident, so treat everything below as provisional.
- It wasn't extra traffic. Microsoft said a number of servers became unexpectedly unavailable, and the remaining servers were overloaded by the work they had to take on.
- Health checks made it worse. Struggling servers failed automated health checks and were removed from service, leaving even less capacity. Microsoft also looked into unusually high processor usage on those servers.
- Secure connections were the choke point. Microsoft said a process responsible for setting up secure connections became overwhelmed, so servers stopped handling requests.
- A configuration change is the main suspect. Microsoft first said it hadn't found a recent change linked to the start of the problem. It later began reverting a recent network configuration change that coincided with it. The fix that finally improved stability was a patch to an authentication and routing component.
Was it a hack, or linked to Patch Tuesday?
Microsoft said there is no indication of malicious activity. The outage came two days after November's Patch Tuesday, which included a fix for an actively exploited Outlook spoofing vulnerability (CVE-2026-124194). However, Microsoft has not linked that update to the outage, and there is no evidence of a connection. You should still install the security update.
Did it affect users in India?
Microsoft first described the problem as affecting users in the Americas, and most Downdetector reports came from the United States. But Microsoft also redistributed Outlook connections worldwide and reported high load across multiple regions, so organisations in other countries, including India, could be affected depending on where their mailboxes are hosted. For Indian users, the worst hours fell late at night on 12 November and the morning of 13 November. The best way to know whether your company was affected is to check the Service health page in your Microsoft 365 admin centre for EX1550543 and MO1550821.
Outlook not working? What to do (and what not to do)
Do
- Check the official status first. Visit status.cloud.microsoft, or ask your IT admin to check Service health in the admin centre.
- Be patient with email. Messages sent during an outage are usually delayed, not lost. They should arrive once the service recovers.
- Switch channels for urgent work. Use a phone call, WhatsApp, SMS or another email account for anything time-sensitive, and tell clients if replies will be late.
- Try Outlook on the web and the mobile app later. During recovery, one sometimes works before the other.
Don't
- Don't reinstall Office or delete your Outlook profile. The problem is on Microsoft's side. Resetting your computer won't fix it and can create new problems.
- Don't reset your password because of the outage. It isn't a sign your account was hacked.
- Don't trust "fix Outlook" emails or pop-ups. Scammers use big outages to send fake support messages. Only follow Microsoft's official status pages or your own IT team.
A checklist for IT admins
- Follow EX1550543 and MO1550821 in Service health to confirm whether your tenant is affected.
- Tell staff early, through a channel outside Microsoft 365 (SMS, WhatsApp group or an external page), so they don't flood the helpdesk.
- Pause your own changes during the incident, so new problems are easy to tell apart.
- Expect Safe Links errors on harmless links while Defender is affected.
- After recovery, download Microsoft's Post-Incident Report and keep a copy: Service health only shows about 30 days of history.
- Record the impact: which teams were affected, for how long, and which workarounds helped.
- Turn on Service health email alerts, with at least one going to an address outside Microsoft 365, and install the Microsoft 365 Admin mobile app.
Lessons for every business
Outages like this are rare, but they happen to every cloud provider, and Microsoft 365 already had a major Outlook outage in January this year. When your email, calendar and documents all sit with one provider, a single fault can stop your whole team. A few simple steps reduce the damage:
- Have a backup way to talk to your team. Agree in advance which channel you'll use if email and Teams are down, and who sends the message.
- Don't let customers hit a dead end. Your website is often the first place people check. A contact form that delivers to a second inbox, a click-to-WhatsApp button and a visible phone number keep enquiries coming in even when your email doesn't.
- Keep a simple status message ready. A short banner on your website ("Our email is delayed due to a Microsoft outage, please call or WhatsApp us") saves confused customers and missed orders.
- Control your own domain and DNS. If your email runs on your own domain, you keep the option to add a backup mail route or switch providers. Know who has access to your domain settings.
- Back up the data that matters. Microsoft keeps your data safe in an outage like this, but you still need an export of key contacts, files and records that you can reach without Microsoft 365.
- Write down what happened. A one-page note on what broke and what helped makes the next outage much easier to handle.
How Brave Syntax can help
At Brave Syntax we build fast, reliable websites and business tools for companies across India. If this outage showed gaps in how customers reach you, we can help with:
- Contact forms and enquiry alerts that keep working when your main inbox doesn't
- WhatsApp, call and enquiry buttons that turn visitors into leads
- A simple status or announcement banner you can switch on in seconds
- Advice on domain, DNS and business email setup
Talk to us for a free review of your website and contact setup.
Frequently asked questions
Is Outlook down right now?
Check status.cloud.microsoft or your admin centre's Service health page for the latest. As of 13 November, Microsoft reported improving stability after a fix, but had not declared full recovery.
Will I lose emails sent during the outage?
Usually not. Microsoft said email delivery could be delayed. Delayed messages are normally delivered once service recovers. If an important message never arrives, ask the sender to resend it.
Was my data hacked or leaked?
Microsoft said there is no indication this was caused by malicious activity. It was a service failure, not a breach.
Why did Teams and Copilot stop working when the problem was email?
Many Microsoft 365 features, like Teams calendars, meeting scheduling and Copilot's access to your mail, depend on Exchange Online behind the scenes. When Exchange had trouble, those features failed too.
Can I get compensation for the downtime?
Business customers with Microsoft 365 plans covered by Microsoft's service level agreement may be eligible for service credits if uptime falls below the promised level. Your admin needs to check the SLA terms and raise a claim through the admin centre.
Sources
- Azure Blog: Microsoft 365 outage, 12 November 2026
- SecurityWeek: Microsoft 365 outage disrupts Outlook, Exchange Online and Teams
- CNBC: Widespread Microsoft outage takes down Outlook and other 365 services
- Newsweek: Is Microsoft Outlook still down?
- ABC News: Microsoft Outlook outage stretches on for hours
