{ "errorCode": "AddAppBotToChatRosterFailed" }

Question

We're encountering a frustrating and inconsistent issue when attempting to install our custom Teams app. The installation process sometimes fails with a generic "Something went wrong" error in the Teams desktop client. When using the Teams web client, we see an HTTP 500 response in the network tab with the error body:

{ "errorCode": "AddAppBotToChatRosterFailed" }

This error doesn't occur consistently:

• Some users (including a customer) experience it 100% of the time.

• Others have never reported the issue.

• Our internal testers see it intermittently—sometimes it installs fine, other times it fails, and occasionally it works again after logging out and back in.

We've carefully reviewed Teams and Azure AD security/permission settings and can't find any clear cause. The installation flow we're using had worked reliably in the past, and this issue only began surfacing recently.

Thanks in advance for any help!

Answer 1

Hi Kinatyan Halaas, 

Thank you for posting your question in the Microsoft Q&A forum.  

Based on what you've shared, I’ve done some research and found a GitHub thread that seems closely related to your situation: 
Custom app installation fails with "Something went wrong" (AddAppBotToChatRosterFailed) error · Issue #3178 · MicrosoftDocs/msteams-docs 

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link 

The discussion is quite extensive, and I highly recommend reviewing it for deeper insights. However, I’d like to summarize some key workarounds shared by the original poster that may help resolve or isolate the issue: 

The error appears to be related to side-loading custom apps and the associated Teams and Azure AD permissions. Please check the following settings in the Teams Admin Center: 

• Teams apps > Permission policies 
  Ensure the policy allows installing 3rd-party and custom apps for the affected users. 
• Teams apps > Setup policies 
  Confirm that uploading custom apps is permitted. 
• Teams apps > Manage apps 
  • Check if the app is listed. 
  • Under Org-wide app settings, verify that users are allowed to install and interact with custom apps. 

If you don’t have access to these sections, please contact your Teams admin or request elevated privileges. 
To help isolate the issue and rule out caching or permission-related problems, please follow these steps in order: 

1. Track the Error Context 
   At every point where an error occurs, note: 
   • The specific action being performed 
   • The exact date, time, and timezone 
     This helps with reproducibility and escalation if needed. 
2. Clear Cache and Restart Teams 
   • Sign out of Teams 
   • Quit the application completely 
   • Reopen Teams and sign in again 
     This helps eliminate known caching issues. 
3. Verify Permissions and Settings 
   Ensure: 
   • You’re signed in as a user with permission to upload/install custom apps 
   • All relevant Teams admin settings (Permission Policies, Setup Policies, Manage Apps) are correctly configured 
4. Check App Visibility 
   • Look for the app under Manage apps in the Teams Admin Center 
   • Also check the “Built for your org” section in the Teams client 
5. Try Installing via Channel First 
   • Click the caret next to the “Add” button and choose “Add to a chat” 
   • Select an existing channel in a team 
6. Test Bot Interaction in Channel 
   • Even if installation fails, try @mentioning the bot in the channel 
   • Check your system logs to see if the event was received 
     • If yes, the installation may have succeeded silently 
     • If no, and the mention doesn’t trigger anything, proceed to next step 
7. Try Installing via Team Instead 
   • Use “Add to a team” from the same dropdown menu 
   • If that fails, try starting a DM chat with the bot and send a message 
   • Again, check logs to confirm whether the bot received the event 
8. Clean Up Previous Attempts 
   • Delete any old or partial installations of the app 
   • Log out, quit Teams, reopen, and log back in 
9. Upload via Teams Admin Center 
   • Instead of uploading the manifest via the Teams client, go to: 
     Teams Admin Center – Manage Apps 
   • Upload the manifest there and repeat steps 4–7 

This structured approach helps eliminate common causes and provides a clearer path to identifying whether the issue is truly backend-related or tied to configuration. 

The poster also said that one customer discovered their Azure subscription had been disabled, which caused the issue. Please verify: 

• App Registration 
• Bot Channels Registration 
• Azure subscription status 
• Resource group configuration 
• AAD permissions 
• Teams user permissions 
• Whether the app is single-tenant 
• Teams admin security settings 

If the issue persists after tried all suggestions above, I recommend raising a support ticket with the Azure Support team. As far as I know, this error seems to be related to backend issue, and they have the necessary tools and access to investigate further. Since we don’t have those tools available on the forum side, I really appreciate your patience and understanding.  

For more details, you can also refer to this article: How to create an Azure support request - Azure supportability | Microsoft Learn  

About why you unable to upload the question with the "Teams Development" tag. This may be due to a recent migration of the Q&A platform, which can cause temporary issues with tag selection. Thanks for your understanding! 

I hope this helps! Please let me know if you have any further questions. 

---

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