Forum Discussion
Olly1212
Jan 26, 2026Copper Contributor
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 ...
Prasad_Das-MSFT
Microsoft
Jan 27, 2026Here’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:
- Follow Microsoft Teams Store submission guidelines.
- Ensure your app passes validation for multi-tenant use and permissions.
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.