microsoft/vscode-azureresourcegroups

Latest version (0.8.0) does not support Azure USGovCloud

Closed this issue ยท 21 comments

I spent the last couple of hours wondering why our resources weren't listed when authenticated as an Azure USGovCloud account. As soon as I manually downgraded to 0.75.0 (the most recent previous version), everything started working again. I believe there is a bug that Azure GovCloud resources cannot be listed or managed.

That's so funny. I literally was just finishing up on a review on their extensions page about how 0.8.0 was completely breaking my workflow. In any case I got a response from Microsoft you can see it below.

Hi Nicholas, sorry to hear that. Version 0.8.0 does work with Azure Gov. cloud but you need to update the microsoft-sovereign-cloud.environment setting in VS Code. You can set it to the "USGovernment" option.

I can't confirm if their suggestion will fix anything, but figured I would come here and make this comment in case others are suffering from the same issue.

@alexweininger we may want to do a 0.8.1 update with a note in the changelog and readme about how to use sovereign clouds.

Version 0.8.0 does work with Azure Gov. cloud but you need to update the microsoft-sovereign-cloud.environment setting in VS Code. You can set it to the "USGovernment" option. Please try that and get back to us. Sorry that wasn't properly communicated on the readme/changelog.

image

Given that through Azure Account, we are logged in, why can this extension just not use the same Cloud environment that the user is authenticated with? I don't think requiring a separate configuration is going to fly unless there is a valid reason I am not aware of. It should "just work" like it always has.

The Azure Account extension is headed for deprecation, so eventually there will still only be one configuration. More information here: https://github.com/microsoft/vscode-azureresourcegroups/blob/main/CHANGELOG.md#azure-account-extension

I updated to 0.8.0 again and after updating microsoft-sovereign-cloud.environment to "USGoverment", as soon as I authenticate to a GovCloud account, I am getting a 400 error from the callback page: http://127.0.0.1:55906/callback?...

image

I think there is still something not working all the way.

Also, the Resources just spins waiting on the authentication confirmation:
image

@daronzwink thanks for trying that out, we're now investigating it ourselves.

Submitted an issue to VS Code microsoft/vscode#198562

Until this issue is fixed, please downgrade the Azure Resources extension to v0.7.5.

Just to add to this conversation v0.8.0 is throwing AADSTS65002 when trying to log in to Azure Gov Cloud.

Sovereign cloud support is now fixed in the latest release v0.8.2.

Any updates to this open issue? I am having issues connecting to US Government cloud.

Looks like ms-azuretools.vscode-azureresourcegroups still can't connect to US Government Cloud.

Any updates to this open issue? I am having issues connecting to US Government cloud.

Looks like ms-azuretools.vscode-azureresourcegroups still can't connect to US Government Cloud.

Please try out the latest release. Looks like we commented at about the same time ๐Ÿ˜„

Ha! What funny timing ;-)

I still was unable to get Azure Resource extension to work with the newer version. I back dated to an older version and it's working now.

I still was unable to get Azure Resource extension to work with the newer version. I back dated to an older version and it's working now.

Could you share any errors you are seeing and the repro steps?

I updated to version 0.8.2, and am now connected to our US GovCloud account, but there is still functionality that is not working within the Resources module.

  • Not able to view Logs, the only option is to stream logs.
image
  • When clicking "Connect to Log Stream", it just hangs.
image
  • Unable to view Files, it doesn't show anything.
image
  • Expanding Deployments results in 403 error.
image

@daronzwink , thank you for providing this! That was my exact issue. :)

@alexweininger : see above from @daronzwink.

@Lwhieldon and @daronzwink please update to Azure Resources v0.8.3 to fix the issue.

@alexweininger , thanks and these functions are now working! Appreciate your support getting this new version resolved.

thanks and these functions are now working! Appreciate your support getting this new version resolved.

Thank you for confirming. And thank you very much for your patience.

Thank you!!