Join a Microsoft Teams meeting from an Azure Communication Services app as an external (bring-your-own-identity) user
domain: learn.microsoft.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Issue your own application-controlled identity for the user (no Entra ID or Teams license required) using the Communication Services Identity SDK to get a Communication access token
Initialize the ACS Calling SDK client with that access token
Call join() against the Teams meeting link/coordinates to join as a guest identity
Handle the constraint that this external-user identity cannot place or receive calls as a native Teams user and has no PSTN support within the meeting
Known gotchas
External users are meeting-join-only — they can't originate/receive standalone Teams calls the way a Teams-licensed identity can
This path is explicitly incompatible with Teams GCC (US Government Cloud) deployments
Don't confuse this with ACS Rooms — Rooms and Teams interop are mutually exclusive; a Room resource can't be used to join a Teams meeting
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?