Manage caller ID for users - Microsoft Teams

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies

Published

2026-03-30

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Microsoft Learn terms (CC BY 4.0 for docs content); no-redistribution; short excerpts and locators only

Source notes citing this source

• Microsoft Teams documentation defines caller ID as two user-facing pieces: calling line ID (CLID), the number, and calling party name (CNAM), the name. in context
• For Teams Direct Routing the substituted number and the CNAM are sent in the SIP From header; if the SBC is configured with ForwardPai true, the P-Asserted-Identity header carries the real calling user. in context
• For inbound PSTN calls Teams chooses the displayed caller ID in this order: the called user's People contacts, then Outlook and Entra ID contacts, then the call's calling party name, then its calling line ID. in context
• A Teams caller ID policy's Calling Party Name can be up to 200 characters, but Microsoft notes that downstream systems might support fewer. in context
• Teams sends the configured calling party name only when the caller ID is set to the user's number or a resource account's number and the caller is a Teams user; the Anonymous setting removes both number and name. in context
• Microsoft states that although Teams supports calling party name on outbound calls, delivering CNAM to the called party still depends on PSTN operators. in context
• When Teams detects that an inbound call is possibly spam it presents the caller ID as Spam likely, and this can be turned off in the user's calling policy. in context
• The Teams caller ID policy Calling Party Name can be up to 200 characters, but Microsoft warns that downstream systems might support fewer. in context
• For Direct Routing, Teams sends the substitute number and CNAM in the From header, and if the SBC's OnlinePstnGateway has ForwardPai set to true, P-Asserted-Identity carries the real calling user. in context
• Teams emergency calls always send the user's own calling line ID to the PSAP, whatever the caller ID policy says. in context
• When a Teams user calls on behalf of another account (a delegator, a call queue or shared calling), the caller ID configured for that account replaces the user's caller ID. in context
• A Teams caller ID policy can send the user's assigned number (the default), Anonymous, or a substitute number assigned to a resource account used by an auto attendant or call queue. in context
• The Teams caller ID policy value CallingIDSubstitute = Service is deprecated: new policies cannot use it, existing ones are not honored, and Resource should be used instead. in context
• Teams will not accept as a substitute caller ID any Calling Plan or Operator Connect number whose usage type is User, any Direct Routing number assigned to a user, or any Skype for Business Server on-premises number. in context
• If a Teams caller ID policy has EnableUserOverride on, the user's own hide-my-number setting takes precedence over the other policy settings, in either direction. in context

Cite this source record

APA

WarmTransfer. (2026, March 30). Manage caller ID for users - Microsoft Teams. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-caller-id-policies

BibTeX

@misc{warmtransfer-ms-learn-caller-id-policies,
  title  = {Manage caller ID for users - Microsoft Teams},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-caller-id-policies},
  note   = {Microsoft, accessed 2026-09-24}
}