How to Check a Microsoft Outlook Outage and Keep Work Moving
Microsoft confirmed a Nov. 12 Outlook and Microsoft 365 outage. How a small business checks official status, handles delayed email, and keeps work moving.

Short answer: Microsoft confirmed a widespread Outlook and Microsoft 365 outage starting Thursday, Nov. 12, around 1 p.m. Eastern. By Friday it reported broad recovery from a technical issue, not a cyberattack, but its public status page still listed a service degradation early Saturday, Nov. 14. Check official status, and use another channel for urgent messages until mail is flowing normally.
Key points
The outage affected Outlook and Exchange Online, and it also hit other Microsoft 365 apps such as Teams, SharePoint and Copilot, according to CNBC, The Verge and Microsoft's own status updates.
In a Friday statement, Microsoft called it a "technical issue not related to cyber or AI / agents," and said it started with "an issue during an earlier network capacity upgrade that surfaced following a recent network change." NBC Chicago and The Verge published the statement in full.
Microsoft lengthened, to 48 hours, the window in which delayed messages keep trying to send, CNBC reported. Windows Central quoted the Microsoft 365 Status account saying that extended window was still in place on Friday.
This is not the same story as Microsoft's exploited Outlook message-file flaw, which is a security bug fixed in an Office update on Nov. 10. The events are unrelated.
What to do now: confirm the outage on Microsoft's official status page, keep a non-email way to reach customers and vendors, and wait for queued mail to catch up before you resend anything.
What happened?
A global Microsoft 365 disruption began Thursday, Nov. 12. CNBC reported that connectivity problems started shortly before 1 p.m. Eastern. The BBC said Microsoft first acknowledged that users in the Americas could not reach Exchange Online mailboxes at 17:54 GMT that day, which is 12:54 p.m. Eastern.
People could not open mailboxes in Outlook on the web, the Outlook desktop app and other connection methods, and outgoing mail piled up. Calendar access and workplace chat were also disrupted for many organizations, as The Verge, CNBC and the BBC all reported.
Microsoft's early status updates, described by CNBC and by NBC Chicago, pointed to an unusually high load on part of its infrastructure after some servers became unavailable and failed automated health checks. On Friday, Microsoft issued a fuller explanation: the incident was a technical problem tied to an earlier network capacity upgrade, and it was not caused by a cyberattack or by AI agents. Microsoft said it had addressed the underlying issue and was bringing remaining customers back gradually. It also said it will publish a post-incident report after its review.
Is the outage over?
Not completely, as of late Friday night, Nov. 13. Treat recovery as in progress until Microsoft's official status page says otherwise.
Just before noon Eastern on Friday, Microsoft said it was seeing "broad recovery and stability across our services," in the statement published by The Verge and NBC Chicago. Earlier Friday, Microsoft reported improving service availability and email delivery, while warning that some people could still see intermittent problems, CNBC and Windows Central reported.
Microsoft's public service health page at status.cloud.microsoft/m365 still showed a Microsoft 365 service degradation, with the line "Users may be unable to connect to multiple Microsoft 365 services," when we checked it at about 11:56 p.m. Eastern on Friday, Nov. 13, and again just after midnight Eastern on Saturday, Nov. 14. The same wording appeared on Microsoft's public service status address, admin.microsoft.com/servicestatus, which redirected to that official status host. Microsoft has not yet published the promised post-incident report.
Access can return before every delayed message has been delivered. If Outlook opens again but mail looks quiet or late, that can still be leftover queue traffic, not a second outage.
How do I check Microsoft's official status?
Start with Microsoft's own pages, not a social post or a forwarded email. Microsoft's documentation explains how administrators should do this, and there is a public page when the admin center itself will not load.
Open the public status page. Go to status.cloud.microsoft/m365, or to admin.microsoft.com/servicestatus. These are Microsoft pages. If they report a Microsoft 365 incident or degradation, the problem is likely on Microsoft's side, not a single broken PC in your office.
If you can sign in as an admin, open Service health. Microsoft Learn says to sign in at admin.microsoft.com, then go to Health, then Service health. The incident identifier quoted in Microsoft 365 Status updates on Friday, and reported by Windows Central, was MO1550821. Look that ID up for the full update feed if it still appears in your admin center.
If the admin center will not load, stay on the public page. Microsoft Learn tells admins to use the service status page when they cannot sign in to the admin center. That matters here, because Microsoft's own updates said some admin center pages might not load during this incident.
Use Microsoft's status account only as a supplement. Microsoft Learn also points readers to the Microsoft 365 Status account, @MSFT365status, on X for some events. Treat it as a pointer back to the official status pages, not as a reason to skip them.
What should a small business do right now?
Confirm it is a Microsoft issue, keep work moving on another channel, and avoid making the backlog worse. You do not need to reinstall Office to "fix" a cloud outage.
Check official status first, using the steps above, before you spend the morning rebuilding a staff member's Outlook profile.
Tell staff and regular customers how to reach you without email. A phone number, a text thread, or a simple voicemail greeting is enough for urgent orders, appointments and vendor issues. Write that backup method down so you are not hunting for it the next time Outlook fails.
Leave working sessions alone. If a signed-in app is still usable, do not sign out, clear its data or reinstall it just to "refresh" it. A reinstall will not end a cloud outage, and it can drop a session that was still working.
Do not blast out duplicates. Microsoft stretched the delivery retry window to 48 hours so delayed messages could still go through. If you resend the same invoice or appointment reminder to everyone, customers may get both copies once the queue drains. Resend only if a message is truly time-critical and you have confirmed it never arrived.
When access returns, scan for what you missed. Check the inbox, sent items, junk folder and calendar for late mail, failed meetings and bounced messages. Look especially for customer orders, invoices, password resets and appointment changes from Thursday and Friday.
Watch for look-alike Microsoft emails. Be wary of unexpected messages that ask you to "restore your mailbox," enter a password, or pay to reopen Outlook. Microsoft will not need a credit card or a hurried login from a leftover email to finish its own recovery. Our guide to checking a security alert that might be a scam walks through a careful way to inspect those messages.
Our view: a small shop in southwest Michigan does not need a second email platform on standby for a single afternoon. It does need a written backup contact method, one person who knows how to open Microsoft's status page, and a habit of not depending on Outlook alone for same-day customer work.
Will delayed emails still arrive?
Many of them should, but not instantly, and Microsoft has not promised that every message will get through.
CNBC reported that Microsoft's engineers were working through email queues and backlogs, and that the company extended to 48 hours the period in which delayed mail keeps trying to send, so those messages are less likely to be dropped. Windows Central quoted Microsoft 365 Status on Friday saying that extended 48-hour window remained in place as delivery caught up.
If a message still has not arrived after that retry window, treat it as missing. Ask the sender to resend it, or use another channel, rather than assuming Outlook will eventually find it.
How is this different from last week's Outlook security flaw?
They are two different problems, close together on the calendar.
On Nov. 10, Microsoft released an Office update for a security flaw in Outlook that attackers were already using. That story is about installing a patch and checking your Office build, and we covered the steps in How to Update Outlook After Microsoft's Exploited Message-File Flaw. This week's incident is a service outage: Microsoft's cloud mail and related apps were hard to reach or slow, then gradually recovered. Installing that Nov. 10 update will not end an outage, and this outage is not evidence that the security flaw is still open.
If you have not yet applied the Nov. 10 Outlook security update, do that after mail is stable, following the guide above. Do not skip it because this week's problem was an outage.
Frequently asked questions
Should I reinstall Outlook or Microsoft 365? Usually no, not as a first step. This was a cloud service failure, not a typical broken install on one PC. Reinstalling can sign you out of apps that are still working. Check official status first, and only repair or reinstall a single device if that device still fails after Microsoft says the service is healthy and other computers in the office work.
Should I resend every email from Thursday and Friday? No. Microsoft extended its delivery retry window to 48 hours to protect delayed mail. Resend only the messages you know are urgent and have not arrived. After the queue clears, review sent items before repeating a mass message.
Did this affect only Outlook? No. Microsoft and multiple news outlets said other Microsoft 365 services were affected, including Teams, SharePoint and Copilot, along with mailbox access in Exchange Online. Some features that do not depend on Exchange Online could still work while mail did not.
How can I get a heads-up next time? If you have a Microsoft 365 admin account, Microsoft Learn says you can turn on email notifications from the Service health page by choosing Customize, then Email. You can also bookmark the public status page and, if you use X, follow @MSFT365status as a backup pointer, as Microsoft's documentation suggests.
For more, see our guides to updating Outlook after the exploited message-file flaw, Microsoft 365's text-message login code deadline and checking a security email that might be a scam.
Disclosure: No company or organization named in this article paid for it, reviewed it or saw it before publication. Cybercave Technologies builds, hosts and manages websites for small businesses and offers remote IT support. Times, quotes and status wording are as published by Microsoft, CNBC, The Verge, the BBC, NBC Chicago and Windows Central and were checked on Nov. 13–14, 2026. Not sponsored.
Sources
- PRIMARY: Microsoft, Service Health Status (Microsoft 365), checked 11:56 p.m. ET Nov. 13, 2026
- PRIMARY: Microsoft, public service status page (admin.microsoft.com/servicestatus), checked 11:57 p.m. ET Nov. 13, 2026
- PRIMARY: Microsoft Learn, "How to check Microsoft 365 service health," checked Nov. 13, 2026
- The Verge (Jess Weatherbed), "Microsoft's massive Outlook outage might be over," updated Nov. 13, 2026, 4:17 p.m. UTC, including Microsoft's Friday statement
- CNBC (Jenni Reid, Samantha Subin and Caleigh Keating), "Microsoft apologizes for massive outage that took down Outlook and other 365 services," updated Nov. 13, 2026, 1:18 p.m. ET
- BBC News (Rachel Clun), "Microsoft 'deeply sorry' for global outage as it reports broad recovery," Nov. 13, 2026
- NBC Chicago and The Associated Press, "What caused the Outlook outage? Microsoft issues apology after some services restored," updated Nov. 13, 2026, 11:50 a.m.
- Windows Central (Sean Endicott), "Microsoft outage drags on as Outlook, Teams, and Microsoft 365 show signs of recovery," updates through Nov. 13, 2026, including Microsoft 365 Status wording
