Share via

VS Code Marketplace returns 500 error on sign-in and published extension is no longer visible

무아 설 0 Reputation points
2026-03-28T06:49:18.5166667+00:00

I am unable to sign in to the Visual Studio Code Marketplace (https://marketplace.visualstudio.com). Every attempt to log in results in a 500 error page with the following details:

  • Error: 500 - Something went wrong!
  • Timestamp: 2026-03-28 오전 4:36:46 (UTC)
  • Correlation ID:  [Removed PII]
  • Azure sign-in account:  [Removed PII]@gmail.com

In addition to the sign-in failure, my previously published extension ("Jupyter Live Share" under the publisher namespace "seolmuah") is no longer visible on the Marketplace. I have not received any email notifications regarding removal or policy violations.

What I have tried:

  • Signing in from different browsers (Chrome, Edge)
  • Clearing browser cache and cookies
  • Waiting several hours and retrying

Questions:

  1. Is there a known ongoing service issue affecting Marketplace sign-in and extension visibility?
  2. Has my extension been removed, or is this a side effect of the server error?
  3. How can I contact support if I cannot even access the publisher management page?

Any help would be appreciated. Thank you.

제목 없음

Developer technologies | Visual Studio | Other
Developer technologies | Visual Studio | Other

A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Gérard Oomens 120.8K Reputation points Volunteer Moderator
    2026-03-29T10:25:21.0966667+00:00

    Try support as stated in the link?

    https://github.com/microsoft/vsmarketplace/issues/1741

    Thanks for reaching VS Marketplace Team, could you please reach our official support alias VSMarketplace@microsoft.com to address the issue promptly.

    Regards, VS Marketplace Team

    0 comments No comments

  2. 무아 설 0 Reputation points
    2026-03-29T00:30:11.72+00:00

    로그인 문제좀 해결해주세요. 로그인이 안됩니다.

    0 comments No comments

  3. Gérard Oomens 120.8K Reputation points Volunteer Moderator
    2026-03-28T11:14:36.7466667+00:00
    0 comments No comments

  4. Q&A Assist
    2026-03-28T06:49:36.91+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    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:

    1. Open the publisher management portal.
    2. Select the relevant publisher.
    3. Locate the extension in the list of published/unpublished extensions.
    4. 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:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.