Meetings, Webinars, and Calling for Microsoft Teams Administrators

What this guide covers

Microsoft sells Teams as one product, and the Learn overview will describe it in a sentence. What that sentence hides is that Teams is really three communication surfaces stacked on a shared identity and policy engine, and most of the trouble you will hit traces back to not knowing which layer you are standing in. A calling policy applied before the Phone System license propagated. A resource account on the wrong license. A global voice routing policy quietly pulling your Calling Plan users onto an SBC. The portal rarely tells you which layer owns the failure, and the licensing keeps shifting under you: the November 2025 re-bundling of the Enterprise suites and the April 2026 move of features out of Teams Premium into Teams Enterprise both changed what your tenant can do without changing anything you configured.

This book is the connected account the documentation scatters across dozens of pages. It walks the stack from the three product areas and the policy-layering model through the full license gates, meeting and event configuration, PSTN connectivity, dynamic emergency calling, and the voice-routing and call-flow work that keeps callers from being dropped. Every license boundary, capacity ceiling, and portal path is grounded against current Microsoft Learn and validated in a live Microsoft 365 E5 lab. You do not need a production voice deployment to follow along; an E5 trial tenant is enough to build and tear down everything here.

Chapter map

1. The Teams Communication Stack, What It Is and Where It Lives
2. Licensing and Prerequisites, Meetings, Events, and Teams Phone
3. Recommending the Right Meeting Type, Meetings, Webinars, Town Halls, and Virtual Appointments
4. Meeting Policies, Org-Wide Meeting Settings, and Copilot in Meetings
5. Meeting Templates, Meeting Template Policies, and Meeting Customization
6. Webinars and Town Halls, Configuration, Capacity, and Delivery
7. Audio Conferencing, Dial-In for Every Meeting
8. Teams Phone Number Types and PSTN Connectivity Options
9. Acquiring, Assigning, and Managing Phone Numbers
10. Emergency Calling, Locations, Dynamic E911, and Policy
11. Calling Policies, Voicemail Policies, Call Park, and Shared Calling
12. Direct Routing Deep Dive, SBCs, Voice Routing, and Dial Plans
13. Auto Attendants, Call Queues, and the Road to Production

Appendices: PowerShell and Graph Quick Reference; Build a Lab Tenant; Production Readiness Checklist.

Who it is for

Three readers. The Teams administrator or engineer already running meetings and Teams Phone in production, who wants the moving parts connected rather than listed. The IT pro ramping onto the voice stack for the first time and needing one coherent reference. The MS-700 (Managing Microsoft Teams) candidate who wants real depth behind the exam's manage-meetings-and-calling domain, not a cram sheet.

See where you are

7 questions from this guide's territory (3 easy, 4 medium), with the explanation after each. Nothing is stored and nothing is sent anywhere.

The rest of Microsoft Teams Field Guides

One product per book, a lab appendix in every one, and a companion page like this one for each.

• 
  Field guide

  Channels, Chats, and Apps for Microsoft Teams Administrators

  Remove a user from a team and they still show up in the SharePoint site. Delete a chat and it stays discoverable for another 21 days.

  Kindle$12.99Get it on AmazonCompanion page
• 
  Field guide

  Environment and Security for Microsoft Teams Administrators

  Most Teams problems are not Teams problems. A data loss prevention policy scoped to Teams skips channel posts.

  Kindle$12.99Get it on AmazonCompanion page
• 
  Field guide

  Governance, Guest Access, and Devices for Microsoft Teams Administrators

  You enable the guest-access toggle, the Teams admin center reports it as On, and guests still cannot open the Files tab, because the gate you missed lives one portal away.

  Kindle$12.99Get it on AmazonCompanion page
• 
  Field guide

  Monitoring and Troubleshooting for Microsoft Teams Administrators

  Most Teams call-quality tickets stay open too long, and the reason is rarely a hard problem. It is the wrong tool.

  Kindle$12.99Get it on AmazonCompanion page

The hard set (4 questions)

The hardest MS-700 questions this guide publishes, none of them repeated from the placement quiz above: the answer first, why every other option is wrong, and the Microsoft Learn page behind it. The practice book for this exam holds the full bank.

An organization assigns Standard Audio Conferencing licenses to 50 US-based meeting organizers. Partway through the month they report that dialing out ("Call me at") to some international destinations stops working, while dial-out to US numbers still works. What explains this, and what is required to restore international dial-out?

Correct answer: B. Each Audio Conferencing user gets 60 dial-out minutes to Zone A destinations pooled at the tenant level; once the pool is exhausted, or for non-Zone A destinations, Communication Credits (or a Pay-As-You-Go option) are required

