What impact will the deprecation of multi-tenant chatbot applications built with the Bot Framework, particularly those deployed in Microsoft Teams?

Question

As recommended by a Microsoft representative, I’m sharing this question here again

I’ve gone through the response from Microsoft in the following thread in Stack Overflow and Microsoft Community, but they don’t clearly outline how the deprecation of multi-tenant support will affect existing bot applications built using the Bot Framework with C# or Python.

I need some clarification on the following points.

• All of our existing bots are currently built on a multi-tenant architecture. Based on the comment, "Incoming webhooks are also deprecated by the end of 2025," does this mean that all incoming requests to these bots will stop working after 2025? Or is the deprecation referring to something else? In that case, we may need to migrate all our existing multi-tenant bots to either single-tenant or user-assigned managed identity models ?.
• Based on my previous experience, the Bot Framework typically requires a multi-tenant setup for authentication, as the authentication process often involves handling requests from different tenants. This was also highlighted by a Microsoft employee in a forum response. Given this, I’m concerned about how the deprecation of multi-tenant support will affect our scenario. If we switch to a single-tenant model, authentication may fail. Is there an alternative solution or recommended approach to handle this situation without breaking existing functionality?
• Please note that our bots are built with highly customized conversational flows, including multiple dialog-level interactions. The logic is quite complex and integrates with RAG (Retrieval-Augmented Generation) and various business-specific APIs. At this stage, migrating to the Microsoft 365 Copilot/Agent SDK (the upgraded version of the Bot Framework) is not a viable option for us, primarily because it won't support for adaptive dialog flows, which are critical to our implementation.

The below screenshot BotFramework is not even highlighted in single tenant and user assigned object only part of multi-tenant app. this is creating to much confusions and risk for existing and new app going to develop.

Answer 1

Hi @Rajeesh M R

Thanks for reaching out to Microsoft Q&A Forum support 

Based on your description, I've conducted some research, and checked through your Stack Overflow links, and found this discussion on Microsoft Tech Community with answer marked and relevant to your context. 

Link discussion: What is the recommended bot type for multi-tenant bots? | Microsoft Community Hub 

I also double checked across other sources to see if there might be an alternative approach, but unfortunately, I wasn’t able to find any additional guidance. At this point, the Tech Community's response is the only direction I can confidently point to. I understand this might not be ideal, and I’m sorry for the inconvenience. As a forum moderator, I’m here to help guide discussions and share information based on Microsoft documentation and community knowledge, but I don’t have access to internal product insights or the ability to give the precise answer from a developer perspective. 

In case the Tech Community answer doesn’t fully address your concerns, I’d recommend following up directly on that thread to ask for clarification. And if you still need a more definitive answer, the best next step would be to open a Unified Support ticket here: 

Link: Unified Support 

Please note that this is a paid support ticket, which means it requires an active support plan or a one-time support purchase. However, the benefit of using this channel is that your inquiry will be routed directly to the Microsoft Product Group responsible for the specific service or feature in question. This team includes engineers and developers who work on the product itself, so they are best positioned to provide accurate, in-depth, and authoritative answers especially for complex or edge-case scenarios that go beyond publicly available documentation or community knowledge. 

Additionally, just to clarify the scope of support available for your information: 

• Teams Admin Center: You can submit a free support ticket here, but it's primarily intended for issues directly related to Microsoft Teams functionality. It doesn’t cover development-related questions or architectural guidance. 
• Microsoft Q&A: This forum is a great place for community-driven support and advice based on publicly available documentation and research. However, we don’t have access to internal database or the ability to provide insights from the product engineering teams. 

That said, the two most reliable paths forward are either checking the Tech Community post, which includes input from Microsoft engineers, or submitting a Unified Support ticket to connect directly with the Product Group. This ensures you get the most accurate and authoritative answer, especially for more technical or complex scenarios. 

Hope you will solve the problem soon. 

---

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.