Microsoft Azure outages and problems
User reports, last 24 hours
57 reports in total, counted in 15-minute windows
In the last hour, 4 problem reports came in for Microsoft Azure, against about 3 at this time on a usual day. Over the last 24 hours there were 57 reports. Worldwide, most recent reports were about server connection (25%) and API (25%). The last spike in reports was 32 h ago and lasted 30 min. These are user reports from the US, where most people report Microsoft Azure problems.
Around the world right now: normal in 71 other countries. Most reports in the last hour: Brazil 1 · Mexico 1. By country
- NormalClose to the usual level24 h · 57 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAbout 3 an hour now
In the past 24 hours, 57 user reports came in for Microsoft Azure. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 3 reports, about 11 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Microsoft Azure in November 2026
- Problem reports in November
- 17,033
- Outage spikes
- 13
- Periods of elevated reports
- 23
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Microsoft Azure worldwide.
Share of 4 recent reports that said what was wrong, from every country listed below.
Microsoft Azure reports around the world
In the last 24 hours, 146 problem reports about Microsoft Azure came in from 27 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 3 | 59 |
| Brazil | Normal | 1 | 25 |
| Mexico | Normal | 1 | 3 |
| The UK | Normal | 0 | 12 |
| India | Normal | 0 | 9 |
| Japan | Normal | 0 | 6 |
| Germany | Normal | 0 | 5 |
| Australia | Normal | 0 | 2 |
| The Netherlands | Normal | 0 | 2 |
| Portugal | Normal | 0 | 2 |
| Italy | Normal | 0 | 2 |
| Pakistan | Normal | 0 | 2 |
Each country's status compares its reports with the usual level there. 60 more countries had 17 reports in the last 24 hours. Map outlines: Natural Earth.
Microsoft Azure problem spikes, last 30 days
In the last 30 days, Microsoft Azure had 16 outage spikes and 32 periods of elevated reports. The longest lasted 15 h 13 min, on 13 November.
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 5 reports
- Tue 27 Oct: 25 reports (outage spike that day)
- Wed 28 Oct: 177 reports (outage spike that day)
- Thu 29 Oct: 329 reports (elevated reports that day)
- Fri 30 Oct: 322 reports (outage spike that day)
- Sat 31 Oct: 49 reports
- Sun 1 Nov: 36 reports
- Mon 2 Nov: 264 reports (elevated reports that day)
- Tue 3 Nov: 350 reports (outage spike that day)
- Wed 4 Nov: 271 reports (elevated reports that day)
- Thu 5 Nov: 205 reports
- Fri 6 Nov: 203 reports
- Sat 7 Nov: 34 reports
- Sun 8 Nov: 25 reports
- Mon 9 Nov: 252 reports (outage spike that day)
- Tue 10 Nov: 207 reports
- Wed 11 Nov: 730 reports (outage spike that day)
- Thu 12 Nov: 8,087 reports (outage spike that day)
- Fri 13 Nov: 2,625 reports (outage spike that day)
- Sat 14 Nov: 315 reports (elevated reports that day)
- Sun 15 Nov: 109 reports
- Mon 16 Nov: 814 reports (outage spike that day)
- Tue 17 Nov: 894 reports (outage spike that day)
- Wed 18 Nov: 692 reports (outage spike that day)
- Thu 19 Nov: 491 reports (outage spike that day)
- Fri 20 Nov: 327 reports (outage spike that day)
- Sat 21 Nov: 82 reports
- Sun 22 Nov: 20 reports
-
Outage
Fri 20 Nov, 21:45–22:15Lasted 30 min28peak reports
-
Elevated reports
Fri 20 Nov, 20:35–20:50Lasted 15 min13peak reports
-
Elevated reports
Fri 20 Nov, 14:51–15:11Lasted 20 min13peak reports
-
Outage
Thu 19 Nov, 20:47–23:27Lasted 2 h 39 min18peak reports
-
Elevated reports
Thu 19 Nov, 18:27–20:00Lasted 1 h 33 min19peak reports
-
Elevated reports
Thu 19 Nov, 17:37–17:59Lasted 22 min15peak reports
-
Elevated reports
Thu 19 Nov, 16:30–17:11Lasted 41 min18peak reports
-
Elevated reports
Thu 19 Nov, 15:32–15:58Lasted 26 min15peak reports
40 earlier spikes in this period.
By country
In the last 25 days, most Microsoft Azure problem reports came from the US (17,928), Brazil (5,640) and the UK (3,483). The US had the most days at outage level: 5 of 25. The latest outage spike was on Wednesday 18 November, in the US.
- The US5 outage days · 5 elevated17,928
- Brazil3 outage days · 1 elevated5,640
- The UK3 outage days3,483
- Japan2 outage days2,314
- India2 outage days1,633
- Canada1 outage day1,510
- Poland1 outage day954
- Mexico1 outage day904
- Outage spike
- Elevated reports
- Normal
- No data yet
Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 29 October 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. Monthly reports for all services
How to fix Microsoft Azure not working
Microsoft Azure is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach azure.microsoft.com over your own connection, right now. Nothing is sent to us or stored.
Open Service Health in the Azure portal
Start with Service Health. Type Service Health in the top search bar of the Azure portal and open Resource health to see if your region or subscription has a known outage.
Switch Azure directories after a full sign out
You may sit in the wrong tenant. Click your profile icon in the top right of the portal and choose Switch directory, because your login can stick to a tenant without access to the subscription you need.
Reload the Azure portal in an InPrivate window
A stuck blade often means local cache. Press Ctrl Shift Delete in Edge or Chrome, clear cached images for the last day, then you open an InPrivate window and sign in again to reload the portal shell.
Check Resource Health and restart the VM
If the portal loads but the VM hangs. Open the VM in the portal, select Resource health under Help in the left menu, read the status, and use Restart at the top when it points to a platform fault you cannot clear with a fresh login.
While Microsoft Azure is down: what to use instead
- Azure CLI or PowerShell When the portal hangs on a blank blade or keeps spinning, the az command line and Azure PowerShell talk to the management API directly, so you can often still restart, scale or inspect resources from a terminal.
- A paired region If you set up geo-replication, fail over to your secondary region.
- AWS or Google Cloud For a static site or a small stateless app, you can push a copy to another cloud and point DNS at it until things recover, and a low TTL on that record makes the switch much faster.
- The Azure mobile app On iOS or Android it lets you check resource health and restart a VM when the browser portal won't load.
Fix Microsoft Azure on Windows, Mac, Android and iPhone
Microsoft Azure on Windows
- Fix
- Clear your web browser's cache and cookies, or disable any active VPNs and proxies that might block the Microsoft Azure portal. If using Azure CLI or PowerShell, ensure your network allows traffic to Azure management endpoints.
- Check
- Attempt to sign in to the Microsoft Azure Portal via a web browser or check the official Azure Status page for ongoing regional outages.
ping azure.microsoft.comTest whether Microsoft Azure's servers replynslookup azure.microsoft.comCheck that Microsoft Azure's DNS resolvestracert azure.microsoft.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadMicrosoft Azure on Mac
- Fix
- Clear your browser cache, try accessing the Microsoft Azure portal in an incognito window, or temporarily disable your firewall. Ensure your Mac's keychain credentials for Azure CLI are not corrupted.
- Check
- Try loading the Microsoft Azure portal in Safari or Chrome, or run a basic network diagnostic to Azure's endpoints.
ping -c 4 azure.microsoft.comTest whether Microsoft Azure's servers replynslookup azure.microsoft.comCheck that Microsoft Azure's DNS resolvestraceroute azure.microsoft.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadMicrosoft Azure on Android
- Fix
- Force close the Microsoft Azure app, clear its cache in your device settings, and check for updates in the Google Play Store. Switching from Wi-Fi to mobile data can also resolve local connection issues.
- Check
- Open the Microsoft Azure app to see if it loads your resources or displays a connection error. You can also check the Azure Status website using a mobile browser.
Microsoft Azure on iPhone and iPad
- Fix
- Restart the Microsoft Azure app, or reinstall it from the App Store to clear corrupt local data. Ensure that cellular data is enabled for the app and disable any active VPNs in your iOS settings.
- Check
- Launch the Microsoft Azure app to check if you can access your dashboard. If it fails to load, check the Azure Status page in Safari to see if there is a global service outage.
Biggest Microsoft Azure problems so far
-
1
899reports in 15 min
-
2
195reports in 15 min
-
3
OutageLasted 4 h 18 min55reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as Microsoft Azure
In the last 30 days, all 48 of Microsoft Azure's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- ADP46 times
- Microsoft 36537 times
- Starbucks36 times
- GitHub36 times
- Microsoft Teams35 times
- Capital One35 times
How many of Microsoft Azure's spikes overlapped one of theirs.
During the latest spike
Microsoft Azure: Fri 20 Nov, 21:45 to 22:15
- Microsoft Outlook, outage,12 Nov 17:42 to 21 Nov 13:37
- PlayStation Network, outage,17 Nov 09:05 to 21 Nov 01:17
- Salt, outage,06:59 to 23:55
- Chase, outage,11:43 to 21 Nov 06:50
- Zelle, outage,11:49 to 21 Nov 01:52
- Rabobank, outage,11:54 to 21 Nov 00:07
- Yahoo Mail, outage,12:39 to 23:05
- Microsoft 365, outage,12:45 to 21 Nov 12:34
104 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Microsoft Azure problems
The busiest hour for reports about Microsoft Azure is 16:00 to 17:00 Central European time, and the busiest day is Thursday.
By hour of the day
- 00:00 to 01:00: 3.8 reports on an average day
- 01:00 to 02:00: 3.2 reports on an average day
- 02:00 to 03:00: 3 reports on an average day
- 03:00 to 04:00: 2.6 reports on an average day
- 04:00 to 05:00: 2.6 reports on an average day
- 05:00 to 06:00: 1.9 reports on an average day
- 06:00 to 07:00: 1.6 reports on an average day
- 07:00 to 08:00: 0.95 reports on an average day
- 08:00 to 09:00: 0.65 reports on an average day
- 09:00 to 10:00: 1.3 reports on an average day
- 10:00 to 11:00: 1.6 reports on an average day
- 11:00 to 12:00: 1.5 reports on an average day
- 12:00 to 13:00: 1.3 reports on an average day
- 13:00 to 14:00: 2.8 reports on an average day
- 14:00 to 15:00: 6.2 reports on an average day
- 15:00 to 16:00: 8.2 reports on an average day
- 16:00 to 17:00: 12 reports on an average day
- 17:00 to 18:00: 12 reports on an average day
- 18:00 to 19:00: 11 reports on an average day
- 19:00 to 20:00: 8.4 reports on an average day
- 20:00 to 21:00: 7.3 reports on an average day
- 21:00 to 22:00: 6.8 reports on an average day
- 22:00 to 23:00: 4.6 reports on an average day
- 23:00 to 00:00: 4.3 reports on an average day
By day of the week
- Monday: 129 reports on an average Monday
- Tuesday: 131 reports on an average Tuesday
- Wednesday: 132 reports on an average Wednesday
- Thursday: 161 reports on an average Thursday
- Friday: 134 reports on an average Friday
- Saturday: 51 reports on an average Saturday
- Sunday: 30 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 43 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Microsoft Azure goes down
Microsoft Azure hosts apps. Teams run virtual machines and databases on it, so when it slips you lose portal access while your own sites backed by App Service drop.
You see logins fail. Portal sessions hang or drop you back to sign-in because Entra ID cannot validate you, while virtual machines stay up but you cannot launch more. Damage stays regional, so your app in one zone fails while another zone answers. You can check the official status page for region faults and open a ticket through the help centre.
Microsoft Azure IP address, servers and network
- IPv4 address
- 72.246.30.122
- IPv6 addresses
- 2a02:26f0:ab00:3a2::439b
Show all 2
- 2a02:26f0:ab00:3b8::439b
- Network
- AS16625 · Akamai Technologies, Inc., registered in the United States
- Served through
- Microsoft Azure Front Door
- DNS hosted by
- Microsoft Azure DNS
- HTTPS certificate
- Issued by Microsoft Corporation, valid until 2 Apr 2027 (131 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 161 ms
Checked from our server in Frankfurt, Germany, 31 h ago, for azure.microsoft.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
11 of 12 locations got an answer from azure.microsoft.com. Fastest from Tokyo (19 ms), slowest from Los Angeles (1,003 ms). Every location connected through Akamai Technologies, Inc. (AS16625), using 11 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 45 ms | 88.221.170.73 |
| ViennaAustria | Up · HTTP 301 | 51 ms | 23.217.50.139 |
| MilanItaly | Up · HTTP 301 | 24 ms | 184.25.54.178 |
| ParisFrance | Up · HTTP 301 | 26 ms | 23.58.194.13 |
| AmsterdamNetherlands | Up · HTTP 301 | 21 ms | 184.30.157.190 |
| MadridSpain | Up · HTTP 301 | 30 ms | 23.46.86.177 |
| WarsawPoland | Up · HTTP 301 | 62 ms | 23.197.162.180 |
| DallasUSA | Up · HTTP 301 | 22 ms | 23.220.200.180 |
| Los AngelesUSA | Up · HTTP 301 | 1,003 ms | 23.12.158.170 |
| São PauloBrazil | No result | – | – |
| SingaporeSingapore | Up · HTTP 301 | 28 ms | 104.83.198.70 |
| TokyoJapan | Up · HTTP 301 | 19 ms | 23.35.102.71 |
Checked with check-host.net from its servers in these cities 31 h ago, for azure.microsoft.com. Time is how long each server took to load the page.
Microsoft Azure FAQ
Is Microsoft Azure down right now?
Why can't I sign in to the Azure portal?
What do I do when my Azure virtual machine stays unavailable?
How do I tell if a region issue broke my Azure web app?
Can a disabled Azure subscription take down running resources?
Service updates from @Azure
No posts about problems from @Azure in the last 14 days. The latest is from .
Contact Microsoft Azure support
- Official status pageazure.status.microsoft/en-us/status
- Help centreazure.microsoft.com/support
- Contact formazure.microsoft.com/support/contact
- Websiteazure.microsoft.com
- X (Twitter)x.com/Azure
Tip: when Microsoft Azure is down, its official status page is the quickest way to confirm the cause and see when a fix is expected.
About Microsoft Azure
- Category
- Cloud Platform
- Country
- United States
How we track Microsoft Azure
The status on this page comes from user-submitted problem reports for Microsoft Azure, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Microsoft Azure, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Microsoft Azure's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.