Why does Microsoft still look green when Microsoft 365 is broken for us?

Tenant-scoped incidents and Message Center posts are not public. Office staff cannot see them. That is a known gap, not a failure of this checker.

If webmail or another site on the same WAN works, and only one app or one profile fails, it is almost never a global outage. If every user in every site fails at the same minute, start with the vendor page and Azure.

Home / Productivity / Microsoft 365

Outage status

Is Microsoft 365 down right now?

Microsoft 365: Operational · checked just now

Source · status.cloud.microsoftNot an official vendor page

Operational

No active incident in the public RSS feed

Last checked just now (5 Oct, 08:55 UTC)

Official status page

Last ~2 hours (24 checks)

Microsoft 365 outage status today: public incidents, known-issue workarounds, Azure upstream, and a them-or-you checklist.

1. Is it down right now?

Microsoft Admin Center public RSS. It is updated when admins cannot open Service health — not a full Outlook/Teams/SharePoint outage board. Check the official page and your admin centre.

Affected regions / cells: Incidents are often worldwide or split by Microsoft cloud (Worldwide, GCC, DoD, China). Tenant-level impact is not public.

2. Known bug — is a fix date published?

No known bug with a published fix date right now.

No open incident in the last successful fetch.

3. Plain-English workaround

From experience

Microsoft does not publish tenant-level Microsoft 365 health as a public machine-readable feed. We poll the public Admin Center status RSS plus Microsoft's undocumented posts API. A green public board can still hide a problem that only shows in your admin centre. While you wait: try Outlook on the web from an InPrivate window, a different network, and a user in another site. If web works and the desktop client does not, it is the client — not Exchange Online.

4. Upstream or scheduled?

Vendors do not publish one shared dependency map. This list is the upstream tools we watch with this service.

Azure OperationalMicrosoft 365 control plane and many workloads sit on Azure.

Upcoming maintenance

No upcoming window in the vendor feed.

How to tell a Microsoft 365 outage from a local mess

The public board at status.cloud.microsoft is not the same as Service health inside admin.microsoft.com. We only repeat the public RSS and posts. A green public page can still hide a tenant-scoped incident that only your admins can see. That is a Microsoft design choice, not a gap we fill by guessing.

Error messages people paste into tickets

Something went wrong / 500 on office.com. If every user in every site hits it at the same minute, open the official status page and Azure. If it is one PC, clear the browser profile and try InPrivate.
We couldn't sign you in. That is usually Entra, Conditional Access, or a licence — not SharePoint. Check Entra ID next.
Your mailbox is temporarily unavailable. Classic Exchange wording. Confirm Outlook on the web for the same mailbox before you create a new desktop profile.
Need admin approval on a consent prompt. Not an outage. An admin must grant the app, or the user is on the wrong tenant.

End user vs admin

End users should prove three things: office.com in a private window, a colleague on a different network, and whether mail/chat/files fail together. Admins should open Service health, Message center, and the Entra sign-in logs. Do not tell the board "Microsoft is down" from one Outlook desktop.

Regions and clouds

Worldwide, GCC, GCC High, DoD and China are separate Microsoft clouds. A Worldwide incident is not a GCC incident. We print region text only when Microsoft published it.

Official pages: public status, Microsoft 365 admin centre, Azure portal.

What this page will not do

We will not show your tenant's Service health. That needs admin consent and the Microsoft Graph. We will not turn a single Outlook profile into a worldwide outage. If public RSS is quiet, say so. If Message center has a tenant post, only your admins can see it — send them there, do not invent a headline here.

When Azure is naming the same hour, open the Azure page. Control plane and many workloads sit there. Still wait for Microsoft to post a Microsoft 365 item before you tell customers "Exchange is down" from an Azure region title alone.

Check your side

Can you open https://www.office.com in a private window on the same PC?
Can a colleague on a different ISP or a phone hotspot sign in?
Admin: is there a Service health incident for Exchange, Teams, SharePoint or Entra in your tenant?
Any Conditional Access or geo-block that only hits this site?

Related guides

FAQ

Is Microsoft 365 down right now?: We only repeat what Microsoft posts publicly. If this page is quiet, check the official status page and — if you are an admin — Service health in the Microsoft 365 admin centre. A single user on one PC is usually cache, profile, or network, not a worldwide outage.
Why does Microsoft still look green when Microsoft 365 is broken for us?: Tenant-scoped incidents and Message Center posts are not public. Office staff cannot see them. That is a known gap, not a failure of this checker.
Is it them or us?: If webmail or another site on the same WAN works, and only one app or one profile fails, it is almost never a global outage. If every user in every site fails at the same minute, start with the vendor page and Azure.