17 · Ecosystem
A picture of the estate stops you from buying a second phone system by accident.
The map puts Entra ID and Cloud Voicemail beside Teams Phone, the dial plan in front of routing, the SBC between Teams and the carrier, and emergency location on that SBC path. Attendants, Dynamics, ACS, Copilot Studio, recording, WFM, Power BI, and the CRM sit on named edges.
Click a node in the map view. The edge label is the thing that has to be true: user homed online, TLS 5061, a licensed resource account, a policy bot, queue intervals. If you cannot point at the edge, you do not understand the integration.
Use the mind map. Every edge is a requirement, not decoration.
I can draw Teams, the SBC, the carrier, and the six sister systems without notes.
If it fails: A design has no picture, so recording and E911 are discovered after go-live.
Which description of Existing calls are unaffected is accurate?
When you grant a compliance recording policy, calls and meetings already up are not swept in. Test with a new call. A pilot that reuses an open meeting proves nothing. Source: https://learn.microsoft.com/en-us/powershell/module/teams/new-csteamscompliancerecordingpolicy?view=teams-ps accessed 2026-10-14.
A colleague reports: The pilot says recording failed because they watched an old meeting. Where do you start?
The pilot says recording failed because they watched an old meeting. Place a fresh call after the grant and confirm the bot joined. Source: https://learn.microsoft.com/en-us/powershell/module/teams/new-csteamscompliancerecordingpolicy?view=teams-ps accessed 2026-10-14.
Which description of Quality management is accurate?
Listening to and scoring recorded interactions. Often the same vendor as compliance recording, sometimes a separate one. QM needs the recording first. A score without audio is a rumor. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-recording-policy 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.
A design has no picture, so recording and E911 are discovered after go-live.
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.
