security identity · stub
Identity SSO and directory provisioning for UC
Verified 2026-09-05 · 2 claims · sources tier 2
Stub. This topic has 2 verified claims and no published article. The claims below are exactly what the corpus holds today.
So far, no summary has been generated for this topic. The claims below are what the corpus currently holds.
See also
Referenced by
- Webex published MCP servers for external AI clients — Client identity tokens and integrations both resolve against Webex identity
- CUCM to Webex Calling migration — Users must exist in Webex before a migration task runs
- Microsoft Teams Phone architecture and licensing — Users require a licensed voice-enabled Microsoft 365 identity
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | All Unified CM end users must already be provisioned as Webex users, through Cisco Directory Connector or another mechanism, before the migration task runs. Migrate Unified CM data to Webex Calling · Before you begin / prerequisites | fact | 0.90 | 2026-09-04 |
| 2 | Every scope named across the Meetings, Workspaces and both contact centre server pages appears in the Webex scope catalogue with a matching description, including a platform connection scope described as accessing servers hosted on the agentic platform. Connect to Webex Agentic MCP Servers · server scope tables against the embedded scope catalogue | inference | 0.60 | 2026-09-05 |
Sources
tier 2 current vendor documentation
Connect to Webex Agentic MCP Servers
tier 2 current vendor documentation
Migrate Unified CM data to Webex Calling
Cite this page
APA
WarmTransfer. (2026, September 5). Identity SSO and directory provisioning for UC. WarmTransfer. https://warmtransfer.net/knowledge/identity-sso-provisioning
BibTeX
@misc{warmtransfer-identity-sso-provisioning,
title = {Identity SSO and directory provisioning for UC},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/identity-sso-provisioning},
note = {Verified 2026-09-05}
}