In enterprise telecommunications, assigning individual direct inward dialling (DID) phone numbers to every user can result in excessive carrier recurring costs and telephone number exhaustion. In scenarios such as retail store floors, manufacturing warehouses, customer service desks, and knowledge-worker environments where external inbound calling is infrequent, organizations require users to initiate outbound public switched telephone network (PSTN) calls and receive incoming transfers using a shared organizational telephone number. Microsoft Teams Phone supports this capability through Shared Calling policies. Managed using the Microsoft Teams PowerShell module with cmdlets such as New-CsTeamsSharedCallingPolicy, Set-CsTeamsSharedCallingPolicy, and Grant-CsTeamsSharedCallingPolicy, voice administrators can link resource accounts, assign calling line identities, and enforce dedicated emergency callback routing across user cohorts.
Architecture of Microsoft Teams Shared Calling
Teams Phone Shared Calling simplifies enterprise PSTN access by decoupling user telephone capabilities from dedicated phone number assignments. Instead of purchasing and assigning individual carrier numbers to each employee:
- Resource Account Binding: An enterprise auto-attendant or call queue resource account is assigned a phone number (via Teams Phone Operator Connect, Direct Routing, or Microsoft Calling Plans) alongside a Teams Phone Resource Account license.
- Shared Calling Policy: Defines the resource account whose phone number is presented as the outbound Caller ID when licensed users place external PSTN calls.
- Emergency Callback Routing: In the event that a user dials an emergency service (such as 999 or 911), the policy specifies an Emergency Callback Number (ECBN) and directs return calls from public safety answering points (PSAP) directly back to an administrative queue or emergency response desk.
- Direct Inward Dialling (DID) Independence: Users assigned the policy only require a standard Teams Phone Standard or Teams Shared Devices license without needing individual phone numbers provisioned on their user account.
Connecting to the Microsoft Teams PowerShell Module
To administer tenant voice and telephony policies, launch an elevated PowerShell session and authenticate with appropriate administrative credentials:
# Install or update the Microsoft Teams module
Install-Module -Name MicrosoftTeams -Scope CurrentUser -Repository PSGallery -Force
# Authenticate to your Microsoft 365 tenant
Connect-MicrosoftTeams
Ensure the executing account holds the Teams Administrator role in Microsoft Entra ID.
Auditing Existing Shared Calling Policies and Resource Accounts
Before deploying a new shared calling policy, review existing tenant configurations and verify that your designated resource account has an assigned telephone number:
# List all existing Shared Calling policies
Get-CsTeamsSharedCallingPolicy
# Verify that the designated resource account has a valid phone number assigned
Get-CsPhoneNumberAssignment -TelephoneNumber "+442079460123"
# Check the resource account identity and license status
Get-CsOnlineUser -Identity "[email protected]" | Select-Object UserPrincipalName, LineURI, EnterpriseVoiceEnabled
The designated resource account must have EnterpriseVoiceEnabled: True and maintain an active telephone number assignment.
Creating a New Teams Shared Calling Policy
To define a new Shared Calling policy, execute New-CsTeamsSharedCallingPolicy, specifying a unique policy name, the resource account object ID, and emergency callback parameters:
# Retrieve the Object ID (or UserPrincipalName) of the resource account
$resourceAccount = Get-CsOnlineUser -Identity "[email protected]"
# Create a Shared Calling policy for United Kingdom branch staff
New-CsTeamsSharedCallingPolicy -Identity "UK-Retail-SharedCalling" `
-Description "Shared calling policy for UK retail store employees" `
-ResourceAccount $resourceAccount.Identity `
-EmergencyNumbers @("999", "112") `
-EmergencyCallbackNumbers @("+442079460123")
The -EmergencyCallbackNumbers parameter ensures that emergency operators can ring back into the primary organizational phone number if an emergency call disconnects unexpectedly.
Modifying an Existing Shared Calling Policy
If you need to update emergency numbers, reassign resource accounts, or add emergency callback numbers to an existing policy, invoke Set-CsTeamsSharedCallingPolicy:
# Update the emergency numbers array for an existing policy
Set-CsTeamsSharedCallingPolicy -Identity "UK-Retail-SharedCalling" `
-EmergencyNumbers @("999", "112", "911")
# Verify the updated policy properties
Get-CsTeamsSharedCallingPolicy -Identity "UK-Retail-SharedCalling" | Format-List
Assigning the Shared Calling Policy to Users
Once the policy is defined, assign it to individual users or batch-assign it across security groups using Grant-CsTeamsSharedCallingPolicy:
# Assign the policy to a single user
Grant-CsTeamsSharedCallingPolicy -Identity "[email protected]" -PolicyName "UK-Retail-SharedCalling"
# Batch assign the policy to all members of a department security group
$groupMembers = Get-MgGroupMember -GroupId "d9a3f2b1-..."
foreach ($member in $groupMembers) {
Grant-CsTeamsSharedCallingPolicy -Identity $member.Id -PolicyName "UK-Retail-SharedCalling"
}
Confirm user assignment by querying user policy status:
# Inspect effective shared calling policy on a user account
Get-CsUserPolicyAssignment -Identity "[email protected]" -PolicyType TeamsSharedCallingPolicy
Removing Shared Calling Policies and Unassigning Users
To revoke a shared calling policy from a user or delete an obsolete policy from the tenant database:
# Revoke the policy from a user (reverting to global default)
Grant-CsTeamsSharedCallingPolicy -Identity "[email protected]" -PolicyName $null
# Delete the shared calling policy from the tenant
Remove-CsTeamsSharedCallingPolicy -Identity "UK-Retail-SharedCalling"
Deploying Teams Phone Shared Calling significantly reduces carrier procurement overhead, simplifies bulk onboarding, and ensures compliant emergency call routing for large user populations across enterprise organizations.