17 · Ecosystem

Integration maps

A goal implies a set of systems. Naming them prevents a tool from being asked to do a job it does not have.

Room HTMLAll downloads

Learn it in 5 minutes

Recording regulated calls implies a certified recorder, an application instance, a policy, the users in scope, and a Call-ID. A CRM pop implies E.164 and middleware. Staffing implies queue intervals and shrinkage. WAN survival implies Direct Routing and an SBA. A bad building implies CQD and the subnet map. A bot implies an escape and a queue.

The integration-map lab asks you to pick the goal and read that list. If your design’s list is shorter, the missing row is the future incident.

For each goal, name the systems and the identifier. A shorter list is a future incident.

Room HTML

Visual

Call queue routingCall queueAttendantAgent 1Agent 2Agent 3Agent 4Timeout to overflow
Attendant distribution for Integration maps. Overflow is a configured target.
Goals to systemsRecord · Five checksPop · Number, CRM, id, pathSurvive · SBA path
Use the lab for the full list. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

I start from the goal and list the systems, including the identifier.

  1. Goal One sentence
  2. Systems The short list
  3. Identifier How logs join
  4. Missing row The incident you will have

If it fails: The design’s list is shorter than the goal requires.

Checklist HTML

Quiz

A colleague reports: The prompt says ‘say agent’ and the recognize step has no such intent. Where do you start?

Which description of Certificate expiry seam is accurate?

A colleague reports: OPTIONS fail on a Saturday and the dial plan is blamed. Where do you start?

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 design’s list is shorter than the goal requires.

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