Add-on components that enhance and customize the Visual Studio integrated development environment
Thanks for reaching out!
The extension belongs to a publisher identity, and the user is logged in with an account that is not associated with that publisher.In the Visual Studio Marketplace: Publishing is controlled by Publisher Accounts. Access is tied to Azure DevOps / Microsoft identity permissions. If the logged-in account is not a publisher owner or contributor, the upload endpoint returns 403.
Below are some steps
- Verify the Publisher Account and check which publisher owns the extension.
https://marketplace.visualstudio.com/manage
If the publisher does not appear, they are logged into the wrong account.
- Verify Azure DevOps Organization Access, Visual Studio Marketplace publishers are actually linked to Azure DevOps organizations. (https://dev.azure.com)
Click profile icon and Switch directory if needed, Verify the organization where publisher was created.
- Check Publisher Permissions, If the publisher exists but publishing fails. Select the publisher and goto Members
Check one of these roles:
-Owner
-Contributor
If not, an owner must add them.
- Clear Authentication Session. Marketplace authentication often breaks due to token mismatch.
- Verify VSCE Publishing Credentials, If publishing via CLI
- Confirm Publisher Name Matches Extension. It must exactly match the Marketplace publisher.
If incorrect then Marketplace returns 403.