Visual Studio Marketplace publisher reinstatement remains unresolved after completed cooldown and remediation — how can I escalate?

veritas 0 Reputation points
2026-11-16T05:43:07.2466667+00:00

Hello Microsoft Support Team,

I am seeking guidance on how to escalate an unresolved Visual Studio Marketplace publisher reinstatement request.

My publisher, ovolab-veritas, has remained blocked since August 2026. Although I have completed the mandatory cooldown period, acknowledged the policy concerns, and confirmed that I will permanently discontinue publishing the affected extensions, I have not received a substantive reinstatement decision from Visual Studio Marketplace Support.

Background and timeline

  • August 2026: Marketplace Support confirmed that my publisher had been blocked due to policy violations involving previously removed extensions. I was instructed to wait for a mandatory 30-day cooldown period before requesting reinstatement.

September–October 2026: After the cooldown period, I repeatedly contacted Marketplace Support and submitted the requested remediation materials, including updated VSIX packages and screenshots.

November 2, 2026: To resolve the policy concerns definitively, I formally confirmed that I would permanently discontinue publishing all affected CodeSnap-related extensions, including the renamed GlyphPane project. I explicitly stated that I would not request restoration of the removed extensions or resubmit them under different names.

November 5, 2026: Marketplace Support replied with instructions to modify extension names, metadata, and content, despite my explicit decision to discontinue publishing the affected projects.

November 6, 2026: I reiterated that I understood the identified issues and confirmed permanent discontinuation as my remediation. I requested reinstatement of the publisher independently of the removed extensions.

As of November 16, 2026: I have received only an automated acknowledgment of my latest response, without a substantive reinstatement decision or specific outstanding requirements.

Current issue

My request is not to restore any removed extension or seek approval to republish the affected projects.

I only wish to restore my existing publisher account so that I can continue maintaining other unrelated extensions, particularly:

ovolab-veritas.academic-pdf-viewer

This extension remains publicly available on the Visual Studio Marketplace, but I cannot publish maintenance updates because my publisher account is blocked.

Attempts to authenticate through vsce have returned:

Request was blocked due to exceeding usage of
resource 'Concurrency' in namespace 'VSID'.

Microsoft.TeamFoundation.Framework.Server.RequestBlockedException

Marketplace Support has separately confirmed that the publisher is blocked due to policy enforcement, so I understand that this is not simply a temporary rate-limiting problem that can be resolved by changing credentials or retrying.

Steps already taken

Completed the mandatory 30-day cooldown period.

Reviewed and acknowledged the identified policy violations.

Submitted the requested remediation materials multiple times.

Formally committed to permanently discontinuing the affected extensions on the Visual Studio Marketplace.

Clarified that my request concerns only publisher reinstatement for maintaining unrelated existing extensions.

Followed up repeatedly through [email protected] and [email protected].

Despite these steps, I have not received a decision or a clear explanation of any remaining reinstatement requirements.

My question

What is the appropriate official escalation path for a Visual Studio Marketplace publisher reinstatement request when the mandatory cooldown has been completed, remediation has been confirmed, and Marketplace Support has not provided a substantive decision despite repeated correspondence?

I understand that Microsoft Learn Q&A moderators may not have direct access to Marketplace publisher enforcement systems.

I am therefore not asking Q&A moderators to remove the block directly. Instead, I would appreciate guidance on how to reach the team authorized to review publisher reinstatement, obtain an actionable case status, or receive a definitive statement of any outstanding requirements.

I am willing to cooperate with any further review or remediation that is specifically required.

Thank you for your assistance.Hello Microsoft Support Team,

I am seeking guidance on how to escalate an unresolved Visual Studio Marketplace publisher reinstatement request.

My publisher, ovolab-veritas, has remained blocked since August 2026. Although I have completed the mandatory cooldown period, acknowledged the policy concerns, and confirmed that I will permanently discontinue publishing the affected extensions, I have not received a substantive reinstatement decision from Visual Studio Marketplace Support.

Background and timeline

