Is Microsoft Azure down?
Right now
No. Microsoft Azure is operational.
No incidents reported.
Read from azure.status.microsoft · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/azure/status.agent.json
MCP: upstream_status {"service":"azure"}
Azure status feed. Microsoft posts here only for broad incidents; tenant-level issues appear in Azure Service Health.
What Microsoft Azure reports
Operational
Taken as is from Microsoft Azure's own incident feed. Incident titles and component names below are theirs.
Open azure.status.microsoftUpButler's independent probe
There is no keyless endpoint of Microsoft Azure that says anything useful, so UpButler does not probe it. To check your own Microsoft Azure account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Microsoft Azure incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Microsoft Azure publishes for 90 days from the day it starts tracking a service.
Tell your outage from Microsoft Azure's
Declare that your project depends on Microsoft Azure. When one of your monitors fails while Microsoft Azure 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:
- azurecurl -s https://upbutler.com/status/azure/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "azure",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Microsoft Azure down right now?
- No. As of 2026-10-10 05:07 UTC, Microsoft Azure is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Microsoft Azure's own incident feed at https://azure.status.microsoft/en-us/status. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Microsoft Azure's words.
- How can my agent or app check Microsoft Azure status?
- Fetch https://upbutler.com/status/azure/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":"azure"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Microsoft Azure's?
- Add "azure" to the dependencies of your UpButler workspace. When one of your monitors fails while Microsoft Azure 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.
More in cloud and edge
UpButler is not affiliated with Microsoft Azure. Status and incident text belong to Microsoft Azure and are read from their public status source; the probe result is UpButler's own measurement.