search

projectkudu / AzureResourceExplorer

Azure Resource Explorer - a site to explore and manage your ARM resources in style
https://resources.azure.com
Apache License 2.0
197 stars 76 forks source link

Access to resources.azure.com was denied #350

Closed manuelcprosa closed 1 year ago

manuelcprosa commented 1 year ago

Hi team,

It seems that the access to Resources.azure.com is showing the following error: "Access to resources.azure.com was denied".

Was the service discontinued? Thanks!

ryanborMSFT commented 1 year ago

Hey there @manuelcprosa, thanks for the heads up. We are seeing this internally as well. I'm reaching out to the owning team now to get this sorted - Stay tuned.

el-pato commented 1 year ago

Experiencing same thing here. Didn't get any email alerts, https://status.azure.com is all green, and no relevant entries in the service health dashboard in Azure.

Some more information, in case it's relevant: I am trying to upgrade a Function's runtime to .net6, which can be done via the Azure Resource Explorer or the Azure CLI. Since the resource explorer appears to be down, I tried the relevant Azure CLI command

az functionapp config set --net-framework-version v6.0 -n <function-app-name> -g <resource-group-name>

The command seems to run successfully, but I still get the "unsupported runtime" warning in the Azure portal. Perhaps the issue is deeper than just the Azure Resource Explorer?

balag0 commented 1 year ago

Sorry for the delay in updating the status. Yes this a regression and we are actively working on resolving the 403 error. Will post an update once the issue is mitigated.

@el-pato I think that error is unrelated to this issue. Could you open an issue at https://github.com/Azure/Azure-Functions/issues

balag0 commented 1 year ago

This should be working now.

David-W-Williams commented 1 year ago

@balag0 It started working for me. Thanks for the update.

kesselringt commented 1 year ago

Hello, I see this issue is a couple months old, but it seems to have resurfaced. Nothing seems to be down on the Azure side as far as I can tell.

verbedr commented 1 year ago

Are you using a user from the tenant or a guest account? I got the same problem and for one tenant it worked, but when I switched if gave the 403. But using a user created in that tenant, everything worked. Perhaps this is not the expected behaviour, but it could be used as a temporary fix.

kesselringt commented 1 year ago

Huh... Well that works now. I swear I tried that last week via a private browser but still didn't work, but now it does. Well at least I have a way in thanks!

Are you using a user from the tenant or a guest account? I got the same problem and for one tenant it worked, but when I switched if gave the 403. But using a user created in that tenant, everything worked. Perhaps this is not the expected behaviour, but it could be used as a temporary fix.

wirelessy commented 1 year ago

It is happening to me and my team aswell. Support is forwarding me here. Requesting help aswell.

aaron-champion commented 1 year ago

I have a user experiencing this issue past few days, even in a private browser session. Other users including myself have no problems accessing and I can't figure out why just the one user. If it is a permissions or account setting that the user is missing, I can't think of what it could be.

balag0 commented 1 year ago

Fix was deployed Sept 29. This should have resolved (and we also have confirmation on this thread) the regression mentioned above.So resolving this issue to avoid confusion.

Regarding subsequent failures, could you please open separate issues with any interesting details in the setup. Sorry for the extra work but this would help us identify the scenarios better. Thanks