Manage Meetings and Calling
Meetings and live events
Meeting policies control lobby behavior, who can present, recording and transcription, and anonymous join; tenant-level meeting settings supply the defaults those policies inherit. Live events have a separate policy controlling who can schedule events, recording, and third-party encoder support. Audio conferencing adds dial-in coordinates per user through a bridge, PIN, and toll or toll-free numbers, and is distinct from the meeting invite settings themselves.
Phone System connectivity
Connect Teams to the PSTN in one of three ways: Microsoft Calling Plans, Direct Routing over an SBC with SIP trunks, or Operator Connect. Direct Routing configuration order matters: dial plans with normalization rules, then voice routes, then PSTN usages, then a voice routing policy, then assignment to users. Calling policies toggle features such as voicemail, call forwarding, simultaneous ring, and group call pickup, while caller ID policies control the outbound number presented. Emergency calling depends on validated emergency addresses and, for nomadic users, dynamic location lookup.
Auto attendants and call queues are backed by resource accounts that need a phone number and the Teams Phone Resource Account license; the number is then attached to the auto attendant or queue.
Worked example. A user dials 555-0100 and the call fails because the digits reach routing unnormalized. Add a normalization rule that converts the digits to E.164 (+1 5550100) in the dial plan before routing. Remember: dial plans normalize numbers, voice routing policies choose the route.