@Gonzalo Jovanovich - The error message "The tenant admin disabled this bot" indicates that the bot's functionality in Microsoft Teams is being blocked at the tenant level by the administrator.
Ensure that the tenant admin has not disabled the bot at the organizational level. The admin might need to explicitly enable the bot for use within the tenant. You can ask the tenant admin to check the bot's status in the Teams admin center
The tenant admin disabled this bot
Hello, we are trying to connect a bot that we made to Teams and are facing an error in the teams channel from the Azure control panel that says "The tenant admin disabled this bot". Searching all over google, we applied new policies, blocked the bot, unblocked it, allowed specific users to it, blocked access to those users and allowed them again, added a LOT of permissions through Microsoft Entra ID to the Application, granted those permissions, waited for up to a day for all the changes to take effect, etc. Nothing worked, we still get the same error.
We can chat with the bot through the web chat test from the azure site, but it wont answer on teams, it just marks the message as read.
We tried to upload and use a default template to check if our code was maybe causing it, but we face the same issue even with an untouched and working template as follows:
Teams Toolkit for VSCode->Create new app->Custom Copilot->Basic AI Chatbot->Python->Azure OpenAI->Provide all the necessary keys->Check that the proyect works correctly as-is with the debug local tool->Provision->Deploy->Publish->Approve in Teams
Any help or advise would be extremely appreciated.
Azure AI Bot Service
Microsoft Teams | Development
2 answers
Sort by: Most helpful
-
Nivedipa-MSFT 3,731 Reputation points Microsoft External Staff Moderator
2025-01-11T19:01:01.7933333+00:00 -
Fernando Gomes 0 Reputation points
2025-07-31T13:46:50.8733333+00:00 I was facing the same issue here, and the problem was a API Permission in the App in Azure, not the Teams App. In my case, the permission that was causing the problem was Teamwork.Migrate.All. Using this permission with a local Teams app works well, but when publishing to Teams App Store, the bot is blocked. Revoking this permission fix the problem.