Applies to Product - Microsoft Copilot Studio
What’s happening?
Customers are experiencing issues with their bots in the Microsoft Teams Store after admin approval. The bots may not respond in chat, despite functioning correctly in Copilot Studio. Additionally, there may be conflicts when attempting to submit the bot for admin approval, resulting in error messages indicating that the Teams app already exists.
Reason:
The underlying cause of this may include:
- The bot not being properly configured for availability in the Teams Store.
- Potential conflicts with existing apps in the Teams environment.
- Authentication issues that prevent the bot from responding in Teams.
Resolution:
To resolve this, the following steps should be taken:
- Ensure that the bot is configured correctly in Copilot Studio, particularly in the Availability Options section. Confirm that it is set to "Show to everyone in my org" and that it indicates "Available in App store."
- If the error "Teams App already exists. Conflict detected" occurs, verify if there are any existing apps with the same name or ID in the Teams environment that may be causing the conflict.
- Check the authentication settings for the bot. If using manual authentication, ensure that all configuration steps were followed correctly. If possible, switch to using Microsoft Entra ID authentication and republish the bot.
- Confirm that the Teams Admin has not blocked any necessary apps or custom apps in the Teams Admin settings, as this can prevent the bot from functioning properly.
- If the bot does not respond in Teams, consider re-adding the bot and creating a new topic in Copilot Studio to initiate a conversation. Set the topic trigger to "Activity Received" and ensure the start behavior is configured to use the latest published content.