17 · Ecosystem
Regulated desks need a recorder the user cannot stop. Convenience recording is not that recorder.
Convenience recording is started by a licensed user and stored with the meeting. Compliance recording is a third-party bot invited by policy into new calls, meetings, and events. Microsoft’s comparison, accessed 14 October 2026, says notification is enforced, participant consent is not the compliance control, and audio-only is not the compliance mode. Listed media is voice, video, and screen share. Desktop screen recording, if you need the CRM window, is a separate product you must disclose.
Configuration: a certified recorder, an application instance, a policy created with New-CsTeamsComplianceRecordingPolicy and set enabled, the application attached, then Grant-CsTeamsComplianceRecordingPolicy to the users or groups. Granting the policy does not record if the instance is missing. Existing calls are unaffected. Test a new call. Retention lives in the partner system, not in meeting storage. Quality management scores those recordings with a form the agent has seen.
Compliance recording needs a certified bot, an enabled policy, a grant, and a new test call. It is not the record button.
Compliance recording is a partner bot, a policy, and an application instance. Users do not start it. I test a new call.
If it fails: The policy is assigned and nothing records, because the bot instance was never created.
A colleague reports: Supervisors export recordings to a laptop share. Where do you start?
Supervisors export recordings to a laptop share. Define the form, the sample, and who may listen. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-recording-policy accessed 2026-10-14.
Which description of Workforce management is accurate?
Scheduling and adherence for a queue. It eats interval stats, handle time, and shrinkage. It is not a feature of a Teams user policy. Teams Call Analytics will not staff next Tuesday. Source: https://learn.microsoft.com/en-us/dynamics365/contact-center/ accessed 2026-10-14.
A colleague reports: WFM says you were overstaffed while the queue overflowed, because overflow removed the calls from the count. Where do you start?
WFM says you were overstaffed while the queue overflowed, because overflow removed the calls from the count. Feed offered, answered, abandoned, and handle time from the queue or the CCaaS. Source: https://learn.microsoft.com/en-us/dynamics365/contact-center/ 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.
The policy is assigned and nothing records, because the bot instance was never created.
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.
