Teams calling - TeamsCallingPolicy issues

Question

Currently having 2 issues with TeamsCallingPolicy

First one changing a users TeamsCallingPolicy keeps reverting to a different policy.

Eg we have one called "AllowCalling" and "Global", we were previously using AllowCalling but now I need to allow the use of sip

When I try to change the Calling policy in Teams Admin Center or Powershell the changes are accepted but then the policy changes right back, not sure why as it's worked for me in the past.

So then I tried to change the settings in the AllowCalling policy, it won't let me do it in the Admin center so I tried using powershell, the command "Set-CsTeamsCallingPolicy -Identity xxxxxx -AllowSIPDevicesCalling $True" works for other policies eg Global, but will not work for the AllowCalling Policy and gives me the following error.

PS C:\WINDOWS\system32> Set-CsTeamsCallingPolicy -Identity AllowCalling -AllowSIPDevicesCalling $True

Set-CsTeamsCallingPolicy : Invalid input parameters Modifying non-Tenant documents is not supported

At line:1 char:1

+ Set-CsTeamsCallingPolicy -Identity AllowCalling -AllowSIPDevicesCalli ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidOperation: ({ ConfigType = ...Configuration }:<>f__AnonymousType84`5) [Set-CsTeamsCallingPolicy], Exception

    + FullyQualifiedErrorId : ClientError,Microsoft.Teams.ConfigApi.Cmdlets.SetCsTeamsCallingPolicy

Answer 1

Dear ARF94,

Good day! Thank you for posting to Microsoft Community. We are happy to help you.

Based on your description, it seems that you are trying to using PowerShell scripts to change a users Teams calling policy to revert to a different one. For issues with PowerShell, we have the dedicated communities that has abundant experience with PowerShell command scripts, we strongly suggest you post this question in PowerShell community support resources - PowerShell | Microsoft Docs. Experts there might be available to tell you why this worked before but not it does not work now and provide relevant suggestions and solutions of PowerShell commands to let you know how to make this works again.

Hopefully it works for you.

Sincerely,

Tommy | Microsoft Community Moderator

***Note: In the event that you're unable to reply to this thread, please ensure that your Email address is verified in the Community Website by clicking on Your Account Name > "My Profile" > "Edit Profile" > Add your Email Address > tick "Receive email notifications" checkbox > click on "Save".***