17 · Ecosystem
The case is where the business remembers the call. Teams will not open Dynamics for an ordinary PSTN call by itself.
Screen pop is a contact-center or middleware behavior. It looks up a contact from the caller number. That number has to be E.164 after normalization. Store the SIP Call-ID, the queue, and the agent on the timeline. A note that says ‘called customer’ cannot be audited.
Troubleshooting: the wrong contact pops when a trunk prefix is still on the number, or when one human has two caller IDs. Teams Phone extensibility and certified Connect transfers do not remove the need for that identifier. A mailbox legal hold does not retain a partner’s compliance recording.
Pop the CRM from an E.164 number and store the Call-ID. Do not expect an ordinary Teams call to open Dynamics by itself.
Screen pop needs E.164 and should write the Call-ID. Teams alone does not open the case.
If it fails: The pop shows the wrong person because the trunk prefix was left on.
A colleague reports: The pop shows the wrong person because the trunk prefix was still on the number. Where do you start?
The pop shows the wrong person because the trunk prefix was still on the number. Normalize before the lookup. Store the Call-ID on the timeline. Source: https://learn.microsoft.com/en-us/dynamics365/contact-center/ accessed 2026-10-14.
Which description of Call-ID is accurate?
The SIP header that identifies one dialog. It is the join key between an SBC capture, a carrier ticket, and a CRM note. A timestamp is not an identifier. Two calls start in the same second. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
A colleague reports: Support has a CRM case and an SBC log and cannot prove they are the same call. Where do you start?
Support has a CRM case and an SBC log and cannot prove they are the same call. Write the Call-ID into the system you will have open during an incident. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan 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 pop shows the wrong person because the trunk prefix was left on.
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.
