How to Configure Teams SMS Messaging Policies Using PowerShell CsTeamsSmsPolicy

In modern enterprise communications, customer-facing employees (such as sales representatives, recruiters, service technicians, and medical staff) frequently need to communicate with external clients via short message service (SMS) and multimedia messaging service (MMS). Traditionally, employees were forced to use personal cellular devices, exposing personal phone numbers and fragmenting corporate compliance records. Through Microsoft Teams Phone integrated with Operator Connect or Microsoft Calling Plans, organizations can enable two-way SMS messaging directly within the Teams desktop and mobile clients. To govern messaging permissions, compliance recording, and outbound authorization, administrators utilize the CsTeamsSmsPolicy cmdlets in PowerShell.

Understanding Microsoft Teams SMS Architecture and Compliance

SMS messaging in Microsoft Teams operates through an integrated telephony and chat gateway pipeline:

• Dedicated Direct Dial Numbers (DID): Outbound and inbound text messages use the user’s assigned Microsoft Teams Phone DID number. External customers receive texts appearing from a trusted corporate number rather than a personal mobile device.
• Carrier Connectivity: Messages route through participating Operator Connect telco partners or Microsoft Calling Plan trunks that support SMS capabilities.
• Unified Chat Threading: Inbound SMS texts appear directly within the Teams Chat view, displaying the sender’s mobile number and threaded history alongside standard internal collaboration chats.
• Enterprise Compliance & Discovery: All SMS and MMS interactions are indexed by Microsoft Purview, enabling unified eDiscovery, legal holds, communication compliance monitoring, and retention schedules.
• Policy Governance: CsTeamsSmsPolicy controls which user accounts are permitted to send and receive text messages, preventing unauthorized outbound texting from unmonitored roles.

Connecting to Microsoft Teams PowerShell

Configuring SMS policies requires the Microsoft Teams PowerShell module (version 4.9.0 or higher) and Teams Administrator or Global Administrator privileges:

# Import the Teams module and connect to your tenant
Import-Module MicrosoftTeams
Connect-MicrosoftTeams

Confirm that the SMS policy cmdlets are available:

# Verify available SMS policy cmdlets
Get-Command *CsTeamsSmsPolicy*

Inspecting Default SMS Policies

By default, Microsoft Teams tenants contain a Global SMS policy that defines baseline permissions for all unassigned users. Retrieve the Global policy configuration:

# Query the tenant Global SMS policy
Get-CsTeamsSmsPolicy -Identity Global

The policy exposes critical configuration flags:

• Identity: The scope or name of the policy profile (e.g., Global or custom name).
• AllowSms: Dictates whether two-way SMS communication is enabled (Enabled) or blocked (Disabled).
• Description: Administrative comments detailing the operational purpose of the profile.

Creating Custom SMS Policies for Departmental Roles

Because cellular SMS messaging involves carrier per-message fees and regulatory compliance constraints, organizations typically restrict text messaging to designated sales, recruitment, or field service groups.

Use New-CsTeamsSmsPolicy to provision targeted policy tiers:

# Create an SMS enablement policy for customer-facing sales representatives
New-CsTeamsSmsPolicy -Identity "Sales-Recruiting-SMSEnabled" `
    -AllowSms "Enabled" `
    -Description "Permits customer service and sales teams to send two-way SMS via Teams"

To ensure that back-office staff, internal finance, or operational technicians cannot generate unmonitored SMS traffic, enforce a permanent block policy:

# Create an explicit SMS lockdown policy
New-CsTeamsSmsPolicy -Identity "Internal-SMSBlocked" `
    -AllowSms "Disabled" `
    -Description "Strictly prevents outbound and inbound SMS communication"

Modifying Existing SMS Policies

To update the Global baseline or modify an existing policy profile, execute Set-CsTeamsSmsPolicy:

# Enable SMS globally across the tenant
Set-CsTeamsSmsPolicy -Identity Global -AllowSms "Enabled"

# Verify modified settings
Get-CsTeamsSmsPolicy -Identity Global | Format-List Identity, AllowSms

Assigning SMS Policies to Users and Security Groups

Assign SMS policies directly to authorized users or map them across Microsoft Entra ID security groups:

1. Assigning Policy to an Individual User

# Grant SMS policy to a sales representative
Grant-CsTeamsSmsPolicy -Identity "[email protected]" -PolicyName "Sales-Recruiting-SMSEnabled"

# Confirm policy assignment on the user account
Get-CsUserPolicyAssignment -Identity "[email protected]" | Where-Object { $_.PolicyType -eq "TeamsSmsPolicy" }

2. Assigning Policy to a Microsoft Entra ID Security Group

# Deploy SMS policy to an entire customer support security group
Grant-CsTeamsSmsPolicy -Group "9e0f1a23-5c6d-7e8f-9a0b-1c2d3e4f5a6b" `
    -PolicyType TeamsSmsPolicy `
    -PolicyName "Sales-Recruiting-SMSEnabled" `
    -Rank 1

Prerequisites for SMS Enablement on User Numbers

In addition to granting the CsTeamsSmsPolicy, ensure that the user’s assigned phone number supports SMS capabilities through your carrier:

# Query telephone number capabilities on a user account
Get-CsPhoneNumberAssignment -TelephoneNumber "+14155550199" | Select-Object AssignedPstnTargetId, Capabilities

The Capabilities attribute must list SmsEnabled: True. If the carrier trunk is provisioned solely for voice calling, SMS messaging attempts will fail at the carrier routing layer.

Revoking and Removing SMS Policies

Before deleting a custom SMS policy profile, disassociate it from active user accounts:

# Unbind custom policy from user account
Grant-CsTeamsSmsPolicy -Identity "[email protected]" -PolicyName $null

# Delete the custom policy profile
Remove-CsTeamsSmsPolicy -Identity "Sales-Recruiting-SMSEnabled" -Confirm:$false

Configuring Teams SMS Messaging Policies via PowerShell provides organizations with secure, auditable, and carrier-integrated mobile messaging, maintaining corporate compliance while empowering hybrid sales and service teams.