You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a common set of edge case issues that customers encounter when using DefaultAzureCredential that result in failures that are difficult to diagnose or debug.
Review all of these error scenarios and improve the relevant error messages as appropriate.
The text was updated successfully, but these errors were encountered:
I'm sure that I'm missing information, but why does the az CLI work fine with this tenant scenario, if as per your comment there is something fundamental that needs to be addressed for VS/VSCode token providers to work. I'm just curious why they can't do the same thing that allows the CLI to work fine in this case.
Our org has been running into this too and it has been a real pain for us.
In this related issue, Anais said that they created an internal request for VS to address this. #12773 (comment)
I'm sure that I'm missing information, but why does the az CLI work fine with this tenant scenario, if as per your comment there is something fundamental that needs to be addressed for VS/VSCode token providers to work. I'm just curious why they can't do the same thing that allows the CLI to work fine in this case.
Our org has been running into this too and it has been a real pain for us.
In this related issue, Anais said that they created an internal request for VS to address this. #12773 (comment)
We're planning to address the tenant discovery feature mentioned in that comment you linked to. Here is the tracking item: #19404
There are a common set of edge case issues that customers encounter when using
DefaultAzureCredential
that result in failures that are difficult to diagnose or debug.Review all of these error scenarios and improve the relevant error messages as appropriate.
The text was updated successfully, but these errors were encountered: