Dear @Sham,
Thank you so much for contacting Microsoft Q&A Forum.
Based on your description, it sounds like you've successfully built and tested your Microsoft Teams bot locally using the Teams Toolkit in Visual Studio, but you're facing issues with publishing it to your organization’s Teams app catalog. Also, you can sideload the .zip app package into your Teams client and it works fine. This means your bot is correctly packaged and functional. However, your app submission request to the admin is not being received or processed and your organization users cannot install the bot from the Teams app store.
In this case, there are several reasons that may cause it:
1.App submission not sent or lost:
- Sometimes the submission doesn’t go through due to tenant settings or UI glitches.
- The admin might not be notified or might have missed the request.
2.Admin permissions or policies:
- Your organization might have strict app publishing policies.
- Admins may have disabled custom app submissions or require manual upload via Teams Admin Center.
3.App catalog issues: the app might not be visible in the catalog due to missing metadata, permissions, or compliance settings.
4.Missing required information in manifest: if your manifest is missing required fields (like webApplicationInfo, validDomains, or bot settings), it might be rejected silently.
Therefore, I have researched and found these suggestions that you can check to see if it can help you:
Suggestion 1: manually submit to Admin:
You can ask your admin to:
- Go to Teams Admin Center → Teams apps → Manage apps
- Click Upload and manually upload your .zip package
- Approve and publish it to the organization catalog
You can also send them the .zip file directly and request manual upload.
Suggestion 2: check Admin settings:
Enable custom app upload for users: your admin must allow users to upload custom apps by configuring App Setup Policies:
- Go to Teams Admin Center: https://admin.teams.microsoft.com
- Navigate to Teams apps > Setup policies
- Either: edit the Global (Org-wide default) policy, or create a new policy for specific users.
- Enable the toggle for Upload custom apps.
- Assign the policy to users who need to upload or test custom apps.
Also, your admin can go to Teams apps > Manage apps > Org-wide app settings > turn on Custom apps toggles.
Reference: Manage custom app policies and settings - Microsoft Teams | Microsoft Learn
Besides that, please check to make sure that your admin enables app submission notifications:
- In Teams Admin Center, go to Notifications & alerts > Rules.
- Find the rule named App submissions.
- Set the rule status to Active.
- Choose where to send notifications.
This ensures admins are notified when you submit your app for approval.
Suggestion 3: verify app manifest:
Make sure your manifest.json includes:
- Correct bot configuration
- Valid webApplicationInfo (if using Azure AD)
- Required permissions
- Proper validDomains
You can validate your manifest using the App Studio or Teams Toolkit.
References:
App Manifest Reference - Teams | Microsoft Learn
Customize app manifest in Agents Toolkit - Teams | Microsoft Learn
Configure Bot Capability - Teams | Microsoft Learn
I hope this information can help you to deploy your app so that your business can work well.
Wish you a pleasant day!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.