Is Microsoft 365 down?
Microsoft 365 is up
Right now
No. Microsoft 365 Microsoft Graph answers UpButler's independent probe; no machine-readable official status.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/microsoft-365/status.agent.json
MCP: upstream_status {"service":"microsoft-365"}
Outlook, Teams, SharePoint and Microsoft Graph. Tenant-level health is in the admin center; the public page is not machine-readable.
What Microsoft 365 says
status.cloud.microsoft has no public JSON API or feed we may read; only the independent probe is shown.
Their site: status.cloud.microsoftWhat UpButler measured
Microsoft Graph is answeringHTTP 401 · 212 ms
One request without credentials to graph.microsoft.com every two minutes, from eu-central (one location, not a global view). An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 06:09 UTC
Microsoft 365 incidents, last 90 days
Without a machine-readable source there is no incident history to show. Microsoft 365 keeps its own at status.cloud.microsoft.
Get alerted when Microsoft 365 goes down
No account. One email when our probe cannot reach Microsoft 365 for several minutes, one when it can again. You confirm the address first, and every email has a one-click unsubscribe.
On UpButler? Add Microsoft 365 as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Microsoft 365's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/microsoft-365)Tell your outage from Microsoft 365's
Declare that your project depends on Microsoft 365. When one of your monitors fails while Microsoft 365 has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- microsoft-365curl -s https://upbutler.com/status/microsoft-365/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "microsoft-365",
"verdict": "proceed",
"status": "operational",
"reason": "Microsoft 365 Microsoft Graph answers UpButler's independent probe; no machine-readable official status",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Microsoft 365 down right now?
- No. As of 2026-10-10 07:17 UTC, Microsoft 365 is up. This page reads the status again every 2 minutes.
- Where does this status come from?
- status.cloud.microsoft has no public JSON API or feed we may read; only the independent probe is shown.
- What does UpButler's own Microsoft 365 check prove?
- Every two minutes UpButler sends one request without credentials to the Microsoft 365 Microsoft Graph (graph.microsoft.com) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
- How can my agent or app check Microsoft 365 status?
- Fetch https://upbutler.com/status/microsoft-365/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"microsoft-365"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Microsoft 365's?
- Add "microsoft-365" to the dependencies of your UpButler workspace. When one of your monitors fails while Microsoft 365 has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Microsoft 365. Status and incident text belong to Microsoft 365 and are read from their public status source; the probe result is UpButler's own measurement.