\nEditing the default policy is possible here, as well as creating new custom policies.
\nI personally do not recommend editing the default policy. This is because it is global. I create new custom policies whenever possible.<\/p>\n
<\/p>\n
Create new Caller ID policies<\/h3>\n
Personally, I prefer to do this task via PowerShell. I like to refer to this Microsoft Technet article<\/a>.<\/p>\n In order to simplify this process, I would like to share my personal experience with you.<\/p>\n When creating a new caller ID policy, it is important to know what type of policy it should be. There are four different options:<\/p>\n It is important to know that currently the option “Resource” cannot be configured via the Web GUI of the Teams Admin Center. First, we need the object ID of the resource account for which we want to create our policy. We put the output of the required PowerShell command in a variable:<\/p>\n Note:<\/strong> Of course, the first thing we need to do is connect to our Teams Tenant via PowerShell. The first thing we need is the command:<\/p>\n Then we need the company name, which we can either enter manually or take the exact name from the tenant. Now we can execute the actual command:<\/p>\n As you can see, we need more information for this command. The “Identity<\/strong>” is the display name of the policy that will later be assigned to the user. Now the policy is created, and we can continue with the assignment.<\/p>\n <\/p>\n There are three different ways in which a user can be assigned to the corresponding policy. Another possibility is to use PowerShell here as well. This usually works very well and without problems.<\/p>\n But what if we need to assign 200 (or more) users in 30 (or more) caller ID policies? Note<\/strong>: If you want to remove the existing caller ID policy for several users, you can simply enter $Null<\/strong> in the CSV under PolicyName. This ensures that no caller ID policy is assigned to the corresponding user.<\/p>\n <\/p>\n The format of the CSV is also displayed again.<\/p>\n <\/p>\n A window opens where we can comfortably browse for the corresponding CSV.<\/td>\n<\/tr>\n If we have accidentally imported the wrong CSV, we can simply continue with “N” and select a new CSV file.<\/p>\n However, if the information is correct, we continue with “Y”.<\/td>\n<\/tr>\n <\/p>\n\n
\nHowever, since in my case this is the variant I mostly need, I will show my example here.<\/p>\n$ObjId = (Get-CsOnlineApplicationInstance -Identity support@contoso.onmicrosoft.com).ObjectId<\/pre>\n
Connect-MicrosoftTeams<\/pre>\n
\nIf we decide on the second variant, we can do this as follows:<\/p>\nConnect-MsolService\r\n$company = Get-MsolCompanyInformation | select DisplayName<\/pre>\n
New-CsCallingLineIdentity -Identity 6600 -CallingIDSubstitute Resource -EnableUserOverride $false -ResourceAccount $ObjId -CompanyName $company -Description \"6600 Contoso Support\"<\/pre>\n
\nThe “CallingIDSubstitute<\/strong>” describes the type of policy we saw at the beginning of this article.
\nThe “Description” is not a mandatory field, but I recommend including it as well, because it serves as a good basic documentation depending on the naming concept of the policies.<\/p>\nAssigning users to the corresponding caller ID policies<\/h3>\n
\nIf it is a matter of individual users and\/or policies, this can be done via the Admin Portal.<\/p>\n
\nFor individual users, this can look like this, for example:<\/p>\nGrant-CsCallingLineIdentity -Identity \"John.Doe@contoso.com\" -PolicyName 6600<\/pre>\n
\nTo solve this chalange quickly and safely, I have created a PowerShell script.
\nTo use this script, you only need a CSV file which is structured as follows:<\/p>\n\"UserPrincipalName\",\"DisplayName\",PolicyName\u201c<\/pre>\n
Here is how to use the script:<\/h4>\n
\n\n
\n ![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2022\/06\/001.png\")
<\/a><\/td>\nAfter running the script for the first time, we have to accept the licence conditions, otherwise we cannot use this script.<\/td>\n<\/tr>\n \n ![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2022\/06\/002.png\")
<\/a><\/td>\nNow the script asks us whether we want to connect to our Teams tenant. If we already have a connection to Microsoft Teams in the existing PowerShell window, we can continue here with “N”, otherwise we select the option “Y”.<\/td>\n<\/tr>\n \n ![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2022\/06\/003.png\")
<\/a><\/td>\nIf we have selected the option “Y”, we must now log on to the tenant.<\/td>\n<\/tr>\n \n ![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2022\/06\/004.png\")
<\/a><\/td>\nAfter the successful login, the script now starts its work and asks for the corresponding CSV, as described in this article.<\/p>\n \n ![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2022\/06\/005.png\")
<\/a><\/td>\nAfter the import is complete, the script shows us the entire import again, so that we can check it again if necessary.<\/p>\n \n ![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2022\/06\/006.png\")
<\/a><\/td>\nNow the policies are created as entered in the CSV and displayed individually in the PowerShell window.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n