Microsoft Teams interop policy for inbound calling selection
Announced and rolled out yesterday, Microsoft have brought PSTN calling to Teams. Previously limited to only the Skype for Business client, this now means you can call mobiles and landlines from the Teams client; whether that’s in the browser, in the Windows application or on your Android or iPhone smartphone. Although not yet in general availability support, however, is the ability to switch the destination of inbound PSTN calls from Skype for Business to Teams; but the capability to allow your users to choose (or indeed to force it upon them) has been released in the form of a Skype for Business and Teams interop policy.
To test inbound calling to Teams in anger, we’ve enabled the user configuration option to select Skype for Business or Teams for our bleeding edge users in the Technology Enablement team and documented it for your convenience.
Here’s what you can do to test it yourself:
Install the Skype for Business Online connector module for PowerShell if you don’t have it already
Sign into Skype for Business Online PSSession
Import the remote PSSession into your shell
Import-PSSession (Get-PSSession 1)
Get-CsTeamsInteropPolicy to check which existing interop policies are available; notice that, by default, there isn’t a policy where
ChatDefaultClient are set to default AND the
AllowEndUserClientOverride = $true
Create a new Teams interop policy which allows the end user to choose their inbound calling client, but still maintain the ‘default’ setting for calling and chat:
New-CsTeamsInteropPolicy -Identity tag:AllowOverrideCallingDefaultChatDefault ` -allowEndUserClientOverride:$true -CallingDefaultClient:Default -ChatDefaultClient:Default
With the policy created, we’ve got to grant this policy to users individually for it to take effect:
Grant-CsTeamsInteropPolicy -PolicyName tag:AllowOverrideCallingDefaultChatDefault ` -Identity email@example.com
In some cases it needs a little while to take affect; grab a drink and stretch your legs
Restart the Teams client a while later and…
…there you have it. You have now allowed your user(s) to choose the destination of inbound PTSN calling, as Microsoft Teams instead of Skype for Business.
About our author
Senior Systems Engineer | Content and CodeOffice 365 has been a primary focus for Ashley for 5 years. Coming from a development background, before moving to infrastructure and SharePoint, Ashley worked as an Identity and SharePoint Consultant for Content and Code for 3 years before shifting to his current role managing the systems and services as our Senior Systems Engineer. He spends time between orchestrating our migration from on-premises to the SaaS or Azure equivalents and keeping Content and Code ahead of the curve with the latest Office 365 and other Microsoft technologies.
The Office 365 productivity suite is made up of many applications that work together to enable a more productive workforce. As such, there are many opportunities to change how employees work - both as individuals and as teams. However, problems can often arise...read more
Digital Transformation in 2018 Masterclass Align your business objectives to Microsoft Technology Date: Thursday, 22nd February | Time: 9.30am – 1pm | Where: Fountain House, 130 Fenchurch Street, London, EC3M 5DJ As the modern workplace advances with new and...read more
I just wanted to share some lessons learned from a recent SharePoint migration project we have undertaken using both the Metalogix Essentials and Content Matrix tools. In this post I will share some potential pitfalls so that hopefully you can rectify these...read more