Skip to content

Re-enable VisualStudioCodeCredential for Windows after VSCode adopts BrokeredAuthentication (WAM) #30525

Open

Description

VisualStudioCodeCredential will depend on a new authentication tool which replaces the Azure Account extension in Visual Studio Code. This tool is not yet built; more details to come. [https://github.com/microsoft/vscode/issues/178740]

Reminder: when added back to DAC, the default failure mode should be CredentialUnavailableException, as with other dev credentials in the chain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Azure.IdentityClientThis issue points to a problem in the data-plane of the library.

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions