projectkudu / AzureResourceExplorer

Azure Resource Explorer - a site to explore and manage your ARM resources in style

Home Page:https://resources.azure.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Can not find Change Directory/Tenant option

IronSean opened this issue · comments

I can not find any options to change AD Directory, and the only relevant issue (#333) is closed with no examples of where to find it.

Hi,
I confirm that I've the same issue, the dropdown select list is empty ->
image

And if I check F12 console, I can see a 500 on https://resources.azure.com/api/tenants
image

I'm still not be able to use the tool cross tenants

Thank you
Regards
Alexandre

Investigating..

Just checked and seems to be fine now. Could you also check please. @IronSean @alex-3sr

There was definitely some intermittent issue over the weekend as we had multiple reports so we will continue to investigate and understand the issue.

Hi,

Thanks for this quick reply. At this time, I still have issue, maybe need wait a bit (if CDN cache, etc..). I tried with inprivate browsing, same issue.

I've to add, that my account has many many several tenants (maybe more than 30 or 40, never count them). And already have issue on Azure Devops for example, when service connection wizard tried to list all subcriptions in all tenants, and finish in timeout. So, don't know if it can help you but I think it could be interesting to precise that I have several tenants on my accounts.

Thanks,
Alex

For complet my previous comment, I just did a (Get-AzTenant).count and got 51. I know that there are a 50 limit subscription display, maybe a same limitation on tenant too ?

commented

I do have the same issue - But I am only member of 2 tenants.
image

Seems that the backend has been turned off - this is the message I receive when I try to access https://resources.azure.com/api/tenants directly.
image

Edit:
The issue can be workarounded if you know your exact tenant name: https://resources.azure.com/@tenantname.onmicrosoft.com

Yes, I can also repro this now. Will post an update soon. Thanks.

Update - We understand the issue and also why it was failing transiently. Fix deployment might take a few more days though.

Update - We understand the issue and also why it was failing transiently. Fix deployment might take a few more days though.

I'm still experiencing this problem.

Hi everyone, I can confirm that issue still exist here too :(
I'm able to workaround it, by using LightHouse, but I don't have all remote tenants associated with LightHouse, So i really need it working as expected

Sorry. missed updating and resolving this thread. the fix was deployed by April 8 and verified using the local repro that was failing earlier.
If this is still failing it must be a different issue. Please open a separate issue to avoid confusion.