This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 99%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
az login hangs,
if/when it finally works, then other az commands timeout, e.g., az group list
The portal reports: An error occured [sic] when trying to fetch resources. Additional details from the underlying API that might be helpful: ajaxExtended call failed
I'm in westus3
BTW, your "tags" requirement is useless. I cannot determine what tags may make sense, so these are random.
Azure is not down.
I'd suggest just trying again.
You will find that occasionally a resource becomes unavailable for a short period of time.
It has been this way for 3 hours.
I've tried 2 different accounts.
From two different machines.
Of course there may be something wrong with my accounts, and the poor error handing masks that. All I see is a hang on "az login", after logging into the portal and doing the 2 factor tricks. The cli just hangs.
And the portal reports: An error occured [sic] when trying to fetch resources. Additional details from the underlying API that might be helpful: ajaxExtended call failed
Tried using --use-device-code with same results. Logs into the portal, cli hangs.
The --verbose option shows:
Finding subscriptions under tenant 823d305b-ddd7-4e81-903a-c7d6615c6c1e 'Default Directory'
It never returns. from that.
It is still hanging. Portal pages also timeout, e.g., https://portal.azure.com/#view/HubsExtension/BrowseResourceGroups
Perhaps it is something about my institution's network. Authenticating to the portal works fine. And forms appear, e.g., when trying to create a resource group. But they end up timing out while loading the default region.
Confirmed access is fine from another network. I suspect the problem is related to my institution being a MS captive, and my Azure account is not tied to that institution account. Perhaps a subscriber ID mismatch. For whatever reason, access to the Azure portal is limited from the institution's network, .e.g., it fails when looking up resources.
I can now reach the Azure portal via the institution's network. No idea who changed what.