Adding a Bot to MS Teams: Sending new messages to this bot has been disabled

Occasional Contributor

I have created a QnA Bot in Azure, published it, and have attempted to open it in Microsoft Teams. However, when I do, I receive a message stating "Sending new messages to this bot has been disabled by your administration." I am the administrator.




I have spoken to two different Microsoft Support Engineers...


The first Engineer told me that I needed to make sure that "Allow sideloading of external apps" was turned on in Office 365 (Settings > Services & add-ins > Microsoft Teams > Apps). It appears to be turned off, but the option to change anything here is grayed out with a message stating that these settings have been migrated to the new Microsoft Teams Admin Center. This is when the Engineer asked me to create a new case with Office 365 to get this turned on.




I created a new case, spoke to the second Engineer who told me that those settings are now in the Microsoft Teams Admin Center. We navigated there, which I had before, and verified that both "Permission" and "Setup" policies beneath "Teams app" is set correctly.




The second Engineer didn't have an answer and told me that he'd get back to me because the settings are correct. Anyone have any ideas? Any advice is greatly appreciated!

11 Replies

Update: The second Engineer followed up via email with a canned reply, sharing URLs for Microsoft Teams documentation, none of which were related to the issue.

@scsh4 On that "Permission policies" screen, click on the button at the top right "Org-wide App Settings"


This page has more detail for me.

Hi @Angela Detzel and @scsh4,


Did it work for you? I've been trying to make it work for weeks.

All the configuration seems to be ok, but the communication is still not possible.


I'm going to open a ticket with Microsoft and just found this post here.


Do you have any updates about this issue?


Thank you very much!

@Rui Carvalho The last update provided was that they're aware of the problem, are working on the issue, but have no ETA on when it will be resolved; that the problem is with Microsoft Teams.

@scsh4 Same issues I have on my tenant! The Microsoft engineer checked all settings and it seem all right ! But the issues is persistent. He said that he will get back to me... It was last week. Hope this week that I can hear from him. Not sure if he is in India or in the US.

@scsh4 Are you starting a conversation with your QnA bot via its bot ID? That is, as opposed to its name, which requires creating and uploading a manifest/app package?


If so, there is a fix for this being rolled out but it hasn't hit our public version yet. 


The workaround is to create an app package (easiest way is to use the App Studio app) and load your QnA bot that way, by name. 


Bill Bliss

MS Teams Platform Architect

@Bill Bliss: Correct; the way in which I am referring to this is beginning the conversation by the BOT ID. Coincidentally, I heard from the Support Engineer that I have been working with today, who communicated the same thing as you just have. Thanks for your response!

@scsh4  I am also facing same issue. I have build normal conversational Bot it is not like yours QnA bot.


I am also not able to ping that bot from MS-Team.

@Hemanttoday Please post a new question with more details on Stack Overflow, our primary support site: Please tag it with "microsoft-teams".

Hello, @scsh4, you or your Teams admin has to check the box 'Allow interaction with custom apps'.

Teams admin center > Team apps > Manage apps > Org-wide app settings. Find more details on the process here. Screenshots can be helpful too.

If this does not help, try to check and manage app permission policies in Microsoft Teams. More details are here.

One more suggestion is to check all the possibilities to back up and recover in Microsoft Teams to be ready for any unexpected data loss.