Forum Discussion

Olly1212's avatar
Olly1212
Occasional Reader
Jan 26, 2026

How to create an audio calling bot for the Marketplace?

What is the correct set of framework(s)/tools that allow a bot to make audio calls to teams users that can be installed to multiple customer's Teams instances, and added to the Teams Marketplace, as of January 2026?

 

It seems that there is a lot of transition going on in the various bot frameworks that are supported by Microsoft. The new Microsoft 365 Agents https://github.com/microsoft/Agents/issues/377 , and won't do until at least March 2026. The Teams Microsoft Graph Comms libraries still work and appear to be current, however that is only half the puzzle. I need to also package up the bot that has been built, including build an app manifest, etc. The AzureBot still works, but upon packaging up, it seems that Multi-tenant support was https://github.com/microsoft/botframework-sdk/issues/6698. The permissions for the various Microsoft graph https://github.com/microsoftgraph/microsoft-graph-comms-samples  do not match up with the permissions for the packaging of the new agent (e.g. Calls.AccessMedia.All, Calls.Initiate.All are required, but not present). It also isn't clear to me Microsoft Graph App Manifest can help in this matter.

 

Any clarity on the matter would be much appreciated. This is kinda urgent, so can't wait until Agent SDK

 




calling
microsoft teams

1 Reply

  • Prasad_Das-MSFT's avatar
    Prasad_Das-MSFT
    Icon for Microsoft rankMicrosoft
    Jan 27, 2026

    Here’s a clear summary of the current (January 2026) best-practice approach for building an audio calling bot for Teams Marketplace that can be installed in multiple customer tenants:

    1. Frameworks & Tools to Use

    • Microsoft Bot Framework SDK
      • Still supported for Teams bots, including calling/meeting bots.
      • Use Bot Framework v4 with Node.js or C#.
    • Microsoft Graph Communications API
      • Use Microsoft Graph Comms SDK for call control, media access, and signaling.
      • Required permissions: Calls.AccessMedia.All, Calls.Initiate.All, Calls.JoinGroupCall.All, etc.
    • Azure Bot Service
      • Host your bot in Azure Bot Service for scalability and compliance.
    • Teams App Manifest
      • Package your bot as a Teams app using the Teams App Manifest schema.
      • Specify bot endpoints, permissions, and capabilities.

    2. Multi-Tenant Support

    • Bot Framework bots can be made multi-tenant by registering as a multi-tenant Azure AD app.
    • In your Azure AD app registration:
      • Set “Supported account types” to “Accounts in any organizational directory (Any Azure AD directory - Multitenant)”.
      • Grant required Graph permissions (Calls.AccessMedia.All, etc.) as application permissions.
    • When publishing to Teams Marketplace, your app must be multi-tenant and consentable by customer admins.

    3. Packaging for Teams Marketplace

    • App Manifest:
      • Include your bot’s Azure AD app ID, endpoints, and required permissions.
      • List the bot in the bots section of the manifest.
      • Specify webApplicationInfo for SSO if needed.
    • Permissions:
      • Teams app manifest does not directly grant Graph permissions; those are handled via Azure AD app registration.
      • Customers must grant admin consent for Graph permissions after installing your app.
    • Marketplace Submission:

    4. Limitations & Notes

    • Microsoft 365 Agents SDK is not GA until at least March 2026; do not use for production Marketplace bots yet.
    • Graph Comms SDK is still the standard for calling bots.
    • Azure Communication Services Call Automation does not support direct bot-to-Teams user calling for Marketplace bots as of now.
    • App Manifest permissions: Only Azure AD app registration controls Graph permissions, not the Teams manifest.

Resources