Microsoft Adds Trusted Publishing to Visual Studio Marketplace
The new feature enables secure extension publishing using short-lived credentials instead of static access tokens.
Updated on Oct. 28, 2026 in Software

Live Poll
Do you trust automated publishing tools to keep your development work secure?
Microsoft introduced Trusted Publishing for the Visual Studio Marketplace, a new feature that enables extension developers to publish code without storing long-lived personal access tokens. This security-focused update uses temporary credentials issued through federated identity services.
Why it matters
The change minimizes the risk of credential theft by eliminating the need to store and rotate sensitive Azure DevOps secrets in CI/CD pipelines. It moves the ecosystem toward a model of short-lived, automated identity verification.
Temporary credentials issued via OpenID Connect expire after 15 minutes, replacing the reliance on static Azure DevOps personal access tokens. Authors must define an approved repository and workflow, with a 48-hour activation window for new policies on private GitHub repositories.
The players
Microsoft
A global technology company providing enterprise software, cloud infrastructure via Azure, and development tools including Visual Studio and GitHub.
Visual Studio Marketplace
A centralized repository for extensions and plugins that enhance the capabilities of Microsoft's integrated development environments.
The details
Trusted Publishing relies on workload identity federation to verify release workflows. GitHub Actions publishers use OpenID Connect—a secure authentication protocol—to request temporary access, while Azure Pipelines utilizes a Microsoft Entra-backed service connection. By linking specific, authorized repositories to the Marketplace directly, the system grants temporary, scoped publishing rights instead of permanent credentials.
Timeline
October 28, 2026: Microsoft announced Trusted Publishing for Visual Studio Marketplace.
The Tech Race
This feature aligns with a broader industry push toward zero-trust CI/CD architectures that eliminate long-lived secrets. It follows similar secure-publishing initiatives seen across major package managers aiming to reduce supply chain attack vectors.
Extension developers can transition their workflows immediately by configuring their GitHub or Azure Pipelines environments for OIDC-based publishing. While token-based publishing remains supported, switching to the new method removes the manual burden of secret rotation.
The takeaway
Developers should audit their CI/CD pipelines to identify where static personal access tokens are currently stored. Watching the documentation for future deprecation announcements regarding token-based authentication will be necessary for long-term maintenance of extensions.
Further reading
For broader trends in secure development practices, see the latest updates in our Software section.
Source note: This article includes information reported by Visual Studio Magazine.
Live Poll
Do you trust automated publishing tools to keep your development work secure?





