Microsoft Teams now supports sending and receiving SMS messages directly inside the Teams chat experience for eligible Microsoft Teams Calling Plan phone numbers. This blog explains what Microsoft Teams SMS is, where it is supported, what prerequisites are required, and how administrators can configure SMS through the Microsoft Teams Admin Center. It also highlights important 10DLC registration requirements, brand and campaign approval steps, number enablement, user experience, reporting, and key limitations.
Microsoft Teams SMS allows users to send and receive text messages from the Teams desktop, web, or mobile app using an eligible Teams Calling Plan number. The feature is currently available for Calling Plan phone numbers in the United States, Puerto Rico, and Canada. Users in those regions can exchange SMS messages with SMS-capable phone numbers that are also regionally assigned in the United States or Canada.
As part of the broader Microsoft Teams Phone experience, SMS capabilities help organizations streamline business communication within a single collaboration platform.
It is important to understand that SMS in Teams is treated as business messaging, also referred to as Application-to-Person (A2P) Messaging, and is not categorized as consumer SMS messaging. Because of this, organizations must complete 10DLC Registration before enabling SMS on Teams Calling Plan numbers.
In the United States, carriers require business SMS sent from 10-digit long-code numbers to be registered through the 10DLC network. This process helps carriers validate the organization and the intended SMS use case before messages are allowed through the carrier network.
Microsoft facilitates this process through The Campaign Registry (TCR) using information submitted in the Microsoft Teams Admin Center.
The 10DLC Registration process has two major parts:
| Step | Purpose |
| Brand Registration | Validates the organization or business entity |
| Campaign Registration | Validates the SMS use case, message flow, opt-in process, and SMS compliance details |
Microsoft also states that administrators need one of the supported Teams RBAC roles to create SMS Brand Registration and SMS Campaign Registration records and manage Teams SMS services.
Step 1: Create a Brand
The first step is to create a Brand in the Microsoft Teams Admin Center. The Brand represents the legal business entity that will send SMS messages using Microsoft Teams SMS.
During SMS Brand Registration, administrators provide organization details such as:
Microsoft notes that the information entered should match the organization’s legal registration records, including correct spelling and legal address details.
After submission, the Brand status changes to Submitted, and Microsoft states that the Brand review process may take around two business days, although timelines can vary.
Step 2: Create a Campaign
Once the Brand is approved, administrators can create a Campaign. The Campaign describes how the organization will use Microsoft Teams SMS, including the type of messages sent, target audience, opt-in process, sample messages, and SMS compliance requirements.
For Microsoft Teams SMS, the campaign use case is defined as Unified Communications as a Service (UCaaS), Low Volume, and Microsoft states that the use case cannot be changed.
The SMS Campaign Registration submission typically includes:
| Campaign Item | What to Provide |
| Campaign description | Explanation of how SMS will be used |
| Target audience | Who will receive messages |
| Call to Action | How recipients opt in |
| Privacy Policy URL | Publicly accessible SMS privacy policy |
| Terms & Conditions URL | Publicly accessible SMS terms |
| Sample messages | Examples aligned with the use case |
| Opt-in message | Automated message sent when SMS starts |
| Opt-out message | Automated response when recipient sends STOP |
| Help message | Automated response when recipient sends HELP |
| Content attributes | Whether messages include links, phone numbers, lending content, or age-gated content |
Microsoft specifies that Teams SMS Campaign registration is intended for SMS-enabled phone numbers assigned to individual employees for one-to-one conversations and does not support marketing, bulk messaging, automated alerts, or API-driven interactions.
Step 3: Enable SMS on a Phone Number
After the Brand and Campaign are approved, SMS can be enabled on eligible Microsoft Teams Calling Plan phone numbers.
In the Microsoft Teams Admin Center:
Microsoft identifies several SMS status values for phone numbers, including Not Available, Not Activated, In Progress, and Activated.
Teams SMS activation can take up to two hours when the number status is In Progress.
Once SMS is activated for a user’s phone number, the user can send and receive Microsoft Teams text messages directly inside Microsoft Teams.
As part of the Microsoft Teams Phone experience, Teams SMS supports one-on-one business conversations, allowing employees to communicate with customers and partners without leaving the Teams environment. Microsoft states that SMS in Teams is supported for one-on-one chat conversations.
Teams SMS has several important limitations that should be understood before deployment:
| Limitation | Detail |
| Supported numbers | Teams Calling Plan numbers only |
| Supported regions | United States, Puerto Rico, and Canada |
| Conversation type | One-on-one SMS conversations only |
| MMS support | MMS, attachments, emojis, stickers, and GIFs are not currently supported |
| Sender types | Toll-free numbers, short codes, and alphanumeric sender IDs are not currently supported |
| Tenant campaign limit | One Brand and one Campaign are allowed per tenant |
| Default number limit | Campaign supports up to 49 SMS-enabled Calling Plan numbers by default |
Organizations planning a Teams Phone deployment should review these limitations before enabling Microsoft Teams SMS for end users.
The biggest learning from configuring SMS on Microsoft Teams Calling Plan Numbers is that SMS enablement is not just a toggle on a phone number. It requires compliance preparation first.
The Brand validates the organization, while the Campaign validates the messaging use case. Only after both 10DLC Registration components are approved can administrators enable SMS on eligible Teams Calling Plan numbers.
Another important point is that Microsoft Teams SMS is designed for one-to-one employee messaging, not bulk SMS campaigns, marketing blasts, automated notifications, or API-driven messaging. Organizations needing those use cases should evaluate alternative enterprise SMS solutions or specialized integrations.
By understanding the requirements for SMS Brand Registration, SMS Campaign Registration, and SMS Compliance, organizations can successfully deploy business messaging capabilities within Microsoft Teams Phone and improve communication efficiency.