Live

Microsoft 365

Microsoft 365 is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Microsoft 365 status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Microsoft 365 since . The days before that show only what Microsoft 365 published.

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

11

Business

Microsoft 365 Operational
90 days agoNo incidentsToday

Consumer

Microsoft 365 (Consumer) Operational
90 days agoNo incidentsToday
Microsoft Copilot Operational
90 days agoNo incidentsToday
Microsoft Lists Operational
90 days agoNo incidentsToday
Microsoft Teams Free Operational
90 days agoNo incidentsToday
Microsoft To-Do Operational
90 days agoNo incidentsToday
Microsoft Whiteboard Operational
90 days agoNo incidentsToday
Office for the web (Consumer) Operational
90 days agoNo incidentsToday
OneDrive Operational
90 days agoNo incidentsToday
Outlook.com Operational
90 days agoNo incidentsToday
Phone Link Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow Microsoft 365

Your coding agent knows when Microsoft 365 is down, and tells you when a failure is theirs, not yours. You can also get Microsoft 365 incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "microsoft365" and tell me if Microsoft 365 has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=microsoft365
Slack
/feed subscribe https://outages.live/feed.xml?providers=microsoft365

Go from tracking outages to fixing production issues with Polylane.

Try Polylane