Repository navigation
Switch to publishing extensions using Azure Entra IDs instead of PATs #6152
Description
Activity
Comments in nimbus-agent/nimbus-vscode#34 suggest an organization-scoped PAT might work, so perhaps we should test this with the next release (or pre-release).
- changed the title
[-]Switch to secure automated publishing for extensions instead of PATs[/-][+]Switch to publishing extensions using Azure Entra IDs instead of PATs[/+]on Sep 8, 2026 Re-reading https://code.visualstudio.com/api/working-with-extensions/publishing-extension#secure-automated-publishing-to-visual-studio-marketplace, it seems like we might not need to completely automate this - the instructions show how to generate a Microsoft Entra ID (AAD) access token via Azure CLI. It's not clear what the lifetime of that is, but it might be that at least part of the workflow just needs to be done once and then publishing can still be done from the CLI.Edit: I think this is untrue?(that said, it might still be nice to automate the whole thing)
At the end of the year, we won't be able to publish extensions using PATs any more.
My request to support organization-scoped PATs has not been responded to (microsoft/vsmarketplace#2121).
However, the Publishing Extensions Docs has been updated to say:
We should figure out the best way forward here.