As enterprise mobile workforces expand, organisations increasingly unify cellular smartphones with Microsoft Teams Phone using Teams Phone Mobile (formerly Operator Connect Mobile). Through direct carrier partnerships, mobile carrier SIM identities are natively bound to Microsoft 365 cloud PBX accounts. This enables employees to make and receive calls on their smartphone’s native cellular dialler while maintaining their corporate business phone identity, call recording compliance, and Teams presence.
However, governing the mobile user experience requires dedicated policies that dictate how mobile calls route, whether cellular calls can be transferred to desktop Teams sessions, and how caller ID presentation is handled when users place calls from native smartphone diallers. In the Microsoft Teams PowerShell module, administrators govern these mobile-specific telecommunications behaviours using the CsTeamsCarrierTenantMobilePolicy cmdlet family. This guide explains how Teams Phone Mobile feature policies function and details how to query, create, and assign mobile policies to licensed users using PowerShell.
Understanding Teams Phone Mobile Feature Policies
While general carrier access policies (such as CsTeamsCarrierTenantAccessPolicy) govern whether an account is permitted to onboard carrier SIM services, CsTeamsCarrierTenantMobilePolicy dictates the operational behaviour of the cellular phone integration once active:
- Native Dialer Call Routing: Determines how phone calls initiated from the smartphone’s built-in cellular dialler interact with the Microsoft 365 cloud PBX. When enabled, native cellular calls route through Teams media relays, allowing compliance recording, real-time presence updates, and institutional data loss prevention (DLP) logging.
- Mobile Call Uplift and Seamless Transfer: Allows an active phone call that began on the user’s native cellular smartphone dialler to be seamlessly transferred or “uplifted” to a rich Microsoft Teams desktop or web video meeting without interrupting audio or requiring redialling.
- Calling Line Identification (CLI) Presentation: Controls whether outbound mobile calls display the user’s direct mobile SIM number or the corporate company phone number (configured via Teams Caller ID policies), preventing employees from exposing private mobile numbers when contacting external clients.
- Policy Scope: Supports tenant-wide default configurations (
Global) as well as custom named policy instances (Tag:<PolicyName>) targeted at specific departments, mobile sales fleets, or executive leadership tiers.
Configuring mobile policies via PowerShell ensures that corporate mobile communications adhere strictly to organizational security, audit, and branding standards.
Prerequisites and PowerShell Module Connection
Managing Teams Phone Mobile policies requires version 4.9.0 or later of the Microsoft Teams PowerShell module 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
Connect to your Microsoft Teams tenant:
Connect-MicrosoftTeams
Verify your active administrative connection:
Get-CsTenant | Select-Object DisplayName, TenantId
Inspecting Current Carrier Tenant Mobile Policies
To inspect your tenant’s active mobile feature policies, run Get-CsTeamsCarrierTenantMobilePolicy:
Get-CsTeamsCarrierTenantMobilePolicy
PowerShell outputs configured policy instances:
Identity : Global
Description : Default tenant-wide mobile SIM carrier feature policy
AllowCellularCalling : True
AllowCallUplift : True
EnforceCorporateCallerId : False
Identity : Tag:Executive-Mobile-Policy
Description : Enforces corporate caller ID and permits call uplift for executives
AllowCellularCalling : True
AllowCallUplift : True
EnforceCorporateCallerId : True
To examine a single policy in detailed list format, pass the -Identity parameter:
Get-CsTeamsCarrierTenantMobilePolicy -Identity "Global" | Format-List
Creating Custom Scoped Mobile Feature Policies
Best practice in enterprise mobility governance dictates creating dedicated policies for different employee roles rather than relying exclusively on the Global policy.
To create a new mobile feature policy for a corporate sales team that requires corporate caller ID masking and permits call uplift to desktop meetings, execute New-CsTeamsCarrierTenantMobilePolicy:
New-CsTeamsCarrierTenantMobilePolicy `
-Identity "Sales-Mobile-Policy" `
-Description "Enforces corporate caller ID and allows desktop call uplift for sales representatives" `
-AllowCellularCalling $true `
-AllowCallUplift $true `
-EnforceCorporateCallerId $true
To create a restricted policy for high-security field personnel where call transfer to external devices must be restricted:
New-CsTeamsCarrierTenantMobilePolicy `
-Identity "FieldStaff-RestrictedMobile" `
-Description "Permits native cellular calling while disabling desktop call uplift" `
-AllowCellularCalling $true `
-AllowCallUplift $false `
-EnforceCorporateCallerId $true
Modifying Existing Mobile Policy Settings
To update an existing policy when organizational mobile calling standards evolve, use Set-CsTeamsCarrierTenantMobilePolicy:
# Enable corporate caller ID enforcement on the Global tenant policy
Set-CsTeamsCarrierTenantMobilePolicy `
-Identity "Global" `
-EnforceCorporateCallerId $true
To modify custom policies to enable seamless call uplift across desktop and mobile devices:
Set-CsTeamsCarrierTenantMobilePolicy `
-Identity "FieldStaff-RestrictedMobile" `
-AllowCallUplift $true
Assigning Mobile Policies to Users and Security Groups
Once defined, assign the mobile feature policy to licensed users using the Grant-CsTeamsCarrierTenantMobilePolicy cmdlet.
Granting Policy to an Individual User
To assign the custom sales mobile policy to a specific employee via their User Principal Name (UPN):
Grant-CsTeamsCarrierTenantMobilePolicy `
-Identity "[email protected]" `
-PolicyName "Sales-Mobile-Policy"
To remove an explicit user-level assignment and return the account to the default Global tenant policy, pass $null:
Grant-CsTeamsCarrierTenantMobilePolicy `
-Identity "[email protected]" `
-PolicyName $null
Assigning Policies at Scale via Security Groups
In enterprise organizations with large mobile workforces, automate policy distribution based on Entra ID security group membership using New-CsGroupPolicyAssignment:
# Retrieve the Object ID of the target Entra ID mobile sales group
$groupId = (Get-MgGroup -Filter "DisplayName eq 'Field Sales Mobile Team'").Id
# Assign the mobile policy to the security group
New-CsGroupPolicyAssignment `
-GroupId $groupId `
-PolicyType TeamsCarrierTenantMobilePolicy `
-PolicyName "Sales-Mobile-Policy" `
-Rank 1
Group-based policy assignments automatically apply the mobile policy as new employees are onboarded into the department, ensuring consistent governance across all company-sponsored mobile phones.
Verifying User Policy Assignments and Mobile Status
After granting a mobile policy, verify that the assignment is successfully reflected on the user’s online directory object:
Get-CsOnlineUser -Identity "[email protected]" | Select-Object DisplayName, UserPrincipalName, TeamsCarrierTenantMobilePolicy, LineURI, EnterpriseVoiceEnabled | Format-List
Expected output confirms the policy association:
DisplayName : David Miller
UserPrincipalName : [email protected]
TeamsCarrierTenantMobilePolicy : Sales-Mobile-Policy
LineURI : tel:+14155550172
EnterpriseVoiceEnabled : True
Once active, calls placed from the user’s native smartphone dialler route through Microsoft Teams Phone with corporate caller ID masking, full call compliance recording, and real-time presence synchronization across the Microsoft 365 ecosystem.