You open Outlook to start the day, but your inbox will not load. A colleague cannot send an urgent customer update. Someone else reports that a Teams meeting invitation has disappeared. The office Wi-Fi is working — so what has gone wrong?
On 12–13 November 2026, a major Microsoft 365 outage disrupted email and a range of connected services for organisations around the world. For small businesses, the immediate problem is not just the technology: it is the customer messages, deadlines and everyday decisions that depend on it.
A Microsoft outage is not automatically a cyberattack or a problem with your own network. Check service health, communicate through a separate channel and keep critical work moving.
Incident update — 13 November 2026: Microsoft reported improvements in service stability and email delivery, but some users could still experience intermittent access and delayed messages. Its Microsoft 365 incident MO1550821 and Exchange Online incident EX1550543 were the relevant service advisories. At the time of this update, a full root-cause report had not been published. Status may change after publication.
What happened during the Microsoft outage?
The disruption began on Thursday 12 November and extended into Friday 13 November. Users reported difficulties connecting to Exchange Online mailboxes through Outlook and other methods. Services that relied on Exchange Online or related Microsoft 365 infrastructure also experienced problems.
Microsoft described affected servers becoming unresponsive under load and said it was applying fixes and carefully restoring capacity. It reported no indication of malicious activity causing the incident. That is an important distinction: an outage can be serious without being a data breach.
Which Microsoft services were affected?
Outlook and Exchange
Mailbox access and email delivery could fail or be delayed, including in desktop, web and mobile clients.
Teams and calendars
Calendar, scheduling and other email-dependent features could be affected, even where core messaging continued working.
Connected tools
Some Copilot, Planner, security-admin and Microsoft Graph functions were also affected. The impact differed by service and user.
Not every feature was unavailable to every customer. For example, Teams chat or files already stored in SharePoint could still work in some cases. Avoid assuming that the entire Microsoft cloud is down simply because Outlook is not responding.
How to check whether Microsoft 365 is down
- Start with the Microsoft 365 admin centre. If you are an administrator, open admin.microsoft.com and review Health > Service health, including advisories relevant to your tenant.
- Check the public status page. Visit Microsoft service health for public information; tenant-specific updates may be available only after signing in.
- Check more than one connection. Compare an affected computer with another device or connection to rule out a local internet, DNS or sign-in problem.
- Record what is failing. Note the time, error message, affected users and services. This is useful when contacting IT support or communicating with customers.
A public green status indicator does not prove that your organisation has no problem. Tenant-specific advisories and your own tests remain important.
What small businesses should do during an outage
- Use a separate communication channel. Keep an agreed phone, SMS or alternative messaging route for staff and important customers. Do not depend entirely on Teams or company email for outage alerts.
- Tell customers what to expect. If responses may be delayed, publish a brief update on your website or another channel that does not rely on the affected service.
- Prioritise urgent work. Identify time-sensitive payments, appointments, bookings and support incidents; assign a person to manage them manually if necessary.
- Avoid repeated configuration changes. Do not reset every account, disable MFA or reconfigure email DNS simply because Outlook is failing during a confirmed provider incident.
- Watch for phishing. Attackers may exploit confusion with fake “Microsoft outage fix” messages. Verify instructions independently before downloading software or entering credentials.
- Keep a simple incident log. Record who is affected, temporary workarounds, supplier updates and the time service returns.
How to prepare before the next outage
You cannot prevent every failure at a cloud provider. You can, however, reduce the disruption it causes your business. Start with a short business continuity checklist:
- Identify the processes that cannot wait for email or Teams, and name a deputy for each.
- Keep an up-to-date contact list accessible outside Microsoft 365, with appropriate access controls.
- Agree a fallback communication method and practise using it.
- Know which applications depend on Microsoft identity, Exchange or Graph APIs — including external automations.
- Set expectations for manual order handling, customer updates and escalation during downtime.
- Review backup and recovery separately: backups help with data loss, but they do not automatically restore access during a live Microsoft service outage.
- After an incident, review what worked, what failed and which controls you need to improve.
The practical takeaway Keep using Microsoft 365 if it suits your business, but make sure that one unavailable platform cannot stop every conversation, customer response or critical decision.
Frequently asked questions
Is the Microsoft outage caused by a cyberattack?
Microsoft said it had no indication of malicious activity causing the 12–13 November incident. That is not the same as a final technical root-cause finding; consult the post-incident report when it becomes available.
Is my Microsoft 365 data lost?
An inability to access email or files does not, by itself, mean that data has been deleted. Avoid drawing conclusions about data loss without evidence. Maintain separate backups and test restores as part of normal resilience planning.
Should I turn off MFA to get Outlook working?
No. Disabling multi-factor authentication creates security exposure and is not an appropriate general workaround for a provider-side outage.
Will switching internet providers fix the outage?
Not if the fault is in Microsoft’s service. Testing another connection can help establish whether there is also a local connectivity issue.
Can I get compensation for Microsoft 365 downtime?
Possibly, depending on the service, agreement, eligibility rules and Microsoft’s published service-level commitments. Review the relevant SLA and any official service-credit process; do not assume credits are automatic.
Where Cholcom fits
At Cholcom, we help small businesses make their Microsoft 365 environments easier to manage, more secure and better prepared for disruptions. That includes reviewing key dependencies, setting up practical incident-response procedures, protecting identities with MFA, and planning how teams will communicate when their usual tools are unavailable.
Would your business keep operating if email went down for a day? Get in touch to discuss a Microsoft 365 resilience and security review.
Sources and live status
For the latest incident status and technical updates, consult Microsoft 365 admin centre service health (sign-in required), the Microsoft public status page, and the University of Pennsylvania’s feed of Microsoft incident advisories. For independent coverage of the wider impact, see Associated Press reporting.



