The Microsoft Dynamics 365 and Microsoft Teams connector entries

Verified 2026-09-05 · 7 claims · sources tier 2

Also known as Private key certificate, Privileged Role Administrator.

A Microsoft Dynamics 365 connector record holds configuration fields including a name, a resource domain, a fixed grant type, a client identifier, certificates, a token URL, and a scope 2. In contrast, the Microsoft Teams integration relies on an Azure authorization flow rather than Control Hub credential fields 4.

Microsoft Dynamics 365 connector setup

A Microsoft Dynamics 365 connector record holds a name, a resource domain, a grant type fixed to client credentials with a certificate, a client identifier, a public key certificate, a private key certificate, a token URL, and a scope 2. Cisco states that after a successful connectivity check, the system saves the Microsoft Dynamics 365 credentials and displays a confirmation message 1.

Microsoft Teams integration setup

The Microsoft Teams integration is set up through an authorisation and consent flow against Azure and exposes no name, client identifier, or secret field in Control Hub 4. The only role the Microsoft Teams integration names is an Azure role, Global Administrator or Privileged Role Administrator, rather than a Control Hub or Webex Contact Center role 7.

WarmTransfer's reading of the sources is that the Microsoft Teams entry is the only one of the connector types whose article is titled as an integration rather than as configuring or creating a connector, and it carries no Flow Designer activity that consumes it 5. In the field, the Microsoft Teams presence state mapping is published as an image rather than as text or a table, so its values cannot be recovered from the article's text 6.

Connector limits

Neither the Microsoft Dynamics 365 nor the Microsoft Teams article publishes a maximum number of connectors of its type 3.

See also

See also What each Webex Contact Center connector type stores. See also Webex Contact Center integration connectors. See also Webex Contact Center Flow Designer architecture.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-05. The deployment model is not covered by any claim in this article.

What remains uncertain

What deleting the Teams connector does to the Azure-side grant is not covered by any claim in this article. In the field, the Microsoft Teams presence state mapping is published as an image rather than text or a table, so its values cannot be recovered from the article's text 6. The ServiceNow connector article the overview lists and never links is not covered by any claim in this article.

WarmTransfer. (2026, September 5). The Microsoft Dynamics 365 and Microsoft Teams connector entries. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-connector-dynamics-and-teams

@misc{warmtransfer-wxcc-connector-dynamics-and-teams,
  title  = {The Microsoft Dynamics 365 and Microsoft Teams connector entries},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-connector-dynamics-and-teams},
  note   = {Verified 2026-09-05}
}