Tenant fetching error

Question

Tenant fetching error

Eric Sun (ScreenBeam) 10

Starting today, I'm experiencing 'Tenant fetching error' with Azure portal services on one network. However, the issue does not occur on another network. Is the public IP address on my affected network being blocked by Azure?

Venkatesan S 9,225 Reputation points Microsoft External Staff Moderator

2026-06-15T22:58:14.7233333+00:00
Hi @Eric Sun (ScreenBeam)

Thanks for reaching out in Microsoft Q&A forum,

Starting today, I'm experiencing 'Tenant fetching error' with Azure portal services on one network. However, the issue does not occur on another network. Is the public IP address on my affected network being blocked by Azure? No, Azure is almost certainly not blocking your public IP address.

The "Tenant fetching error" only appearing on one network (while working on another) strongly indicates the problem is local to your affected network, not an Azure-side block. When Azure blocks an IP, the issue would affect all networks using that IP—not disappear when you switch networks.

Causes:

On your affected network, one of these is blocking Azure Portal communication:

Antivirus software — Avast and similar security tools are known to block https://management.azure.com/ and cause this exact error

Firewall rules — Corporate firewalls may block Azure Portal URLs or restrict access to certain regions (geoblocking)

Proxy server — Corporate proxy filtering Azure Portal traffic

SSL inspection — SSL decryption/scanning interfering with Azure authentication

Web filtering — Solutions blocking Azure endpoints

DNS issues — DNS resolution failing for Azure endpoints

Conditional Access policies — Azure Entra ID policies blocking portal access from specific networks

Steps:

Try a mobile hotspot — This bypasses your corporate network and confirms it's network-related

Check browser developer tools (F12) — Look for failed requests to management.azure.com, login.microsoftonline.com, or portal.azure.com

Test Azure CLI authentication — Run az login from the affected network to see if authentication works

Check antivirus — Add https://management.azure.com/* and https://portal.azure.com to your AV exceptions

Clear browser cookies/cache or try incognito/private mode

Disable ad blockers — They can interfere with portal requests

Check Entra ID sign-in logs — Look for authentication failures or Conditional Access blocks

You're seeing "Tenant fetching error" instead of "Request is blocked" or a timeout. The issue works on one network but fails on another which wouldn't happen if Azure blocked your IP. Azure-side IP blocks affect all networks using that IP, not just one. Since it works from another network, focus your troubleshooting on your affected network's security controls first.

Reference:

Allow the Azure portal URLs on your firewall or proxy server - Azure portal | Microsoft Learn

Sign-in logs in Microsoft Entra ID - Microsoft Entra ID | Microsoft Learn

Microsoft Entra Conditional Access: Zero Trust Policy Engine - Microsoft Entra ID | Microsoft Learn

How to troubleshoot sign-in errors - Microsoft Entra ID | Microsoft Learn

Kindly let us know if the above helps or you need further assistance on this issue.

Please “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Eric Sun (ScreenBeam) 10 Reputation points

2026-06-16T00:03:47.98+00:00

Venkatesan,

Thanks for the response and appreciate the answers! However, what I experienced was actually that the issue occurred on networks behind one public IP address but not on networks behind another public IP address. I'd appreciate if you could advise accordingly. Thanks!
Venkatesan S 9,225 Reputation points Microsoft External Staff Moderator

2026-06-17T17:51:59.9166667+00:00

Hi @Eric Sun (ScreenBeam)

We haven’t heard back from you regarding our last response and wanted to check if you had the opportunity to review our previous post.

Please “up-vote” if the information helped you. This will help us and others in the community as well.

Answer accepted by question author

0 additional answers

Your answer

Eric Sun (ScreenBeam) 10 Reputation points

2026-06-16T00:03:47.98+00:00

Venkatesan,

Thanks for the response and appreciate the answers! However, what I experienced was actually that the issue occurred on networks behind one public IP address but not on networks behind another public IP address. I'd appreciate if you could advise accordingly. Thanks!
Venkatesan S 9,225 Reputation points Microsoft External Staff Moderator

2026-06-17T17:51:59.9166667+00:00

Hi @Eric Sun (ScreenBeam)

We haven’t heard back from you regarding our last response and wanted to check if you had the opportunity to review our previous post.

Please “up-vote” if the information helped you. This will help us and others in the community as well.

Answer 1

Hi @Eric Sun (ScreenBeam)

Thank you for the clarification,

Since the issue consistently happens on all networks behind one public IP address but works on all networks behind a different public IP, the public IP address itself is now a key factor to investigate.

While Microsoft doesn't typically block customer public IPs from accessing the Azure portal, it is possible that access is being affected by:

Conditional Access policies — Your organization may have restrictions based on IP address or location
Reputation-based filtering — Azure or your ISP may flag the IP due to reputation issues
Network security devices — Firewalls, proxies, or SSL inspection blocking Azure endpoints from that IP
Microsoft-side restrictions — Rare, but excessive failed attempts could trigger temporary rate limiting

Next Steps to Diagnose:

Check Entra ID sign-in logs — Look for failed sign-in attempts from the affected public IP. Check if Conditional Access policies are blocking access based on location or IP
Test Azure CLI authentication — Run az login from both public IPs and compare results. This tests authentication at the API level, independent of the browser
Capture browser network trace (F12) — Open Developer Tools, reproduce the error, and check which Azure endpoints (portal.azure.com, login.microsoftonline.com, management.azure.com) are failing
Verify network security configs — Confirm traffic from the affected IP isn't being filtered or inspected differently by firewalls, proxies, or SSL inspection tools
Try a VPN or different ISP temporarily — If another public IP works immediately, this confirms the original IP is the issue

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Eric Sun (ScreenBeam) 10 Reputation points

2026-06-17T18:55:18.3566667+00:00

Hi Venkatesan,

We didn't find any issues on our end and the access to Azure services from the affected networks resumed later on 6/15. We've been monitoring and the issue has not reoccurred since then. Thank you for your support!
Venkatesan S 9,225 Reputation points Microsoft External Staff Moderator

2026-06-17T18:57:51.88+00:00

Hi @Eric Sun (ScreenBeam)

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Share via

Tenant fetching error

0 additional answers

Your answer