08 · Emergency, LBR, survivability
A phone system that cannot reach emergency services is not ready, even if every other demo looks good.
Treat emergency calling as a gate before go-live. Calling Plans in supported countries use Microsoft’s emergency service, and you still load locations. Direct Routing makes you, the SBC, and the carrier responsible for the call.
Do not test by placing a real emergency call. Use the carrier’s test process. Do not send emergency calls into a bot so they can be ‘handled.’ Know whether your recorder includes them, and follow the rule you were given.
Finish emergency location and a local route before go-live. Test with the carrier’s process, not a real emergency call.
Emergency is a gate. I will not demo a bot on the emergency number.
If it fails: 999 matches the IVR workstream.
Which description of Dynamic emergency calling is accurate?
Teams picks a civic address from the network location it can see: trusted IP, site, and subnet in the usual design. A VPN address must not inherit the headquarters address. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
A colleague reports: A laptop on the VPN reports the HQ floor. Where do you start?
A laptop on the VPN reports the HQ floor. Build the topology, assign addresses, and test from a known subnet. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Which description of Civic address is accurate?
The street address you validate for emergency calling. A dispatchable location is specific enough for responders. A campus with one address and five buildings is not specific. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.
999 matches the IVR workstream.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
