CompaniescollaborationMicrosoft 365
Is Microsoft 365 down?
Microsoft 365’s status page reports all systems operational since , as of our latest poll (every 10 minutes).
Last incident: Users may be unable to connect to multiple Microsoft 365 services, started , resolved . 31 incidents in the last 30 days, 31 in 90. Status history · Uptime
Follow Microsoft 365: Atom feed, calendar, or start a stack with it to follow it alongside your other vendors.
- Status page says
- Operational since
- Last 90 days
- 31 incidents
- Rewrites caught
- 2 edited
- Next deprecation
- None announced
Company facts
- Founded
- 1975
- Listing
- Public (NASDAQ: MSFT)
Company facts · source: Crustdata / The Companies API via Treg · as of 2026-11-13. Third-party data, not covered by our CC BY 4.0 license.
Our copy of Microsoft 365’s status page starts Nov 12; hatched days are before that. Select a day to jump to its incidents. Days are in UTC.
How Microsoft 365 reports incidents
Compared with the 175 vendors that have enough incidents to compare. Each tick is one vendor; lower is better on every line.
Provisional. Built nightly from every archived version of each incident, last on . Compare all vendors
- First posted only after it was over
- 0% 0 of the 31 incidents we have in full detail
The first update already said resolved. Typical vendor: 6%.
Microsoft 365: lower than most vendors.
- Time to resolve
- 1 h 2 min median; 9 in 10 within 2 h 1 min
From the vendor’s own start and resolve times, over the 10 days of history we have. Typical vendor: 1 h 48 min.
Microsoft 365: lower than most vendors.
- Major or critical incidents
- 0.0 a month 0 in the 10 days of history we have
Impact as the vendor labels it. Typical vendor: 1.1 a month. Short history, so this rate can swing.
Microsoft 365: lower than most vendors.
- Rewrites caught
- 0 deleted, 2 edited after publishing
Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.
Dependencies
What Microsoft 365 relies on and who relies on Microsoft 365, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.
Who depends on Microsoft 365
| Vendor | Evidence | Signal |
|---|---|---|
| FireHydrant | blamed in 2 incidents; integration affected in 1 “…to the app The issue affecting our service has been fully resolved. The login button for Microsoft Teams users is now displaying and functioning correctly. Our upstream provider, Microsoft, is curren…” incident | Strong |
| Greenhouse | blamed in 1 incident; integration affected in 2 “…n Scheduling Shared Calendar Our engineering team has released a workaround that restores Microsoft Teams links when scheduling on shared calendars. Affected customers have been contacted by Support w…” incident | Likely |
| Netlify | blamed in 1 incident; together in 1 outage event “…Delayed Support Email Delivery to Microsoft 365 and Outlook Mailboxes This incident has been resolved. We are aware that some Netlify Support email responses to customers using Microsoft 365 and Outlo…” incident | Likely |
| Asana | blamed in 1 incident; together in 1 outage event “…Integrations with Outlook are unavailable or degraded This incident is now resolved: the earlier Microsoft Outlook outage that caused degraded performance for features like AI meetings and AI teammate…” incident | Likely |
| Help Scout | blamed in 1 incident; together in 1 outage event “…Possible email delays for Microsoft 365 / Outlook users Microsoft is reporting that Microsoft 365 services have recovered and sustained service recovery has continued across most platforms. While Micr…” incident | Likely |
| Dynatrace | blamed in 1 incident; together in 1 outage event “…Information regarding the global Microsoft 365 outage Microsoft has reported that its services are back to an operational state. Dynatrace services that rely on Microsoft, including email notification…” incident | Likely |
| Mailchimp | blamed in 1 incident; together in 1 outage event “…nt outage affecting Microsoft. Due to this, you may see issues with delayed deliveries to Outlook, Hotmail, or other Microsoft email inboxes. Additionally, if you are a Microsoft customer, you may exp…” incident | Likely |
| Chargebee | blamed in 1 incident “…Microsoft 365 Service Degradation Microsoft has fully restored their 365 services. Custom SMTP email notifications are fully restored. We apologize for any disruption this caused. Due to an ongoing Mi…” incident | Likely |
| Anthropic | blamed in 1 incident “…Elevated errors affecting the Microsoft 365 connector This incident has been resolved. From 08:03 PT / 16:03 UTC on November 12 to 08:40 PT / 16:40 UTC on November 13, mail, calendar and search tools…” incident | Likely |
| Scaleway | blamed in 1 incident “…[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail) This incident has been resolved. Start: 2026-11-12 ~18:45 UTC (19:45 CET) Impact: Some emails can take up…” incident | Likely |
| Claude | blamed in 1 incident “…Elevated errors affecting the Microsoft 365 connector This incident has been resolved. From 08:03 PT / 16:03 UTC on November 12 to 08:40 PT / 16:40 UTC on November 13, mail, calendar and search tools…” incident | Likely |
| Gong | blamed in 1 incident “…Microsoft Teams calls & outlook is currently affected by a service disruption at Microsoft The issue has been resolved. Some customers may currently experience disruptions with Microsoft Teams calls d…” incident | Likely |
| Jira | blamed in 1 incident “…email processing. The issue is attributed to the ongoing global service degradation with Microsoft 365 services. More details can be referred on their status page - https://status.cloud.microsoft/ In…” incident | Likely |
| Xero | blamed in 1 incident “…genow lists all systems operational. Emails from Xero to Microsoft email inboxes (such as Outlook or hotmail) may have failed during this time. We're aware that customers attempting to send emails fro…” incident | Likely |
| Lever | blamed in 1 incident “…Microsoft 365 outage affecting email/calendar sync and interview scheduling This incident has been resolved. Impact Summary: Customers using Microsoft may have experienced delays or failures in Outloo…” incident | Likely |
And 25 more.
Outage events: Microsoft 365, .
Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.
Changes and edits
Incidents Microsoft 365 rewrote or removed, and notable changes to the pages we watch.
Struck in red is what Microsoft 365 removed. Blue is what they added.
Thursday, November 12
1 rewrite
- Wording onlyEdited by the vendor
Microsoft 365 (incl. Teams) status: Service degradation
Title
Users may be unable to connect to multiple Microsoft 365 servicesMicrosoft 365 (incl. Teams) status: Service degradation
Pricing and pages we watch
No pricing, trust or legal pages tracked for Microsoft 365.
Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
The Weekly Rewind: one short weekly email on what changed at Microsoft 365 and the other vendors we track, including silent edits. Subscribe (opens in new tab)
Incidents
31 incidents since Nov 12. Maintenance is left out.
Friday, November 13
23 incidents
- Minor, 1 h 7 minMinor incident
- Minor, 10 h 6 minMinor incident
- Minor, 2 h 10 minMinor incident
- Minor, 2 h 1 minMinor incident
- Minor, 1 h 11 minMinor incident
- Minor, 1 h 8 minMinor incident
- Minor, 1 h 9 minMinor incident
- Minor, 1 h 7 minMinor incident
- Minor, 1 h 3 minMinor incident
- Minor, 1 h 7 minMinor incident
- Minor, 54 minMinor incident
- Minor, 2 h 9 minMinor incident
- Minor, 40 minMinor incident
- Minor, 50 minMinor incident
- Minor, 51 minMinor incident
- Minor, 1 h 10 minMinor incident
- Minor, 46 minMinor incident
- Minor, 1 h 1 minMinor incident
- Minor, 30 minMinor incident
- Minor, 53 minMinor incident
- Minor, 48 minMinor incident
- Minor, 1 h 2 minMinor incident
- Minor, 59 minMinor incident
Thursday, November 12
8 incidents
- Minor, 1 h 31 minMinor incident
- Minor, 56 minMinor incident
- Minor, 56 minMinor incident
- Minor, 1 h 7 minMinor incident
- Minor, 35 minMinor incident
- Minor, 1 h 7 minMinor incident
- Minor, 39 minMinor incident
- Minor, 36 minMinor incident