Forum Discussion

MatejSvejda's avatar
MatejSvejda
Copper Contributor
Nov 13, 2026

Teams app update stuck in Certification for almost three weeks

Hi everyone,

We submitted an update to our Teams app Condens on October 26. Since Oct 26, 2026, 10:55 PM UTC, it has been in the Certification step in Partner Center, and nothing has changed since. Partner Center estimates under 5 business days for this step.

Details:

  • Product ID: WA200008643
  • Listing: https://marketplace.microsoft.com/en-us/product/wa200008643
  • Submitted changes: packages, marketplace listings and availability
  • Status: In progress, step “Package availability” under Certification

We emailed email address removed for privacy reasons on November 9 and followed up since, but haven’t received a response.

Has anyone seen something similar recently? Is there another channel we should use to escalate a stuck submission? If someone from the Teams Store team sees this, we’d really appreciate a look.

Thank you!
Matej

1 Reply

  • Three weeks at 'Package availability' is past stuck, not just slow — Partner Center's own estimate for that step is under five business days, and the Teams docs don't publish a separate timeline for that intermediate stage, so there's nothing to wait out.

     

    The channel that actually gets this tracked is a Partner Center support ticket, not email. Microsoft Learn's Partner Center account FAQ for Teams publishers says to go through the publishers support page and, if the guidance there doesn't help, create a Partner Center support ticket. Put the product ID (WA200008643), the October 26 submission date and the exact step — 'Package availability' under Certification — in it, so it lands with the right team.

     

    Then, because it's already been more than seven business days: the same FAQ has a specific follow-up for a ticket with no update in seven business days — email email address removed for privacy reasons with the subject 'Partner Center Account Issue for Condens', and include the support ticket number, your seller ID and a screenshot of the stuck status. If the email you sent on November 9 went to that address without a ticket number attached, that would explain the silence — the ticket comes first, the email is the chase for the ticket.

     

    I'd hold off resubmitting the same package while the ticket is open, since that would start a fresh certification run. The ticket plus that follow-up email is the documented escalation route.