Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review errors for all FAQ DefaultAzureCredential error scenarios #20203

Closed
christothes opened this issue Apr 7, 2021 · 2 comments
Closed

Review errors for all FAQ DefaultAzureCredential error scenarios #20203

christothes opened this issue Apr 7, 2021 · 2 comments
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.

Comments

@christothes
Copy link
Member

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.

@ericsampson
Copy link

Hi @christothes , re your comment that led to this issue being created

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)

@christothes
Copy link
Member Author

Hi @christothes , re your comment that led to this issue being created

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

@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

2 participants