Publishing extensions to Marketplace issue resolved
We have resolved a known issue regarding publishing extensions to the Visual Studio Marketplace. If you’ve run into the error message: “Your ability to create global personal access tokens (PATs) is restricted by your organization.”, this is likely because your administrator has enabled a policy to restrict the creation of global personal access tokens (PATs).
Previously, a global PAT was necessary to publish an extension to the Visual Studio Marketplace using the Cross-platform CLI for Azure DevOps (tfx-cli). We have now redesigned the extensions publishing process to accept any PATs with a Marketplace “Publish” scope.
Moving forward, any personal access token with a Marketplace “Publish” scope can be used to publish Azure DevOps and Visual Studio extensions in the Visual Studio Marketplace. This is the case even if the administrator has disabled the creation of global personal access tokens (PATs) policy.
Thank you for your patience while we resolve this PAT issue and we hope you are able to more seamlessly publish extensions moving forward. If you come across any other issues, please do not hesitate to share with us below.
Dear Gloridel, I am very happy with your posts on this blog. All of your posts are informative and come from experience. Good lock. crypto