Azure Login Issue

Hello Batman,

Kindly share your email, timezone and availability in private chat for us to discuss on the issue?

Use targeted portal troubleshooting and collect data for support, since browser-level steps are already done.

1. Verify portal access and directory/subscription
   • If the portal page hangs or fails to load, try again with:
     • A different browser than already used, if available.
     • Private browsing mode (InPrivate/Incognito) as described in the sign‑in troubleshooting guidance.
   • After a successful load (if it works intermittently), confirm the correct directory is selected from the account menu in the top-right. An incorrect directory can lead to follow‑on errors like No subscriptions found even when sign‑in succeeds.
2. Check for sign‑in or tenant issues
   • If the error appears during or immediately after sign‑in, confirm that the tenant is not blocked or inactive. Inactivity can cause tenant blocks that prevent normal portal usage and sign‑in.
   • If a message such as No subscriptions found appears once the portal loads, switch to the correct directory and ensure the account has at least Owner access on a subscription.
3. Confirm network/firewall/proxy allow‑listing
   • Even if there is no explicit proxy configured in the browser, upstream firewalls or secure web gateways can block required Azure portal endpoints and cause LoadFailed behavior.
   • Ensure that the URLs required for the Azure portal are allowed (for example, authentication endpoints like login.microsoftonline.com and portal framework endpoints such as *.portal.azure.com, management.azure.com, and related FQDNs). Missing access to these can cause the shell to fail to load.
4. Capture diagnostics for Microsoft support If the issue persists after confirming the above, collect detailed diagnostics before opening a support request: a. Capture a browser trace
   • In Edge or Chrome:
     1. Sign in to the Azure portal first.
     2. Press F12 to open DevTools.
     3. On the Console tab, enable Preserve log.
     4. On the Network tab, enable Preserve log.
     5. Stop recording and Clear the Network log.
     6. Start recording again, then reproduce the LoadFailed – TypeError issue.
   • In Firefox, use DevTools with Persist Logs enabled on both Console and Network, then reproduce the issue and save the HAR file.
   b. Capture portal session diagnostics
   • In an active portal session (if it loads at least partially), press Ctrl + Alt + A to generate PortalDiagnostics.json and save it.
   c. Include both the HAR trace and PortalDiagnostics.json when opening an Azure support request so the portal team can correlate with the Browser ID and identify the failing script or call.
5. If still blocked from any portal access
   • If the portal never loads far enough to capture PortalDiagnostics.json, rely on the HAR trace plus screenshots (like the one already captured) and open a support request directly from the Azure support site, referencing the Browser ID shown on the error page.

References:

• Troubleshoot Azure subscription sign-in issues
• Capture a browser trace for troubleshooting
• Capture an Azure portal browser trace in Microsoft Edge
• Capture an Azure portal browser trace in Google Chrome
• Capture an Azure portal browser trace in Firefox
• Allow the Azure portal URLs on your firewall or proxy server
• No subscriptions found sign in error for Azure portal