The provided information does not indicate any documented, ongoing service issue with Visual Studio Marketplace sign-in or extension visibility, and it does not describe any behavior where a 500 error would automatically unpublish or remove an extension.
From the available guidance, the only supported ways an Azure DevOps/VS Marketplace extension becomes invisible are:
- It was unpublished by the publisher (only free extensions can be unpublished).
- It was removed from the Marketplace (only possible if the extension has zero installs, or via a manual deletion by Microsoft Support for legal/security reasons).
When an extension is unpublished:
- It is immediately removed from public Marketplace listings and can no longer be installed by new users.
- Ratings and reviews remain stored with the extension.
- The publisher can later republish it from the publisher management page.
If an extension is removed and had zero installs, the action is irreversible.
Because sign-in to the Marketplace is currently failing with a server-side 500 error, the only supported path to investigate both the sign-in failure and the missing extension is to contact Microsoft support so they can:
- Check the status of the publisher account associated with the Gmail identity.
- Verify whether the extension has been unpublished or removed, and why.
- Help restore access or advise on republishing if applicable.
For extensions that must be removed or restored due to legal or security problems, the documented escalation path is to contact Customer Support via Developer Community, where requests are reviewed and handled manually.
Once sign-in is working again and access to the publisher management portal is restored, the extension’s state can be checked and changed there:
- Open the publisher management portal.
- Select the relevant publisher.
- Locate the extension in the list of published/unpublished extensions.
- If it is unpublished and should be visible again, choose Publish.
If the extension does not appear at all under the publisher after sign-in is fixed, support must confirm whether it was removed and whether any recovery options exist.
References: