Outlook, Teams, OneDrive, Word, Excel and Copilot. The public page covers consumer services; business tenants see their own incidents in the admin center.
OperationalNo active incidents in the official feed
0active incidents now
0incidents in the last 90 days (official feed)
66.50%of our 5-minute checks with no degraded or major status, last 7 days
From Microsoft 365 public status (consumer). Times in Eastern (ET).
No active incidents reported by Microsoft 365
Checked Nov 18, 9:39 PM EST · official feed, refreshed every 10 minutes
Services
Microsoft 365 (Consumer)Operational
Microsoft CopilotOperational
Microsoft ListsOperational
Microsoft Teams FreeOperational
Microsoft To-DoOperational
Microsoft WhiteboardOperational
Office for the web (Consumer)Operational
OneDriveOperational
Outlook.comOperational
Phone LinkOperational
Our 5-minute checks · last 7 days
We read Microsoft 365's official status every 5 minutes. Each sliver is one hour, colored by the worst status seen; the daily figure is the share of checks with no degraded or major status. Stored since Nov 11, 9:48 PM EST.
7 days agonow
100%Wed 11/11
75%Thu 11/12
0%Fri 11/13
5%Sat 11/14
100%Sun 11/15
100%Mon 11/16
100%Tue 11/17
100%Wed 11/18
Periods flagged by our checks
Nov 12, 2:33 PM EST → Nov 14, 10:46 PM EST
1 service(s) affected
Microsoft 365 (Consumer): Service degradation Users may be unable to access or perform several actions in Microsoft 365 services such as Outlook.com and OneDrive.
Incident history
Incidents per month from the official feed, by severity. Microsoft does not publish a public Microsoft 365 incident history. Business and enterprise incidents (with root causes) are in the Microsoft 365 admin center under Health > Service health; history here comes from this site's own 5-minute checks. History is short: dashed boxes and empty months before the feed's first entry mean no published data, not a clean record.
Last 13 weeks
OperationalMinorDegradedMajorNo data
Root causes: hack, AI, config error or something else?
For each incident in the past year we show a cause only when Microsoft 365's own report states one, quoting the sentence. The category is our label for that sentence; anything else is marked Unconfirmed / not yet disclosed.
No incidents in the public feed for the past year. Microsoft does not publish a public Microsoft 365 incident history. Business and enterprise incidents (with root causes) are in the Microsoft 365 admin center under Health > Service health; history here comes from this site's own 5-minute checks. See the notable outages below.
Notable past outages
The big ones, with the cause in the official write-up's own words.
Jul 19, 2024
CrowdStrike update crashes Windows PCs
Third-party dependency
“CrowdStrike, an independent cybersecurity company, released a software update that began impacting IT systems globally. Although this was not a Microsoft incident…”
Impact: Windows PCs running CrowdStrike Falcon crashed, so many people could not reach Microsoft 365 at work.
“A network engineer was performing an operational task to add network capacity to the global Wide Area Network (WAN)… steps to modify the IP address for each new router.”
Impact: Teams, Outlook and other Microsoft 365 services were unreachable for many users.
A short playbook. Tick items as you go (saved on this device only).
1 · Confirm the impact
2 · Fail over and limit the damage
3 · Monitor and get alerts
4 · Communication templates
Customer heads-up (incident open)
Status update ({time} ET): Some of our services are slow or unavailable because of an outage at Microsoft 365, a provider we use. Your data is safe. We're working around it and will update you by {next} ET. Live status: {your_status_page}
Internal alert
Microsoft 365 incident affecting {services} in {region} since {time} ET. Impact on us: {impact}. Owner: {name}. Failover: {yes_no}. Next check-in {next} ET.
All clear
Resolved ({time} ET): Microsoft 365 has recovered and our services are back to normal. If anything still looks wrong, reply here or contact {support}. Thank you for your patience.
Fill in the {curly} parts. Post updates somewhere not hosted on the affected provider.
Official links, contacts and alerts
Every link checked before publishing. Phone numbers only where Microsoft 365 publishes them.