Teams Bot creation fails with “Multitenant bot creation is deprecated” even when using TDP and Single-Tenant Azure AD app

Hi @Yuvan Kesav A

Thank you for your patience. After reviewing the documentation, a bot configured as single-tenant in Azure Bot Service can still use a multi-tenant application.

Based on the current documentation, the supported approach for new bot registrations is single Tenant and create new multi-tenant bot registrations is not recommended.

For new implementations, this approach should be preferred over attempting to create a new multi-tenant bot registration, since that option has been deprecated.

That said, for any future roadmap changes or updates beyond what is currently documented publicly, it would be best to wait for further confirmation in official documentation.

Thank you.

Hi @Yuvan Kesav A

Based on your description, I understand that your Teams bot creation is failing with the error "Multitenant bot creation is deprecated. Please use SingleTenant or UserAssignedMSI". This is happening despite the fact that you are using the Teams Developer Portal (TDP) and your Azure AD app is explicitly configured as Single-Tenant, a workflow that was previously working without any issues.

To help narrow down the cause, could you please provide a bit more context?

• Did this error suddenly start occurring on an existing bot that was working, or are you encountering this while trying to create a brand-new bot?
• Could you please provide a screenshot of your Azure AD App Registration showing that it is fully configured as Single-Tenant?
• How long ago did you deploy or update this to single-tenant? If it was changed very recently, please wait a short period for the configuration to fully sync across the Microsoft backend services.

While we look into this, please try the following steps to bypass or resolve the issue:

• Instead of using the Teams Developer Portal (TDP) to create the bot registration, try creating the Azure Bot resource directly inside the Azure Portal. Once the Single-Tenant Azure Bot is provisioned there, you can easily link its App ID back to your TDP manifest.
• After moving to a single-tenant architecture, you must explicitly configure your bot's app settings. If the following parameters are missing, the Bot Framework SDK will default to a multi-tenant authentication flow, which will trigger the error.
• Please check if there are any lingering multi-tenant configurations in your tenant. For instance, ensure you aren't reusing an old App ID that was previously set up as multi-tenant, or collaborating with any tenant settings that might still reference a multi-tenant structure.

Please check these configurations and let me know how it goes or if you have any updates!

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.

This is happening because the Teams Developer Portal (TDP) wizard still utilizes a legacy backend provisioning API that implicitly requests a multi-tenant bot channel registration by default—even if your underlying Azure AD app registration is explicitly set to Single-Tenant. Now that Microsoft has fully stripped away the temporary portal exceptions, that automated request is immediately blocked by the new deprecation enforcement rules.

Since the TDP creation wizard is currently broken for single-tenant workflows, you will need to bypass it completely and register the bot manually using the modern Azure framework:

Create the Registration in Azure: Go directly to the Azure Portal, search for Azure Bot, and create a fresh resource. In the creation blade, make sure you explicitly set the app type to Single Tenant or UserAssignedMSI under the configuration settings to align with the new security policy.

Link the Microsoft App ID: Use your existing single-tenant Azure AD App ID during this setup process to keep your current configurations intact.

Connect Back to TDP: Once the Azure Bot resource is provisioned cleanly on the backend, grab its Bot ID, head back into the Teams Developer Portal, open your app manifest, and manually paste the ID into the Bot Connect / Tools section instead of trying to hit "Create Bot".

Taking the manual Azure route completely circumvents TDP's outdated provisioning logic and will get your manifest compiled without throwing any structural errors!