August 2026: Marketplace Support confirmed that my publisher had been blocked due to policy violations involving previously removed extensions. I was instructed to wait for a mandatory 30-day cooldown period before requesting reinstatement.

September–October 2026: After the cooldown period, I repeatedly contacted Marketplace Support and submitted the requested remediation materials, including updated VSIX packages and screenshots.

November 2, 2026: To resolve the policy concerns definitively, I formally confirmed that I would permanently discontinue publishing all affected CodeSnap-related extensions, including the renamed GlyphPane project. I explicitly stated that I would not request restoration of the removed extensions or resubmit them under different names.

November 5, 2026: Marketplace Support replied with instructions to modify extension names, metadata, and content, despite my explicit decision to discontinue publishing the affected projects.

November 6, 2026: I reiterated that I understood the identified issues and confirmed permanent discontinuation as my remediation. I requested reinstatement of the publisher independently of the removed extensions.

As of November 16, 2026: I have received only an automated acknowledgment of my latest response, without a substantive reinstatement decision or specific outstanding requirements.

Current issue

My request is not to restore any removed extension or seek approval to republish the affected projects.

I only wish to restore my existing publisher account so that I can continue maintaining other unrelated extensions, particularly:

ovolab-veritas.academic-pdf-viewer

This extension remains publicly available on the Visual Studio Marketplace, but I cannot publish maintenance updates because my publisher account is blocked.

Attempts to authenticate through vsce have returned:

Request was blocked due to exceeding usage of
resource 'Concurrency' in namespace 'VSID'.

Microsoft.TeamFoundation.Framework.Server.RequestBlockedException

Marketplace Support has separately confirmed that the publisher is blocked due to policy enforcement, so I understand that this is not simply a temporary rate-limiting problem that can be resolved by changing credentials or retrying.

Steps already taken

Completed the mandatory 30-day cooldown period.

Reviewed and acknowledged the identified policy violations.

Submitted the requested remediation materials multiple times.

Formally committed to permanently discontinuing the affected extensions on the Visual Studio Marketplace.

Clarified that my request concerns only publisher reinstatement for maintaining unrelated existing extensions.

Followed up repeatedly through [email protected] and [email protected].

Despite these steps, I have not received a decision or a clear explanation of any remaining reinstatement requirements.

My question

What is the appropriate official escalation path for a Visual Studio Marketplace publisher reinstatement request when the mandatory cooldown has been completed, remediation has been confirmed, and Marketplace Support has not provided a substantive decision despite repeated correspondence?

I understand that Microsoft Learn Q&A moderators may not have direct access to Marketplace publisher enforcement systems.

I am therefore not asking Q&A moderators to remove the block directly. Instead, I would appreciate guidance on how to reach the team authorized to review publisher reinstatement, obtain an actionable case status, or receive a definitive statement of any outstanding requirements.

I am willing to cooperate with any further review or remediation that is specifically required.

Thank you for your assistance.

Developer technologies | Visual Studio | Extensions
0 comments No comments

Answer accepted by question author
Brian Pham (WICLOUD CORPORATION) 1,430 Reputation points Microsoft External Staff Moderator
2026-11-16T08:11:31.4966667+00:00

Hi @veritas ,

Thank you for the detailed explanation.

First, I sincerely appreciate the time and effort you've put into addressing the policy concerns and communicating with Marketplace Support throughout this process.

I see that you've already been contacting the appropriate support channels through the two mails you mentioned. These are the most relevant contacts I'm aware of for handling your publisher reinstatement request.

Therefore, I recommend continuing your existing email conversation and explicitly requesting an escalation of your publisher reinstatement review. You may also ask for an update on the review status and clarification of any outstanding requirements. While the process may take some time, continuing to follow up through these channels is the most appropriate course of action for your concern at this stage.

Thank you for your understanding of the limitations of Microsoft Q&A, as publisher restrictions can only be reviewed by the appropriate Marketplace team. I appreciate your continued patience.

You’re also welcome to share your feedback on my response by following this guidance .

Have a nice day! Thank you for your understanding.

Was this answer helpful?

2 people found this answer helpful.

0 additional answers

Sort by: Most helpful

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.