Forum Discussion
Urgent: Teams app publishing process blocked - app does not appear in the store after approval
Hello everyone,
i am contacting you regarding a problem with the publishing of my Microsoft Teams app that started yesterday and is blocking my development work.
Problem description:
After developing a new version of my MS Teams app, I can no longer successfully publish it in my organization. The app is uploaded in the Developer Portal, released in the Teams Admin Center, but then does not appear in the Teams App Store under "Built for your org", so I cannot test it.
Chronology:
I am an admin in my organization and am developing a Teams app
Before yesterday, the publishing process went smoothly: Upload in the Developer Portal → Appearance in the App Store → Test
Yesterday, a colleague installed the app for testing purposes
Since then, I can no longer publish new versions (they do not appear in the App Store)
The upload and release in the Admin Center work without an error message
However, the app does not appear in the App Store afterwards, neither in the desktop client nor in the web client
Attempts have already been made to solve this:
Completely restarted Teams client several times
App version increased in manifest (to 1.2.0)
App deleted and re-uploaded in Developer Portal
App deleted and re-released in Teams Admin Center
Waited for a delay of several hours
Cleared cache (as far as possible on Mac)
Test in web client (with the same result)
Special observations:
In the Mac client, the button "Upload a custom app" is grayed out with the note to contact my IT admin (I am the admin myself)
On the Service Health Page, there is an active incident with the ID MO1093370 that affects Microsoft Teams
I suspect that the issue is related to the current service degradation, which is described in the health page as "An infrastructure component is not processing requests as efficiently as expected" and explicitly affects Microsoft Teams.
Is there a way to fix or work around this issue so that I can continue my development work? Can you confirm whether there is a connection with the current service degradation?
Thank you in advance for your help.
Best regards
Michael
Hello Michael, your analysis is correct: the incident MO1093370 on the Microsoft 365 Service Health page is likely the root cause of your issue. When there is a service degradation affecting Teams infrastructure, app publishing, discovery, and update propagation can be delayed or blocked—even if uploads and releases appear successful in the Developer Portal and Admin Center.
Monitor the Service Health Dashboard for updates on MO1093370. Once Microsoft resolves the incident, app publishing and discovery should return to normal.
There is a direct connection between your publishing issue and the ongoing service degradation. Once Microsoft resolves MO1093370, your app should appear as expected. No action on your side is likely to resolve this until the incident is closed.
4 Replies
Sayali-MSFTMicrosoft
Hello Michael, your analysis is correct: the incident MO1093370 on the Microsoft 365 Service Health page is likely the root cause of your issue. When there is a service degradation affecting Teams infrastructure, app publishing, discovery, and update propagation can be delayed or blocked—even if uploads and releases appear successful in the Developer Portal and Admin Center.
Monitor the Service Health Dashboard for updates on MO1093370. Once Microsoft resolves the incident, app publishing and discovery should return to normal.
There is a direct connection between your publishing issue and the ongoing service degradation. Once Microsoft resolves MO1093370, your app should appear as expected. No action on your side is likely to resolve this until the incident is closed.Hello Sayali,
Thank you for your reply! The problem has now been solved - it was really due to the incident MO1093370
Best regards
Michael
- Sayali-MSFT
Hello MRingtunatus,
Glad to hear that your issue is resolved
We would appreciate it if you could share your valuable feedback via the Microsoft Teams Developer Community Response Feedback link?
- Sayali-MSFT
Hello Michael, Thank you for your inquiry! Could you please provide more details about your issue? Specifically, it would be helpful to know:
- Reproduction Steps: What steps did you take leading up to the problem?
- Documentation Links: Are there any specific guides or documentation you followed?
- Teams Client Version: What version of the Teams client are you using?
- Code Snippets: If applicable, please share any relevant code snippets.
- Manifest Package: If you have one, could you include the manifest package for your app?
Providing this information will help us better understand your situation and assist you more effectively.
However, if you have any business-critical issue which need immediate attention, please raise a support request here:
https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide&tabs=online
