How to build multi tenant teams apps with new changes

[yashgandhi-32]

Hy teams after new changes how to build multi tenant apps

I put single tenant in azure bot but what to select in entra app so that any org can use it

also what should be in code

I am using this

createBotFrameworkAuthenticationFromConfiguration(
        null,
        new ConfigurationServiceClientCredentialFactory({
          MicrosoftAppId: configService.get<string>('MICROSOFT_APP_ID'),
          MicrosoftAppPassword: configService.get<string>(
            'MICROSOFT_APP_PASSWORD',
          ),
          MicrosoftAppTenantId: configService.get<string>(
            'MICROSOFT_APP_TENANT_ID',
          ),
          MicrosoftAppType: configService.get<string>('MICROSOFT_APP_TYPE'),
        }),
      ),

what should we put here..can u help its becoming so confusing to understand new changes

[m365-agent-toolkit-assistant]

👋 Hi @yashgandhi-32,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Building a multi-tenant Teams app has changed due to Azure Bot multi-tenant deprecation. Here’s what’s needed:

Azure Entra App Configuration:

• In the Entra app Authentication settings, select Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant).
  • This lets any org use your app.
• For Azure Bot resource, you must set an App Tenant ID—Bots are now single-tenant only.

Code Configuration:

• Set MicrosoftAppType: "SingleTenant" and provide your home tenant ID for MicrosoftAppTenantId.
  • Example:

    createBotFrameworkAuthenticationFromConfiguration(
      null,
      new ConfigurationServiceClientCredentialFactory({
        MicrosoftAppId: ...,
        MicrosoftAppPassword: ...,
        MicrosoftAppTenantId: "...",      // Your own tenant ID
        MicrosoftAppType: "SingleTenant"  // Not "MultiTenant"
      })
    )

• You can only test in your own tenant; cross-tenant sideloading isn’t supported with new bots. For global use, publish to Teams App Store.

References & details:

• Multi-tenant change discussion
• MS Docs: Publishing Teams Apps

If you need further help, share: your dev environment, toolkit version, and error logs.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

Hello @yashgandhi-32,

To enable your Teams Bot for multi-tenant access across any organization, follow these steps:

1. Entra App Registration

Go to Supported account types.
Select: Accounts in any organizational directory (Multitenant) 
See: https://learn.microsoft.com/en-us/security/zero-trust/develop/identity-supported-account-types

2. Bot Code Configuration (.env / config)

Set these values:

MicrosoftAppType=MultiTenant
MicrosoftAppTenantId=
MicrosoftAppId=<your-app-id>
MicrosoftAppPassword=<your-secret>

For a multi-tenant setup, leave the tenant ID field blank (do not enter your tenant ID).

Reference: Add authentication to a bot in Bot Framework SDK - Bot Service | Microsoft Learn

3. OAuth / SSO Configuration

In Azure Bot → OAuth Connection → Tenant ID, enter: common

(For multi-tenant apps, use 'common' as the tenant ID.)

Reference: Add authentication to a bot in Bot Framework SDK - Bot Service | Microsoft Learn

Please let us know if you have any further query here.

[yashgandhi-32]

Hi @Nivedipa-MSFT

I registered my Azure Bot as Single Tenant in the Azure Portal, but in Entra ID the app registration is set to "Accounts in any organizational directory (Multitenant)".

I'm using botbuilder@4.15.1 with the following config:

MicrosoftAppType=MultiTenant
MicrosoftAppTenantId=
MicrosoftAppId=
MicrosoftAppPassword=
With this setup I get:

RestError: Authorization has been denied for this request.
However, if I switch to MicrosoftAppType=SingleTenant and provide a MicrosoftAppTenantId, it works.

Question: What is the correct MicrosoftAppType to use when the Azure Bot is registered as Single Tenant but Entra ID is set to Multitenant? Should I be using SingleTenant with a tenant ID, or is there a proper way to make MultiTenant work in this scenario?

[Nivedipa-MSFT]

Hello @yashgandhi-32 - Single tenant/multitenant only applies to the Azure Bot registration type and not the Entra/AAD app used for Bot creation. Entra app can continued to be created as Multi-Tenant (Accounts in any organizational directory (Any Azure AD tenant – Multitenant).
Only for the "Type of App" in Azure bot registration, options are now limited to Single Tenant and User-Assigned Managed Identity.

How to Register a New Bot as Single Tenant
 
1.When creating an Entra app, make sure that it’s still multi-tenant (this is the AAD app). This is what that looks like

Notice that this app is still multi-tenant (option 3) - this will make sure your bot still works beyond Bot Authentication, especially for SSO flows if you’re using the same App.
 

2.Register Your Azure Bot Resource as Single Tenant:
In the Azure portal, select Single Tenant as the bot type.
Enter the App Tenant ID for the tenant where your AAD app is registered.
Save your changes.

 3.Update Your Bot Configuration:
In your bot’s code (Bot Framework SDK v4 or Teams AI SDK), set MicrosoftAppType to "SingleTenant" and fill in MicrosoftAppTenantId with your tenant’s ID.

{
  "MicrosoftAppType": "SingleTenant",
  "MicrosoftAppTenantId": ""
}

Reference: Microsoft-Teams-Samples/samples/bot-conversation/csharp/appsettings.json at main · OfficeDev/Micros…

For JS apps, set the value of tenantId in your .env file.
Reference: Microsoft-Teams-Samples/samples/bot-conversation/nodejs/.env at main · OfficeDev/Microsoft-Teams-Sa…

Please let us know if you have any further query here.