Clarify DefaultAzureCredential documentation re InteractiveBrowserCredential
See original GitHub issueIt should be noted inline with the InteractiveBrowserCredential
that it is not actually enabled by default.
Proposed text:
InteractiveBrowserCredential (if enabled – see Remarks)
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 414d8832-9224-3bb5-2bf4-1197c41fdedf
- Version Independent ID: 02d95dd6-bf1b-5cef-bc94-ac187b133c45
- Content: DefaultAzureCredential Class (Azure.Identity) - Azure for .NET Developers
- Content Source: xml/Azure.Identity/DefaultAzureCredential.xml
- Service: azure
- GitHub Login: @rloutlaw
- Microsoft Alias: routlaw
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
[Identity] Browser DefaultAzureCredential should only use ...
InteractiveBrowserCredential defaults to "common" tenant and the client ID used for Azure CLI, so there's not a concrete difference in ...
Read more >DefaultAzureCredential Class (Azure.Identity)
Provides a default TokenCredential authentication flow for applications that will be deployed to Azure. The following credential types if enabled will be ...
Read more >azure.identity.DefaultAzureCredential class
A default credential capable of handling most Azure SDK authentication scenarios. The identity it uses depends on the environment.
Read more >DefaultAzureCredential, InteractiveBrowserCredential, etc.. ...
I am developing a Microsoft 365 / Office 2013 - 2021 Taskpane Add-in using Visual Studio Code that is written in JavaScript. The...
Read more >Class DefaultAzureCredential | Azure SDK for .NET
Provides a default Azure.Core.TokenCredential authentication flow for applications that will be deployed to Azure. The following credential types if enabled ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @christothes @Cpcrook – wanted to follow up on this.
I agree with @Cpcrook that addressing it in the Remarks section probably doesn’t go quite as far as we want to in this case. Someone could read the documentation, see “these credential types are tried”, and easily hit a “gotcha” scenario unless they happen to read all the way through to the Remarks.
I think a small piece of text like @Cpcrook suggests is warranted to call out the potential issue and save time/frustration without requiring a heavy lift on the part of the Docs.
Since I thought it would be helpful, I created https://github.com/Azure/azure-docs-sdk-dotnet/pull/2083 to attempt to put it into action.
This change has been merged, so the issue can now be closed. 👍