A Standard Audio Conferencing license includes 60 outbound minutes per user per month to Zone A countries/regions, pooled across the tenant. Once that pool is exhausted, or for dial-out to non-Zone A destinations, Communication Credits (or a Pay-As-You-Go option) are required to keep placing dial-out calls. US dial-out continuing while some international destinations stop is consistent with running past the pooled/Zone A allowance.

Why the other options are wrong:

• A. Audio Conferencing does include dial-out from meetings ("Call me at"); assigning a Calling Plan to every organizer is not required.
• C. Dial-out from a meeting does not require a per-organizer auto attendant resource account.
• D. The default Microsoft-provided conferencing bridge supports dial-out; switching providers is neither required nor the fix.

Memory hook: AC dial-out = 60 pooled Zone-A min/user/month, then Communication Credits pays overage + non-Zone-A.

Microsoft Learn: Audio conferencing subscription dial out

A call queue's routing method is set to Longest idle. In the queue settings, the Presence-based routing toggle shows Off and is grayed out. An agent who has set their Teams status to Busy still expects to be skipped. What actually happens?

Correct answer: D. Presence-based routing is automatically enforced with Longest idle, so only agents whose presence is Available receive calls.

When Longest idle is the routing method, presence-based routing is required and automatically enabled even though the toggle appears Off and grayed out. An agent counts as 'idle' only when their presence is Available; agents in any other state (such as Busy) are excluded from routing until they return to Available. (Also, when there are fewer calls than available agents, only the two longest-idle agents are presented with each call.)

Why the other options are wrong:

• A. The grayed-out Off toggle is cosmetic; Longest idle forces presence-based routing on, so the Busy agent is excluded, not rung.
• B. Simultaneous ringing is Attendant routing behavior; Longest idle targets the single longest-idle Available agent.
• C. The queue does not silently switch to Serial routing; Longest idle enforces presence internally by design.

Memory hook: Longest idle secretly flips presence-based routing ON - 'idle' means Available.

Microsoft Learn: Aa cq setup call queue

An organization uses Microsoft Calling Plan for PSTN. Security wants a security desk conferenced in (muted) and notified whenever anyone dials 911. A Teams engineer insists they must first build and assign an emergency call routing policy to every user to enable this. Which statement is correct?

Correct answer: C. The security desk conference/notification is configured in the emergency calling policy, which applies to Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing; the emergency call routing policy applies only to Direct Routing.

The Teams emergency calling policy configures the security desk notification experience (who is notified and how - chat only, conferenced in muted, or conferenced in and able to unmute, plus an optional PSTN number) and applies to Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing. The emergency call routing policy configures emergency numbers and PSTN routes and applies only to Direct Routing (assigning it to Calling Plan users has no effect). The engineer has the two policies backwards.

Why the other options are wrong:

• A. The emergency call routing policy is Direct Routing-only and does not enable notifications. Security desk notification is configured through the emergency calling policy, which the scenario needs.
• B. Security desk notification is configured via the emergency calling policy in the Teams admin center or PowerShell; it is not gated behind a Teams Premium license.
• D. Security desk notifications are explicitly available with Microsoft Calling Plans, Operator Connect, and Direct Routing - not Direct Routing only. Calling Plan fully supports this.

Memory hook: Security desk notify = emergency CALLING policy (all PSTN types). Emergency call ROUTING policy = Direct Routing only (numbers/routes).

Microsoft Learn: Manage emergency calling policies

Your organization uses Direct Routing. You must (1) define the emergency dial strings and route emergency calls to a dedicated SIP trunk, and (2) automatically notify the security desk and let them listen in whenever a user dials 911. Which policy or policies accomplish both requirements?

Correct answer: D. A Teams emergency call routing policy (with a PSTN usage) for the emergency numbers and routing, plus a Teams emergency calling policy for the security-desk notification.

For Direct Routing, the emergency CALL ROUTING policy defines the emergency dial strings, dial masks, and PSTN usage that routes the call to the correct trunk. The emergency CALLING policy configures the security-desk notification experience - who is notified and whether they can listen in. Both requirements therefore need both policies.

Why the other options are wrong:

• A. The emergency calling policy configures notification only; it does not define the emergency numbers or PSTN routing that Direct Routing requires.
• B. The emergency call routing policy does not configure security-desk notification; that is the emergency calling policy's job.
• C. Those are general calling and voice-routing policies, not the emergency-specific policies needed here.

Memory hook: Routing policy = where the call goes (Direct Routing); Calling policy = who gets notified.

Microsoft Learn: Configure dynamic emergency calling