In January of 2023, Microsoft announced that we will stop supporting the use of Service calling line ID substitution in Caller ID policies in the Teams admin center and in the New-CsCallingLineIdentity cmdlet in the Teams PowerShell Module and we are instead asking customers to use the Resource calling line ID substitution. In this first phase, announced by MC505122 (now archived), we removed the ability to create new Caller ID policies with Service calling line ID substitution.
In April of 2023, Microsoft announced the second phase of the retirement via MC545913 (requires Admin sign-in to view) indicating that we will stop honoring Caller ID policies using Service calling line ID substitution.
We have started to rollout the second phase of this retirement which should be complete by end of October.
When this change has been implemented, Caller ID policies using Service calling line ID substitution will no longer be honored and the outbound call will not have any caller ID substitution. We will still honor other settings on a Caller ID policy using Service calling line ID substitution. We will also remove using Service calling line ID substitution from the Teams admin center and in the New/Set-CsCallingLineIdentity cmdlet in the Teams PowerShell Module.
Tenant administrators will need to use the Resource calling line ID substitution. This type of substitution uses the phone number of a resource account associated to an Auto Attendant or Call Queue and it supports both Calling Plan, Direct Routing and Operator Connect phone numbers.
You should change any existing caller ID policies using Service calling line ID substitution to using Resource calling line ID substitution.
For more information, please review the following resources:
Updated Nov 09, 2023
Version 2.0
Rebecca Valdivia
Microsoft
Microsoft
