17 · Ecosystem
The glossary is the shared language for the map. Interviews punish fuzzy words.
Each term has a plain definition, a reason it matters, a configuration hint, and a fault you should recognize. Filter by track. If a definition and a vendor blog disagree, open the source link. The access date is 14 October 2026.
Flashcards are the same facts in recall form. Do not treat a card you flipped once as evidence you can operate the system. The lab is that evidence.
Use the glossary to keep words sharp. Recording, for example, is two different features.
I can define the term, the fault, and the document I would open.
If it fails: Two people use ‘recording’ and mean convenience and compliance.
A colleague reports: The policy is granted and nothing records because the bot instance was never created. Where do you start?
The policy is granted and nothing records because the bot instance was never created. Create the application instance, enable the policy, grant it, and test a new call. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-recording-policy accessed 2026-10-14.
Which description of Compliance recording application is accurate?
The bot instance of a certified recorder. The policy references it. Without it, granting the policy does not record. Work with the recorder vendor for the application ID. Do not invent one. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-compliance-recording-setup accessed 2026-10-14.
A colleague reports: Recording works in the vendor’s cloud and never joins the Teams call. Where do you start?
Recording works in the vendor’s cloud and never joins the Teams call. New-CsTeamsComplianceRecordingApplication attaches it to the policy. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-compliance-recording-setup 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.
Two people use ‘recording’ and mean convenience and compliance.
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.
