Deploying enterprise Public Switched Telephone Network (PSTN) connectivity for large organisations often incurs significant licensing and operational expenses. In traditional Microsoft Teams Phone deployments, every employee who requires outbound PSTN calling must be assigned a dedicated direct inward dialling (DID/DDI) phone number alongside a Teams Phone license. However, in many corporate environments—such as retail branches, educational institutions, or corporate back-offices—employees rarely receive inbound direct calls but frequently require outbound dialling capabilities. Microsoft Teams Shared Calling addresses this challenge by allowing groups of licensed users to share an outbound phone number pooled from an Auto Attendant resource account.
Administrators manage this architecture using Microsoft Teams PowerShell through the CsTeamsSharedCallingRoutingPolicy cmdlets. Configuring shared calling routing policies eliminates the overhead of managing individual phone numbers while maintaining enterprise outbound caller ID standards.
Understanding Shared Calling Architecture in Teams Phone
Shared Calling operates by decoupling outbound PSTN calling from individual phone number assignment:
- Resource Account Anchor: A dedicated Teams resource account is provisioned with a Teams Phone Standard resource account license and an assigned telephone number (from Microsoft Calling Plans, Direct Routing, or Operator Connect). This number serves as the shared outbound caller ID and inbound reception entry point.
- Auto Attendant / Call Queue Integration: Inbound calls directed to the shared phone number are routed to an Auto Attendant or Call Queue, allowing external callers to reach employees via company directories or departmental queues.
- Shared Calling Routing Policy: Defines the resource account mapping, outbound emergency calling numbers, and designated emergency location routing for all targeted users.
- Emergency Callback Routing: During an emergency call (such as 999 or 911), Teams routes the call using the user’s validated physical location and dynamically routes any emergency service callback back directly to the specific user rather than the general shared auto attendant.
Connecting to Teams PowerShell and Verifying Prerequisites
To configure Shared Calling policies, launch an elevated PowerShell console and connect to the Microsoft Teams tenant:
# Ensure latest Microsoft Teams PowerShell module is installed
Install-Module -Name MicrosoftTeams -Force -AllowClobber
# Connect to the Teams administrative endpoint
Connect-MicrosoftTeams
Inspect existing shared calling policies to determine the current tenant state:
# List existing shared calling routing policies
Get-CsTeamsSharedCallingRoutingPolicy | Format-Table Identity, Description, ResourceAccount
Preparing the Shared Calling Resource Account
Before creating the policy, verify that the anchor resource account exists, has a Teams Phone license, and has an active telephone number assigned.
Query the resource account details:
# Locate the target resource account
$ResourceAccount = Get-CsOnlineUser -Identity "[email protected]"
# Verify assigned telephone number
$ResourceAccount | Select-Object UserPrincipalName, LineURI, EnterpriseVoiceEnabled
Ensure that the resource account’s LineURI contains the valid E.164 formatted number (for example, tel:+442079460123).
Creating a Shared Calling Routing Policy
Use the New-CsTeamsSharedCallingRoutingPolicy cmdlet to define the policy, linking it to the resource account object ID:
# Create Shared Calling Routing Policy for Regional Office
New-CsTeamsSharedCallingRoutingPolicy `
-Identity "London-Office-SharedCalling" `
-Description "Shared outbound PSTN calling policy for London branch staff" `
-ResourceAccount $ResourceAccount.Identity
To configure emergency calling numbers and ensure dynamic callback routing compliance:
# Define emergency callback numbers on the policy
Set-CsTeamsSharedCallingRoutingPolicy `
-Identity "London-Office-SharedCalling" `
-EmergencyNumbers @{add="999"}
Modifying and Inspecting Policy Configurations
To review the complete policy configuration and verify all mapped parameters:
# Retrieve detailed policy attributes
Get-CsTeamsSharedCallingRoutingPolicy -Identity "London-Office-SharedCalling" | Format-List
If the organisation migrates to a different primary outbound telephone number or assigns a new resource account, update the policy dynamically without disrupting end-user assignments:
# Update policy with a new resource account ID
Set-CsTeamsSharedCallingRoutingPolicy `
-Identity "London-Office-SharedCalling" `
-ResourceAccount "[email protected]"
Assigning Shared Calling Policies to Users
Assign the validated policy to target employees who require outbound PSTN access using the Grant-CsTeamsSharedCallingRoutingPolicy cmdlet.
Assign the policy to an individual user:
# Grant shared calling policy to a specific user
Grant-CsTeamsSharedCallingRoutingPolicy `
-Identity "[email protected]" `
-PolicyName "London-Office-SharedCalling"
Assign the policy across an entire departmental security group or location in bulk:
# Retrieve all retail store employees and assign shared calling
$RetailStaff = Get-CsOnlineUser -Filter {Department -eq "Retail-London"}
$RetailStaff | ForEach-Object {
Grant-CsTeamsSharedCallingRoutingPolicy -Identity $_.UserPrincipalName -PolicyName "London-Office-SharedCalling"
}
To verify the assigned policy on a user account:
# Verify assigned shared calling policy
Get-CsOnlineUser -Identity "[email protected]" | `
Select-Object UserPrincipalName, TeamsSharedCallingRoutingPolicy
By leveraging Shared Calling routing policies in Microsoft Teams, enterprise IT teams deliver reliable PSTN voice connectivity across distributed teams while drastically reducing telecom expenditure and direct dial management overhead.