DeployTelephonyMicrosoft Teams

Microsoft Teams

Put an ElevenLabs agent inside Microsoft Teams.

Overview

Microsoft Teams has no built-in ElevenAgents connector. How you make an ElevenLabs agent reachable in Teams depends on how users should reach it and what infrastructure you can run:

  • a web widget embedded in a Teams tab,
  • a phone number the agent answers (Azure Communication Services),
  • a bot users call by name in Teams (Microsoft Graph media bot).

Choosing an approach

Widget tab

Embed the ElevenLabs agent widget in a Teams tab. Click-to-talk in the Teams client. No telephony, no phone number.

Phone number (ACS)

Users dial a phone number that the agent answers, via Azure Communication Services Call Automation. PSTN, contact-center style.

Calling bot (call by name)

Call or chat with the agent by name in Teams, like a colleague — a Microsoft Graph media bot for voice plus Bot Framework messaging for text.

Comparison

Widget tabPhone number (ACS)Calling bot
How users reach itOpen a Teams tab, click to talkDial a phone numberSearch the bot by name → call
TransportWeb widget (mic in the Teams webview)PSTN → ACS media streamingTeams VoIP → Graph media platform
Phone number requiredNoYes (ACS number)No
HostingStatic HTML on any HTTPS hostLinux bridge (Container Apps)Windows media bot (VM)
EffortLowestMediumHighest (.NET on Windows)
Warm transfer to humanNot built-inYes (add participant)Yes (invite Teams user)
Text chat in TeamsNoNoYes (Bot Framework messaging)

At a glance

Each approach has different access requirements — see the Permissions & roles section in each guide. In short: the widget needs Teams custom-app upload; ACS needs a paid subscription + Contributor; the calling bot needs an Azure Bot, Graph Calls.AccessMedia.All, and admin consent (Global Admin / Privileged Role Admin).