Azure Policy
An Azure service that is used to implement corporate governance and standards at scale for Azure resources.
883 questions
Azure Policy VS Code extension auth error
Mikael Sand
26
Reputation points
When trying to get my deployed policies in the explorer to the left of VS Code I get this error.
Strange. No setting I know of that I need to update.
I can access my resources in the top part of the explorer.
{count} votes
-
![](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(249.60000000000002, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
SwathiDhanwada-MSFT 18,756 Reputation points2020-10-12T08:27:10.527+00:00 @Mikael Sand Welcome to Microsoft Q& A Team.
You might have already tried it , but can you please try signing out and try to sign in and access Azure Policy via Visual Studio Code by following through this document ?
-
Mikael Sand 26 Reputation points
2020-10-12T09:19:29.977+00:00 Yes, but I had never tried signing out first.
I did however do that now, but the error is still the same.The strange thing is that your Login uses another tenant id as issuer, and the old STS path.
Why not use the proper oauth path for Login in Azure? -
SwathiDhanwada-MSFT 18,756 Reputation points
2020-10-14T09:55:50.163+00:00 @Mikael Sand Thanks for trying the instructions. As per my analysis, seems the error is prompted for the users who have Free or VSE subscriptions. I am further checking on this internally.
Can you please let me know what subscription are you using ?
-
Mikael Sand 26 Reputation points
2020-10-14T11:54:43.95+00:00 Ah! Now we are on to something.
- Yes the first error was in a IUR subscription (my ooooold MSDN one). Non work credentials.
- I tried with the company EA one (with work credentials) in the same tenant. This works fine.
- I tried my work credentials with other tenants (guess access) and got the same error as with point 1.
This is only for the "Policy" part. The resources part works fine with whatever I am using.
-
SwathiDhanwada-MSFT 18,756 Reputation points
2020-10-16T06:53:13.137+00:00 @Mikael Sand Thanks for detailed information. I am checking internally with the team and will post an update soon.
-
SwathiDhanwada-MSFT 18,756 Reputation points
2020-10-21T03:51:09.297+00:00 @Mikael Sand Thanks for your patience. I am checking internally with the PG team. We are still debugging the issue to find the cause. I will keep you posted.
-
Mikael Sand 26 Reputation points
2020-10-21T06:05:27.277+00:00 Let me know if you need any more info.
-
SwathiDhanwada-MSFT 18,756 Reputation points
2020-10-22T13:35:22.437+00:00 @Mikael Sand : From the analysis done by Azure Policy PG team, the Azure Policy extension uses the Azure Account extension for Azure auth. It appears that legacy accounts have different session behavior, and are getting populated with two session properties, each with tokens from different tenant IDs.
A bug has been raised with Azure Account extension team for the same. You can track the bug here.
Kindly let me know if you have any further queries.
-
Mikael Sand 26 Reputation points
2020-10-22T14:10:00.433+00:00 The downside of having been on Azure for a long time :-)
Sign in to comment
Sign in to answer