Microsoft 365 Outage: What a Small Team Should Do in the First 15 Minutes

By JH-A, Charrette AI Room editor · Editorial Policy · Checked November 15, 2026

Outlook won't load, Teams is spinning, and someone has already asked you if the Wi-Fi is broken. Check Microsoft's public status page first, then move the team to a backup channel and local files, and leave your passwords alone.

I didn't test any of this during an outage. The Microsoft features below come from Microsoft's own help pages, and the outage details come from named press reports. The order, the timings and the "what not to do" list are my own reasoning, not Microsoft's advice.

Key Takeaways

• Press reports describe a worldwide outage. They put the main incident's start at 1:26 PM Eastern on Thursday, November 12.
• Start with one page when you wonder "is it just us?": status.cloud.microsoft. You don't need to sign in.
• Pick one backup channel now, before you need it. A phone list on paper counts.
• Files marked "Always keep on this device" in OneDrive still open when you're offline, Microsoft says.
• My advice, not Microsoft's: don't reset passwords or keep signing out and in. A new password can't fix an outage on Microsoft's side.

Contents

1. Was the Microsoft 365 outage just us?
2. How do I check Microsoft 365 status in one minute?
3. What should we do in the first 15 minutes?
4. What should we set up before the next outage?
5. One thing to do today
6. Frequently Asked Questions

Was the Microsoft 365 outage just us?

No, it wasn't just you: press reports say the Microsoft 365 outage of November 12 to 14, 2026 hit organizations worldwide.

BleepingComputer reported that the main incident began Thursday at 1:26 PM ET. The admin center advisory, MO1550821, listed Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR.

Petri, which called the outage global, put the first mailbox trouble earlier, at around 11:17 AM ET. Microsoft said the incident "was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change," Petri reported. Microsoft also called it "a technical issue not related to cyber or AI / agents."

Petri's last update, at 1:22 AM ET on November 14, quoted Microsoft: "We have completed our efforts to address the underlying issue of the incident."

From 1:26 PM Thursday to that update is about 36 hours. That's my arithmetic from two press timestamps, not an official figure. Other counts I saw ran shorter, so treat it as an upper estimate. I couldn't open Microsoft's own incident record, so I can't give you its official end time.

It reached South Korea too. ETNews reported that some Korean companies had trouble sending and receiving email. The science ministry said on November 14 that it had formed an emergency response team with Microsoft Korea. The ministry's own press release didn't turn up in my search.

How do I check Microsoft 365 status in one minute?

Open status.cloud.microsoft on your phone, using mobile data. If it shows a problem, stop troubleshooting your own office.

If it shows nothing yet, that doesn't clear Microsoft. I couldn't confirm how fast it listed this outage, so check again in a few minutes and ask your admin.

Microsoft's guide to checking service health names three places to look. Only one of them needs an admin account.

Where to look	Who can use it	What Microsoft says it's for
status.cloud.microsoft	No sign-in needed.	Known issues, for when you can't sign in to the admin center.
@MSFT365Status on X	No Microsoft 365 sign-in needed.	Information on "certain events". Microsoft doesn't say which ones.
Admin center: Health > Service health	Admins only, including Helpdesk admin and Service Support admin roles.	The incident ID, affected services, status and a feed of the messages Microsoft posts.

If you're not an admin, find out today who is. During an outage, that person can read the incident feed and pass it on.

The admin center is a Microsoft service too, so it can go down with the rest. If it won't load, go back to the public page.

What should we do in the first 15 minutes?

Confirm the outage, tell everyone once, then switch to work that doesn't need Microsoft 365. Copy this plan.

The steps and timings are mine. Where a step leans on a Microsoft page, the last column says so.

Minute	Do this	Why, and whose advice
0 to 1	Check status.cloud.microsoft on mobile data.	Microsoft's guide points there when you can't sign in. Mobile data rules out your office network (my reasoning).
1 to 3	Send one message on your backup channel: "Microsoft 365 is having an outage. It's not your computer. Do not reset your password."	My reasoning: it stops forty people from troubleshooting forty laptops.
3 to 6	Phone anyone with a meeting or a deadline in the next two hours. Agree on a phone call instead.	My reasoning: Teams and Outlook can't carry that message right now.
6 to 10	Ask people to open files already on their computers in the desktop Word and Excel apps. Save with Ctrl+S.	Microsoft's OneDrive page says files already on the device open offline.
10 to 13	Keep a short list of what's waiting: emails to send, files to share, approvals.	My reasoning: you can clear it in order when service returns.
13 to 15	Set a time to check status again, such as every 30 minutes. Name one person to do it.	My reasoning: everyone else can stop refreshing.

