Azure Portal Not Working? Here's How to Fix It

This sounds basic, but it catches people regularly, especially on enterprise machines where IT controls which browser versions are deployed. The Azure portal has an official list of supported browsers and devices, and running outside that list causes everything from cosmetic glitches to complete load failures.

Microsoft officially supports the latest two major versions of:

• Microsoft Edge (Chromium-based)
• Google Chrome
• Mozilla Firefox
• Apple Safari

Internet Explorer is not supported and hasn't been for years. If anyone in your organization is still hitting portal.azure.com via IE, that's the answer right there.

To check your browser version quickly:

• Edge: Navigate to edge://version in the address bar.
• Chrome: Navigate to chrome://version.
• Firefox: Go to Help → About Firefox.

If you're more than two major versions behind, update immediately. In Edge, go to Settings → Help and feedback → About Microsoft Edge and click Update if available. In Chrome, the three-dot menu → Help → About Google Chrome triggers an update check automatically.

One more thing worth checking: JavaScript must be enabled. The Azure portal is heavily JavaScript-dependent, nearly every element in the portal shell, the portal menu, the service menu, and the working pane renders through JavaScript. If JavaScript is disabled or restricted by a browser policy, you'll get a blank working pane with no error message. To verify in Chrome, go to Settings → Privacy and security → Site Settings → JavaScript and make sure it's set to "Sites can use JavaScript."

If this step fixes the Azure portal access issue, you should now see the full Home page after sign-in, including the list of recently visited resources and the Create a resource shortcut in the portal menu.

If your browser is up to date but the Azure portal is still showing blank screens, broken layouts, or a dashboard that won't load, clearing cached data is your next move. This is especially effective after Microsoft pushes a portal update, your browser holds onto old cached files that conflict with new portal code.

Here's the exact sequence for each major browser:

Microsoft Edge (recommended for Azure):

Settings → Privacy, search, and services
→ Clear browsing data → Choose what to clear
→ Select: Cached images and files, Cookies and other site data
→ Time range: All time
→ Click "Clear now"

Google Chrome:

Settings → Privacy and security → Clear browsing data
→ Advanced tab
→ Select: Browsing history, Cookies and other site data,
   Cached images and files
→ Time range: All time
→ Click "Clear data"

Firefox:

Settings → Privacy & Security
→ Cookies and Site Data → Clear Data
→ Check both: Cookies and Site Data + Cached Web Content
→ Click Clear

After clearing, completely close and reopen your browser, don't just open a new tab. Then navigate back to portal.azure.com and sign in. You'll be prompted to sign in fresh since your session cookies were cleared, which is expected and normal.

What you should see if it worked: the Azure portal Home page loads within a few seconds, your portal menu appears on the left side (either in flyout or docked mode depending on your previous preference), and your most recently visited resources show up in the main working pane. If the Home page loads but your dashboard looks empty or different, that's normal, your dashboard is stored server-side and will repopulate.

One nuance here: if you're signed into multiple Azure accounts or multiple Microsoft directories simultaneously, clearing cookies signs you out of all of them. Have your credentials ready before clearing.

If the portal loads but you can't see your resources, get an "Access denied" message, or the Home page looks empty with no recent resources listed, the issue isn't your browser at all, it's your account or subscription.

Start by verifying which account you're signed in with. Look at the top-right corner of the Azure portal header, that's the account element (key #7 in Microsoft's portal layout). Click it to see your display name, email address, and the currently active directory. If you manage resources across multiple tenants or directories, it's easy to land in the wrong one after a sign-in.

To switch directories from within the portal:

Click your account name (top-right) → Switch directory
→ Select the correct directory/tenant from the list
→ The portal will reload in that directory context

If you don't see a Switch directory option or the directory you need isn't listed, your account may not have been added as a guest or member to that tenant. You'll need to contact whoever manages that Azure tenant and ask them to verify your access through Microsoft Entra ID.

Next, check whether your subscription is active. A suspended, cancelled, or expired subscription causes the portal to load normally but show no resources. In the portal's global search bar (the search field in the page header, key #4), type "Subscriptions" and select the Subscriptions service. You'll see a list of all subscriptions your account can access, along with their current status.

If you see a subscription marked as "Disabled" or "Expired," that's your answer. Reactivating it requires navigating to that subscription and following the reactivation steps, or contacting your billing administrator.

If you're brand new to Azure and the Subscriptions list is empty, this is expected. As the official docs note: if you don't have an Azure subscription, you won't have resources to manage. You'll need to create a free account or have your organization's administrator add you to an existing subscription with the appropriate Azure role-based access control (RBAC) permissions.

One of the most confusing Azure portal problems is when the interface loads but navigation stops working, the portal menu doesn't respond, the service menu disappears, the breadcrumb navigation breaks, or the global search bar in the header returns no results. I've seen users spend an hour thinking their resources are gone when really they just can't navigate to them.

The Azure portal menu can operate in two modes: flyout mode (hidden until you click the menu icon) and docked mode (always visible on the left). If your portal menu has vanished entirely and you're used to seeing it docked, someone, or a browser glitch, may have toggled it to flyout mode. Look for the hamburger menu icon in the top-left area of the portal header and click it. That opens the flyout menu immediately.

To permanently change the portal menu back to docked mode:

Click Settings (gear icon in the page header, key #6 in portal layout)
→ Portal settings
→ Appearance + startup views
→ Portal menu behavior → Select "Docked"
→ Apply / Save

If the service menu is missing while you're working inside a specific resource (the left sidebar that shows resource-specific commands), try this: service menus default to collapsed within menu groups. Look for a small expand/collapse icon near the service icon at the top of the menu area. Clicking it toggles all folders between collapsed and expanded states.

For the global search not returning results, first check whether JavaScript is fully loaded, the search bar uses dynamic JavaScript to query Azure's resource graph in real time. If the search field exists but doesn't respond to typing, open your browser's Developer Tools (F12), click the Console tab, and look for any red JavaScript errors. Common culprits are Content Security Policy violations caused by browser extensions or corporate proxy injections.

If service menu preferences seem scrambled, the portal does preserve your menu group selections throughout sessions by resource type. If you suspect that saved state is corrupted, resetting your portal settings to defaults often clears it: Settings → Portal settings → Reset settings → Restore default settings.

Dashboards in the Azure portal give you a focused, customized view of your most important resources. When a dashboard breaks, tiles show errors, the dashboard loads blank, or it redirects to a default view you didn't set, it can feel like you've lost your whole workspace. The good news is that dashboards are stored server-side, so they're not actually gone; the issue is usually display or permission related.

Start by switching to the default dashboard. At the top of the portal page when you're on the Dashboard view, there's a dropdown selector showing the current dashboard name. Click it and select "My Dashboard" (Microsoft's built-in default). If that loads correctly, the issue is specific to your custom dashboard, not the portal itself.

If individual tiles on a dashboard show error states like "Couldn't load this tile" or "You don't have access to this resource," check two things:

1. Resource access: The tile may be pointing to a resource you no longer have RBAC permissions to view, or a resource that was deleted. Edit the tile (click the pencil/edit icon during dashboard edit mode) and point it to a resource you do have access to.
2. Subscription context: If the dashboard was built in one directory/tenant context and you're now viewing it from a different one, the resources it references won't resolve. Switch to the correct directory first.

To enter dashboard edit mode and clean up broken tiles:

Navigate to Dashboard (select Dashboard from the portal menu or Home)
→ Click "Edit" in the command bar at the top
→ Hover over broken tiles → Click the X to remove them
→ Drag new tiles from the Tile Gallery on the right
→ Click "Save" when done

If you want to start completely fresh, you can create a new dashboard from the portal menu → Dashboard → + Create a dashboard → Blank dashboard. Give it a name, add the tiles you need from the gallery, and save. Your old dashboards remain intact until you explicitly delete them, so there's no risk in creating a new one to test with.

One important tip for enterprise users: if your organization published a shared dashboard that appears in your list, you may not have edit permissions on it. Contact whoever published it, typically an Azure admin, to request changes, or create your own copy: while viewing the dashboard, click "Clone" from the command bar to get an editable copy under your own profile.