Azure Portal service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
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
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.
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
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Where to report a Azure Portal problem
Use Service Health and Resource Health for account/resource detail when accessible.
Open Azure Portal help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Include these details in a Azure Portal 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 or 429 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: a step-by-step workflow
- Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
- Run the portal.azure.com check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
- Compare the relevant provider information. Open Azure Portal status and check whether the named service and incident time fit your error.
- Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.
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. Compare permitted network paths
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
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 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.