Reaching people when Teams and Outlook are both down

This part is my advice. Use a channel that doesn't run on Microsoft 365. That can be a phone tree, a text group, or a second chat channel your team already has. Keep the contact list outside Microsoft 365 too, or you can't open it.

Keeping work moving on files

This part comes from Microsoft's help pages. In OneDrive on Windows, a file with a blue cloud icon is online only. The Files On-Demand page says you can't open those without a connection. Files with a green check are on your device and will open.

Save by hand while you work. Microsoft's AutoSave page ties AutoSave to files stored in OneDrive or SharePoint Online. I couldn't find what it does when those are unreachable, so press Ctrl+S.

You can do less with email. In new Outlook for Windows, offline access is on by default and keeps 30 days of mail on your device. You can read, write drafts and queue replies in the Outbox. They wait there until you're connected again.

Microsoft 365 Copilot was on the affected list this time, so plan to write the first draft yourself.

What not to do

These four are my reasoning. No Microsoft page I opened gives this list.

• Do not reset passwords. Petri quoted Microsoft blaming a network upgrade for this outage, and a new password can't fix a fault on Microsoft's side.
• Do not keep signing out and back in. Microsoft's own example of an incident includes users "unable to sign-in". If you sign out, you may not get back in.
• Do not resend every email. Follow up by phone on the urgent ones only.
• Do not reinstall Office or restart the router before you've checked the status page.

What should we set up before the next outage?

Set up four things before the next outage: incident alerts, the admin phone app, offline folders and a contact list outside Microsoft 365.

The features are Microsoft's, and each row links to its instructions. Choosing these four is my call.

Set up	Who does it	Microsoft's instructions
Email alerts for new incidents, sent to up to two addresses. Make one a non-Microsoft address (my suggestion).	Admin	Service health: Customize > Email
The Microsoft 365 Admin app on a phone, with service health push notifications.	Admin	About the admin mobile app
Mark this month's working folders "Always keep on this device".	Everyone	OneDrive Files On-Demand
Export contacts to a CSV file. Print the key phone numbers (my suggestion).	You	Export contacts from Outlook

The email alerts have a catch. An alert sent to your Outlook inbox won't reach you if Outlook is the thing that's down. That's why I'd make the second address a non-Microsoft one.

The offline folders have a cost too. Microsoft notes that always-available files "take up space" on the device. Pick the folders you'd need tomorrow, not the whole drive.

One thing to do today

Bookmark status.cloud.microsoft on your phone, and save your admin's mobile number next to it.

Frequently Asked Questions

What if the status page looks fine but we still can't work?

It may be a problem on your side, or Microsoft may not have listed it yet. Microsoft's guide says an admin can select Report an issue on the Service health page. Microsoft then checks reports from other organizations to see how widespread it is.

Were emails lost during the outage?

I couldn't confirm that either way. BleepingComputer reported that Microsoft extended its email timeout window to 48 hours to protect delayed messages. If a message mattered, confirm with the other person that it arrived.

Does classic Outlook work offline the same way as new Outlook?

Not quite. In classic Outlook you choose Send / Receive, then Work Offline, and Microsoft says you "can't send or receive email until you reconnect". By default classic Outlook syncs 12 months of mail for Microsoft 365 accounts, while new Outlook keeps 30 days.

Will Microsoft publish a report on what went wrong?

For incidents with broad impact, Microsoft promises a preliminary review within 48 hours of resolution and a final one within five business days. Both arrive through Service health, so only admins see them. When I checked on November 15 the 48-hour window was still open, and I can't see the admin center where it would appear.

This post was drafted with the help of AI writing tools, based on my own notes and the sources linked above. The post-incident timing comes from Microsoft's Service health and continuity page.