Voice LabTeams Phone

17 · Ecosystem

Configuring an ecosystem change

A voice change that ignores the sisters will pass a test call and fail the business.

Room HTMLAll downloads

Learn it in 5 minutes

Write the change as a list: tenant, license, route, emergency subnet, recording policy, queue or workstream, CRM field, and the rollback. Do the lab version first. Read effective policy after each grant. Acquire resource-account licenses even when the price is zero.

Include the certificate expiry and the holiday calendar if the change touches an attendant. Include shrinkage if the change adds a queue. A test call by itself is not an ecosystem test.

Configure an ecosystem change as a list: route, location, recorder, CRM, and rollback. A single test call is not enough.

Room HTML

Visual

ACS call automationAnswerPlayRecognizeDTMFTransferHang up
Events, not a phone tree hidden in a form. Configuring an ecosystem change still needs a human escape.
Change listRoute · VoiceLocation · E911Recorder · If regulatedCRM field · If poppedRollback · Always
Minimum rows. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

My change list names the sisters, not only the SBC.

  1. List All sisters touched
  2. Lab First
  3. Read back Effective policy
  4. Rollback Written

If it fails: The pilot is declared production because one test call worked.

Checklist HTML

Quiz

Which description of Average handle time is accurate?

A colleague reports: The Erlang sheet uses talk time only and the agents never finish wrap-up. Where do you start?

Which description of Policy recording bot join is accurate?

Flashcards

Ecosystem

Glossary

  • Convenience recording A user starts a recording of a call, meeting, or event. Policy can allow it. The user can stop it. Storage follows meeting rules. Config: Set the meeting, calling, and events policies on purpose. Fault: A regulated desk is told to ‘just hit record.’
  • Compliance recording A third-party recorder is invited by policy into new calls, meetings, and events. The user does not start it and participant consent is not the control. Notification is enforced. Config: Create the application instance, enable the policy, grant it, and test a new call. Fault: The policy is granted and nothing records because the bot instance was never created.
  • Compliance recording application The bot instance of a certified recorder. The policy references it. Without it, granting the policy does not record. Config: New-CsTeamsComplianceRecordingApplication attaches it to the policy. Fault: Recording works in the vendor’s cloud and never joins the Teams call.
  • Existing calls are unaffected When you grant a compliance recording policy, calls and meetings already up are not swept in. Test with a new call. Config: Place a fresh call after the grant and confirm the bot joined. Fault: The pilot says recording failed because they watched an old meeting.

Sister technologies

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.

Config and troubleshooting

The pilot is declared production because one test call worked.

Cross-platform bridges

CUCM

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.

Webex

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.

UCCE

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.

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem

Sources and go deeper

Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.

sources.json