When Microsoft 365 goes down, the right response is to confirm the problem is on Microsoft's side, leave passwords and software alone, move your team to a backup communication channel, contact key customers by phone, and watch for phishing. Businesses that prepare a simple outage plan in advance lose far less time than those that improvise. 
At Infortech, we are a managed IT services provider based in Santa Clara, California, and we have supported Bay Area manufacturers, construction firms and other businesses for more than 26 years. This guide explains what a Microsoft 365 outage is, what the major outage of November 2026 showed, and the action plan we recommend for any extended email and collaboration outage.
Key takeaways
- A Microsoft 365 outage is a failure inside Microsoft's infrastructure. You cannot fix it from your side.
- Email and collaboration tools can fail together. Teams is not a backup for Outlook.
- Major outages can last longer than a business day, so plan for more than a short interruption.
- Email is usually delayed during an outage, not lost.
- A one-page plan, a backup communication channel and a standby way to send email cover most of the risk.
What is a Microsoft 365 outage?
A Microsoft 365 outage is a period when Microsoft's cloud services, such as Outlook, Exchange Online, Teams, Copilot, SharePoint and OneDrive, are unavailable or degraded because of a problem in Microsoft's own infrastructure. Because these services share underlying systems, a failure in one often affects the others at the same time.
What happened in the November 2026 Microsoft 365 outage?
On Thursday, November 12, 2026, a worldwide Microsoft 365 outage disrupted Outlook, Exchange Online, Teams, SharePoint, Copilot and other services, and degraded service continued into the following day. We run our own company on Microsoft 365, so we felt this one too. It is a useful case study because it lasted far longer than most.
Key facts
- Date: began Thursday, November 12, 2026, with degraded service continuing into Friday, November 13
- Duration: more than 24 hours of disrupted or degraded service
- Microsoft incident IDs: EX1550543 (Exchange Online) and MO1550821 (Microsoft 365)
- Services affected: Outlook and Exchange Online most heavily, plus Teams, SharePoint, Copilot, Defender XDR, Planner, To Do and Purview. Consumer services such as Outlook.com and OneDrive were also affected.
- Who was affected: businesses, government agencies, hospitals and airlines in multiple countries
- Cyberattack: Microsoft reported no indication of malicious activity
What caused it?
During the outage, Microsoft explained that a large number of its servers had become unavailable, and the load they had been carrying fell on the servers that remained. On the affected servers, the process that sets up secure connections became overwhelmed, and the servers stopped handling requests. Microsoft stated that the overload was not caused by an increase in traffic, and it committed to publishing a Post-Incident Report with the full root cause.
Why did recovery take so long?
- There was no obvious change to undo. Many cloud outages end quickly because the provider reverses a bad update. Early in this outage, Microsoft said it could not tie the failure to a recent change.
- The first fixes did not hold. Rerouting traffic and restarting servers did not bring the expected relief.
- Restarted servers failed again under load. Microsoft reported that servers it returned to service could become unresponsive once traffic reached them, which forced a slow, staged recovery.
- The backlog had to clear. After connections came back, emails that had queued up during the outage still needed time to be delivered.
What did the outage teach businesses?
- Email and collaboration tools can fail together. Teams, SharePoint and Copilot went down alongside Outlook. If Teams is your backup for email, you do not have a backup.
- An outage can last more than a business day. A plan that assumes a one-hour interruption is not enough.
- You cannot fix it from your side. Password resets, new Outlook profiles and reinstalls do nothing when the fault is in the provider's infrastructure.
- Your IT provider may be affected too. If everyone relies on the same platform, everyone needs a second way to communicate.
- Outages attract scammers. Fake "restore your mailbox" messages follow every major disruption.
What should a business do when Microsoft 365 goes down?
No business can prevent a Microsoft outage. What you control is how prepared you are, how you respond, and how quickly you recover. We recommend an action plan in three phases.
Phase 1: Precautions to prepare before an outage
- Write a one-page outage plan. Name who decides that an outage is under way, who communicates with staff, and who communicates with customers and vendors.
- Set up a backup communication channel that does not depend on Microsoft 365. Your phone system, a group text list or a separate chat and meeting tool all work. Test it at least once.
- Arrange a standby way to send and receive email. Options include an email continuity service or a small mailbox on a separate provider and domain for urgent notices.
- Keep key contacts outside Microsoft 365. Store staff, customer and vendor phone numbers and email addresses somewhere you can reach when Outlook is down.
- Make critical files available offline. If you solely rely on OneDrive or SharePoint, keep local or synced copies of the documents your operation cannot run without, such as schedules, drawings, bids and job files.
- Back up Microsoft 365 data independently. An outage is about availability, not data loss, but a separate backup means a provider problem never becomes a data problem.
- List what depends on email. Purchase orders, invoices, scan-to-email, system alerts and sign-in codes sent by email all stop when email stops. Decide the workaround for each in advance.
- Bookmark the status page. Microsoft posts updates at https://status.cloud.microsoft when the Microsoft 365 admin center is unavailable.
- Train your staff. Everyone should know the backup channel and should know to ignore unexpected messages offering to restore or re-verify an account.
Phase 2: Actions during an outage
In the first 30 minutes:
- Confirm it is the provider and not you. Check the status page and with your IT provider.
- Tell staff what is happening over the backup channel. Ask them not to reset passwords, rebuild Outlook profiles or reinstall Office.
In the first few hours:
- Contact key customers and vendors by phone or your standby email so they know replies may be delayed.
- Handle time-sensitive work first: orders, shipments, bids, payroll and anything with a deadline.
- Work from offline files where you can, and keep a list of what will need to be sent or filed once service returns.
- Stay alert for phishing.
If the outage passes one business day:
- Switch customer-facing communication to your standby email or continuity service.
- Post a short notice on your website and phone greeting if customers normally reach you by email.
- Hold a brief daily check-in to reset priorities until service is stable.
Phase 3: Recovery after an outage
- Expect a backlog. Sending mail systems normally retry delivery for a period of time, so delayed messages may arrive in a burst and out of order.
- Check Outbox and Sent Items and resend anything that did not go out.
- Confirm the important ones. For time-sensitive items, ask the other party to confirm they received your message, and confirm you received theirs.
- Restart Outlook and Teams if they do not reconnect on their own.
- Ask about service credits. Microsoft's service level agreement provides for credits when uptime falls below its commitment, and credits have to be requested. Ask your Microsoft licensing provider whether you qualify.
- Review and update the plan. Write down what worked, what did not, and what you want in place before the next one.
Frequently asked questions
How do I check if Microsoft 365 is down?
Check Microsoft's public status page at status.cloud.microsoft. Administrators can also check Service health in the Microsoft 365 admin center, and Microsoft posts updates on its Microsoft 365 Status account on X.
Should I reset my password or reinstall Outlook during an outage?
No. When the failure is inside Microsoft's infrastructure, changes on your end will not help and can cause new problems when service returns.
Is email lost during a Microsoft 365 outage?
In most cases email is delayed, not lost, because sending mail systems normally retry delivery for a period of time. If you were expecting something time-sensitive, ask the sender to confirm.
Can Microsoft Teams be a backup when Outlook is down?
Not reliably. Teams and Outlook share Microsoft infrastructure and can fail together, as they did in November 2026. A backup channel should be independent of Microsoft 365.
What is an email continuity service?
An email continuity service is a standby system that lets your business keep sending and receiving email while your primary email service is unavailable.
How long do Microsoft 365 outages last?
Most are resolved within hours, but major ones run longer. A January 2026 outage in North America lasted nearly ten hours, and the November 2026 outage disrupted service for more than a day.
Was the November 2026 Microsoft 365 outage a cyberattack?
Microsoft reported no indication of malicious or cyber activity. It attributed the outage to servers in its own infrastructure becoming unavailable.
Can a small business prevent Microsoft 365 outages?
No, but you can limit the impact with a written outage plan, a backup communication channel, a standby way to send email, offline access to critical files, and an independent backup of Microsoft 365 data.
Talk to Infortech
Infortech helps businesses across Silicon Valley and the Greater Bay Area plan for and manage Microsoft 365. Our Secure Managed Microsoft 365 Service Plan (https://www.infortech.com/services/secure-managed-microsoft365-services/) includes email security, backup, and email continuity solutions for extended outage. If you want an outage plan that fits your business, we are glad to help.
Book a Discovery Call: 800-741-8530 or https://infortech.com/discovery-call-request
Sources