From Azure status RSS, Azure status history (PIRs). Times in Eastern (ET).
No active incidents reported by Microsoft Azure
Checked Nov 18, 9:39 PM EST · official feed, refreshed every 10 minutes
Microsoft Azure does not publish a public per-region component list; when an incident is open, its regions and services appear on the incident above.
Our 5-minute checks · last 7 days
We read Microsoft Azure'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
100%Thu 11/12
100%Fri 11/13
100%Sat 11/14
100%Sun 11/15
100%Mon 11/16
100%Tue 11/17
100%Wed 11/18
No problems flagged by our checks in this window.
Incident history
Incidents per month from the official feed, by severity. Azure publishes Post Incident Reviews for broad issues and keeps them five years; the public page lists the most recent months. 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 Azure's own report states one, quoting the sentence. The category is our label for that sentence; anything else is marked Unconfirmed / not yet disclosed.
Config / deploy error: 1
AI / automation: 1
Sep 30, 2026
Network Connectivity – Gateway service degradation in multiple regions
Config / deploy error
“These updates are designed to roll out gradually across deployment stages and redundant gateway instances, allowing service health to be evaluated before updates proceed.” — Microsoft Azure PIR
Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services – Intermittent request failures and latency in Sweden Central
AI / automation
“When requests are made to Azure OpenAI Service and related Azure AI services in a region, the service relies on a regional backend service to retrieve resource metadata and configuration information for the account making the request.” — Microsoft Azure PIR
The big ones, with the cause in the official write-up's own words.
Oct 29, 2025
Azure Front Door: connectivity issues across multiple regions
Config / deploy error
“Microsoft's PIR traces it to a specific sequence of customer configuration changes on the Azure Front Door control plane, which is deployed globally to all edge sites.”
Impact: Sites and Microsoft services fronted by Azure Front Door, including management portals, failed to load.
CrowdStrike update crashes Windows machines, including Azure VMs
Third-party dependency
“CrowdStrike, an independent cybersecurity company, released a software update that began impacting IT systems globally… CrowdStrike's update affected 8.5 million Windows devices.”
Impact: Windows VMs and PCs running CrowdStrike Falcon crashed worldwide. Microsoft said this was not a Microsoft incident.
Storage: impact to multiple services in Central US
Config / deploy error
“Microsoft's PIR says an update to the Storage 'allow list' of VM host addresses was published incorrectly, so Storage rejected disk reads and writes from VMs.”
Impact: VMs and the services built on them in Central US, with knock-on effects on Microsoft 365.
“A network engineer was performing an operational task to add network capacity to the global Wide Area Network (WAN) in Madrid… The task included steps to modify the IP address for each new router.”
Impact: Network connectivity problems across Azure regions and Microsoft 365 (Teams, Outlook).
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 Azure, 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 Azure 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 Azure 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 Azure publishes them.
Phone supportMicrosoft lists support phone numbers by country on its official page: Global customer service phone numbers. Azure technical cases are opened in the portal.