Azure Portal service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Is Azure Portal Down? Check portal.azure.com Status and Outages
Run a live reachability check for portal.azure.com. Compare the regional responses with the problem you see in Azure Portal.
Find Azure Portal help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Is Azure Portal working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding Azure Portal connection and service problems
The Azure portal can fail to render or sign in while deployed workloads remain available.
The checker above requests portal.azure.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Azure Portal action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For a cloud administration or security-console issue, compare the entrypoint involved in your actual workflow: Microsoft Defender status check, Azure status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse infrastructure checks.
Azure Portal status information and official help
Azure Portal help and reporting
Use Service Health and Resource Health for account/resource detail when accessible.
Open portal.azure.com
Open the website in your browser and compare it with the result above.
Where to report problems with Azure Portal
Open Azure Portal help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Portal blade URL, tenant/subscription, browser error, correlation ID and UTC time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Azure Portal.
What to check when Azure Portal is not working
These are troubleshooting comparisons, not claims that Azure Portal is currently experiencing a particular incident.
Start with the action that failed
Compare an existing workload's endpoint with the failing portal blade and record whether the shell or one resource view fails.
Narrow down the affected service
Consult Azure Status/Service Health; ask an authorised colleague to check the same subscription before changing access roles.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Azure Portal is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the portal.azure.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open Azure Portal status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If Azure Portal Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Azure Portal seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open portal.azure.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Azure Portal issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Azure Portal support.
Frequently asked questions about Azure Portal problems
Is Azure Portal down, or is the problem limited to one feature?
Run the portal.azure.com check and compare its original timestamps and responses with your actual error. The Azure portal can fail to render or sign in while deployed workloads remain available.
Where can I report a problem with Azure Portal?
Use the community buttons on this page to share whether the service works for you. For help from Azure Portal, use the official help/reporting resource linked above. Use Service Health and Resource Health for account/resource detail when accessible.
What should I check first when Azure Portal is not working?
Compare an existing workload's endpoint with the failing portal blade and record whether the shell or one resource view fails. Consult Azure Status/Service Health; ask an authorised colleague to check the same subscription before changing access roles.
What information helps Azure Portal support investigate?
Portal blade URL, tenant/subscription, browser error, correlation ID and UTC time.