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

Deprecate VisualStudioCodeCredential #48596

Open
scottaddie opened this issue Mar 6, 2025 · 1 comment
Open

Deprecate VisualStudioCodeCredential #48596

scottaddie opened this issue Mar 6, 2025 · 1 comment
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.
Milestone

Comments

@scottaddie
Copy link
Member

scottaddie commented Mar 6, 2025

Ask: Deprecate VisualStudioCodeCredential (and VisualStudioCodeCredentialOptions). There's no path to success when using it. Apply [EditorBrowsable(EditorBrowsableState.Never)] to the class, and remove all mentions of the credential from the README.

Background: The VS Code Azure Account extension on which VisualStudioCodeCredential relies has been deprecated. Customers should use other dev-time credentials, such as AzureCliCredential, for their local development needs. Once the VS Code desktop app has authentication broker support (via MSAL Node.js) across Windows, macOS, and Linux, a broker-enabled instance of InteractiveBrowserCredential would be a great solution here. Unfortunately, that broker support only exists for Windows customers today, via WAM. Issue #30525 tracks the work to improve the devex for VS Code customers on Windows.

@scottaddie scottaddie added Client This issue points to a problem in the data-plane of the library. Azure.Identity labels Mar 6, 2025
@scottaddie scottaddie added this to the 2025-04 milestone Mar 6, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Mar 6, 2025
Copy link

github-actions bot commented Mar 6, 2025

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@scottaddie scottaddie moved this from Untriaged to Not Started in Azure Identity SDK Improvements Mar 6, 2025
@scottaddie scottaddie removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.
Projects
Status: Not Started
Development

No branches or pull requests

2 participants