Share via

Unable to login in Foundry Portal

Diaz 0 Reputation points
2026-06-04T09:07:36.16+00:00

I am unable to login in Foundry Portal. It stays forever as "Loading"

User's image

Foundry Models
Foundry Models

A catalog of AI models in Microsoft Foundry that you can discover, compare, and deploy using Azure’s built‑in tools for evaluation, fine‑tuning, and inference

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jerald Felix 13,255 Reputation points Volunteer Moderator
    2026-06-04T10:26:20.7733333+00:00

    Hello Diaz,

    Greetings! Thanks for raising this question in Q&A forum.

    The "Loading" hang on the Azure AI Foundry Portal (https://ai.azure.com) is most commonly caused by one of these reasons a stale browser session or cached authentication token, a browser extension interfering with the portal's JavaScript, a conditional access or firewall policy blocking certain portal endpoints, or a missing/incomplete Azure subscription or hub setup that the portal is trying to load in the background and timing out on.

    Here are the steps to resolve this:

    Start by opening the Foundry Portal in a fresh InPrivate or Incognito browser window and try logging in again at https://ai.azure.com. This rules out any cached session or extension interference immediately.

    If the InPrivate window also gets stuck on "Loading", try a different browser entirely (for example, switch from Edge to Chrome or vice versa) to isolate whether it's a browser-specific issue.

    Clear your browser's cache and cookies completely, then close and reopen the browser before trying again.

    Disable any browser extensions such as ad blockers, script blockers, or VPN extensions temporarily, as these can block the portal's authentication scripts from completing.

    Check if your organization has Conditional Access policies that may be blocking access to ai.azure.com or related Microsoft endpoints. If you're on a corporate network, try switching to a personal network or mobile hotspot to see if the portal loads.

    Make sure the Microsoft account you're using has an active Azure subscription and that you have been assigned at least Contributor or Owner role on the subscription or resource group. If your account has no subscription access, the portal may hang indefinitely while trying to enumerate resources.

    Check the Azure Service Health page at https://status.azure.com to see if there is an ongoing incident affecting Azure AI Foundry or the AI services in your region.

    If none of the above helps, try accessing the portal using a direct deep link to your specific hub, such as https://ai.azure.com/resource/<your-hub-name>, which sometimes bypasses the loading issue caused by the portal trying to enumerate all resources.

    As a last resort, open your browser's Developer Tools (F12), go to the Console or Network tab, reproduce the loading hang, and capture any error messages or failed network requests. Share those details when raising an Azure Support ticket — they will help the support team pinpoint the exact cause quickly.

    If this answer helps you kindly accept the answer which will help others who have similar questions.

    Best Regards,

    Jerald Felix.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-04T09:07:55.82+00:00

    When the Foundry portal hangs on “Loading” during sign-in or project load, the most common causes in the provided context are:

    1. Network restrictions (public access disabled or IP not allowed).
    2. Private endpoint / DNS connectivity issues.

    Use these checks from a machine where the browser is running:

    1. Verify whether the Foundry hub allows your network:
      • If the hub’s public network access is Disabled, access must come through a private endpoint from your virtual network (via VPN, ExpressRoute, or Bastion). If trying to access directly from the internet, the portal will not load.
      • If public network access is Enable from selected IPs, ensure the current public IP is added to Firewall IP ranges allowed to access Foundry. If not, an admin must add it.
    2. If the hub uses a private endpoint, validate private connectivity:
      • From a machine joined to the same virtual network, run: 
             # Replace with your Foundry hub FQDN from the private endpoint DNS config
     $fqdn = "<your-workspace-id>.workspace.<region>.api.azureml.ms"
     
     nslookup $fqdn
     Test-NetConnection -ComputerName $fqdn -Port 443
      • Expected:
        • nslookup returns a private IP (for example, 10.0.0.4).
        • Test-NetConnection shows TcpTestSucceeded: True.
      • If DNS resolves to a public IP, fails, or TcpTestSucceeded is False, there is a private endpoint or DNS/firewall misconfiguration that an admin must fix.

    If these checks fail, adjust the hub’s public access/firewall settings or correct the private endpoint and DNS configuration, then retry logging into the Foundry portal.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.