Modern enterprise voice architectures deployed on Microsoft Teams Phone increasingly incorporate multi-carrier peering solutions. Rather than routing all enterprise Public Switched Telephone Network (PSTN) voice traffic through a single global telecommunications provider, multinational corporations often contract with multiple tier-1 telecommunications carriers (such as AT&T, Verizon, Vodafone, BT, and Swisscom) across different regional subsidiaries. Through Operator Connect and direct carrier interconnects, organisations route domestic calls through local carriers to minimise toll costs and comply with national telecommunications regulations.
Governing how user accounts, branch offices, and corporate departments map to specific telecommunications carrier services requires granular administrative policies. In Microsoft Teams, administrators manage carrier peering boundaries and user routing entitlements via the CsTeamsCarrierServicePolicy cmdlet family. Using PowerShell, administrators can inspect existing carrier service configurations, define scoped carrier policies for regional departments, and assign routing policies to licensed Teams Phone users. This guide explains how Teams Carrier Service Policies operate and details how to manage them using the Microsoft Teams PowerShell module.
Architecture of Teams Carrier Service Policies and Multi-Carrier Peering
Teams Carrier Service Policies govern the programmatic relationship between Microsoft 365 cloud PBX users and certified telecommunications operator services:
- Operator Peering Segregation: In enterprise tenants with multiple active carrier relationships (e.g. Carrier A in North America and Carrier B in Europe), carrier service policies ensure that European sales teams cannot inadvertently provision numbers from North American trunk pools, preventing regulatory licensing violations.
- Carrier Service Capabilities: Policies define what tier of carrier telecommunications features a user cohort is permitted to consume, such as standard PSTN two-way calling, international dialing, emergency E911 services, and mobile cellular SIM integration.
- CsTeamsCarrierServicePolicy Cmdlet Family: Operates at the tenant level (
Global) and custom policy level (Tag:<PolicyName>). Administrators can define policies and grant them to individual users or synchronize them across user cohorts via Entra ID security groups.
Configuring carrier service policies via PowerShell ensures that voice routing adheres to corporate compliance baselines, preventing unauthorized trunk access and streamlining multi-carrier lifecycle management.
Prerequisites and PowerShell Module Connection
Managing carrier service policies requires Microsoft Teams PowerShell module version 4.9.0 or later and an account assigned the Teams Administrator or Global Administrator role in Microsoft Entra ID.
Open an elevated PowerShell prompt and check your module version:
Get-Module -ListAvailable -Name MicrosoftTeams
If required, install or update the module from the PowerShell Gallery:
Install-Module -Name MicrosoftTeams -Force -AllowClobber -Scope CurrentUser
Authenticate to your Microsoft Teams tenant:
Connect-MicrosoftTeams
Confirm your active administrative connection:
Get-CsTenant | Select-Object DisplayName, TenantId
Inspecting Current Carrier Service Policies
Before introducing new carrier assignments, audit existing tenant policies using Get-CsTeamsCarrierServicePolicy:
Get-CsTeamsCarrierServicePolicy
PowerShell outputs configured policy definitions:
Identity : Global
Description : Default tenant-wide carrier peering configuration
AllowCarrierIntegration : True
CarrierServiceType : Standard
Identity : Tag:EMEA-Vodafone-Policy
Description : Routes European voice traffic through Vodafone Operator Connect
AllowCarrierIntegration : True
CarrierServiceType : OperatorConnect
To inspect a named policy in detailed list format, pass the -Identity parameter:
Get-CsTeamsCarrierServicePolicy -Identity "Global" | Format-List
Creating Custom Scoped Carrier Service Policies
Best practice in multinational enterprise governance dictates leaving the default Global policy restricted and creating dedicated regional policies mapped to specific carrier contracts.
To create a new carrier service policy for an American corporate branch utilizing AT&T or Verizon operator peering, execute New-CsTeamsCarrierServicePolicy:
New-CsTeamsCarrierServicePolicy `
-Identity "NA-Carrier-Policy" `
-Description "Governs North American user routing for Operator Connect carrier services" `
-AllowCarrierIntegration $true
To create a restricted policy for temporary workers or contract personnel whose accounts should not be permitted to bind carrier-managed mobile numbers or direct carrier features:
New-CsTeamsCarrierServicePolicy `
-Identity "Contractors-RestrictedCarrier" `
-Description "Restricts carrier service integrations for external contractors" `
-AllowCarrierIntegration $false
Modifying Existing Policy Attributes
If policy terms change—such as when extending carrier capabilities or transitioning user cohorts during telecommunications contract renegotiations—use Set-CsTeamsCarrierServicePolicy to update active configurations:
# Update description and ensure integration is active
Set-CsTeamsCarrierServicePolicy `
-Identity "NA-Carrier-Policy" `
-Description "Updated North American Operator Connect peering policy" `
-AllowCarrierIntegration $true
To immediately revoke carrier service access across a named cohort during security investigations or carrier outages:
Set-CsTeamsCarrierServicePolicy -Identity "NA-Carrier-Policy" -AllowCarrierIntegration $false
Granting Carrier Service Policies to Users and Groups
Once defined, carrier service policies must be granted to licensed Teams Phone users using Grant-CsTeamsCarrierServicePolicy.
Assigning Policy to an Individual User
To assign the North American carrier policy to a specific employee via their User Principal Name (UPN):
Grant-CsTeamsCarrierServicePolicy `
-Identity "[email protected]" `
-PolicyName "NA-Carrier-Policy"
To remove an explicit policy assignment and revert the user to the tenant-wide Global policy default, pass $null:
Grant-CsTeamsCarrierServicePolicy `
-Identity "[email protected]" `
-PolicyName $null
Automating Large-Scale Assignments via Entra ID Security Groups
In enterprise organizations with thousands of distributed knowledge workers, assign policies dynamically based on group membership using New-CsGroupPolicyAssignment:
# Retrieve the Object ID of the target Entra ID regional security group
$groupId = (Get-MgGroup -Filter "DisplayName eq 'North America Sales'").Id
# Assign the carrier policy to the security group
New-CsGroupPolicyAssignment `
-GroupId $groupId `
-PolicyType TeamsCarrierServicePolicy `
-PolicyName "NA-Carrier-Policy" `
-Rank 1
Group-based policy assignments automatically apply the appropriate carrier policy as new users are provisioned into the security group, eliminating manual administrative overhead.
Verifying User Policy Assignments and Phone Telemetry
After granting the carrier policy, confirm that the assignment is successfully reflected on the user’s online directory object:
Get-CsOnlineUser -Identity "[email protected]" | Select-Object DisplayName, UserPrincipalName, TeamsCarrierServicePolicy, LineURI, EnterpriseVoiceEnabled | Format-List
Expected output confirms the policy association:
DisplayName : Michael Chang
UserPrincipalName : [email protected]
TeamsCarrierServicePolicy : NA-Carrier-Policy
LineURI : tel:+12125550188
EnterpriseVoiceEnabled : True
Once verified, the user’s phone identity can be synchronized with the operator portal, providing reliable domestic and international voice connectivity across Microsoft Teams.