How to Send SMS From Microsoft Teams in 2026
- Falkon SMS Editorial Team
- Jul 1, 2025
- 16 min read
Updated: Jul 24
TL;DR
Can Microsoft Teams Send Text Messages? Can It Receive Them?
Yes to both. As of 2026, Microsoft Teams can send and receive SMS natively for US, Puerto Rico, and Canada users on a Microsoft Calling Plan number — plain text only, one-to-one, with Brand/Campaign registration required. For MMS, shared inboxes, your existing business number, or team-wide texting, a third-party app like Falkon SMS adds full business texting on top of Teams.
Table of Contents
Native Microsoft Teams SMS: Features, Limits, and How It Works
How to Enable Native SMS in Microsoft Teams (Step-by-Step Admin Guide)
The Limits That Push Most Businesses to a Third-Party SMS App
Calling Plans vs Operator Connect vs Direct Routing: What Each Means for SMS
Industry Use Cases (Healthcare, Legal, Real Estate, Field Services, Finance)
Ready to Unlock Texting Power in MS Teams?
Try Falkon SMS for Teams FREE for 14 days!
What Changed in 2025-2026 (Microsoft Native SMS Update)
If you read older guides, you'll see a common claim: "Microsoft Teams does not natively support SMS." That used to be true. It is no longer accurate.
Between February and April 2025, Microsoft made several updates to native SMS in Teams:
Canada is now supported. Native SMS in Teams works for users in the United States (including Puerto Rico) and Canada when their number is a Microsoft Teams Calling Plan number. Microsoft confirmed this in the Plan for SMS in Teams with Microsoft Calling Plan numbers documentation (updated 02/25/2025).
Microsoft introduced its own Brand and Campaign registration. Admins must register a Brand and Campaign inside the Teams admin center before SMS can be activated on a phone number. This is Microsoft's version of 10DLC, and it lives under Voice → Phone numbers.
An SMS usage report was added to Teams admin center under Reports & analytics → Usage reports → PSTN and SMS Usage.
Pooled message allotments are part of the calling plan, with limits described by Microsoft as roughly 200 messages per user per month for typical plans, with overages billed through Communication Credits.
Opt-in and opt-out keywords (STOP, START) are enforced at the platform level for compliance with US and Canadian carrier rules.
The headline: Native SMS in Teams is real, but it is intentionally limited. It is built for one-to-one personal texting from a Calling Plan user, not for shared inboxes, automation, MMS, or business texting at scale.
Native Microsoft Teams SMS: Features, Limits, and How It Works
Native SMS lives inside the existing 1:1 chat experience in Teams. Once your admin enables it, you start a new chat using a phone number instead of a person's name, and the recipient gets a regular text on their phone.
What native Teams SMS includes
One-to-one SMS to mobile numbers in the US, Puerto Rico, and Canada
In-chat replies that thread under the same conversation in Teams Chat
Standard STOP / START opt-out handling at the carrier level
Admin reporting through PSTN and SMS Usage in Teams admin center
Works from Teams desktop, web, and mobile clients
Uses your Teams Calling Plan phone number, no separate app or number required
What native Teams SMS does not include (and why this matters)
No MMS: You cannot send or receive images, PDFs, contracts, signed forms, photos of damaged property, intake forms, IDs, or any rich media. This rules out most healthcare, legal, real estate, insurance, claims, and field-service workflows.
No shared inbox: Every conversation lives in one person's chat. If that person is out of office, the customer gets no reply. There is no way for a team to triage messages, assign threads, leave internal notes, or hand off conversations.
No automation: No templates, no scheduled messages, no auto-replies, no triggered texts from a CRM or a calendar, no bulk messaging.
No existing-number support: Native SMS only works on numbers issued through Microsoft Calling Plans. You cannot text-enable your existing landline, toll-free, or third-party VoIP number.
Tight per-user quotas: The 200-messages-per-user-per-month pool covers light personal use, not customer-facing workflows.
Limited compliance posture: There is no HIPAA Business Associate Agreement attached to native Teams SMS, no SEC-grade archival workflow, and no built-in audit trail beyond Microsoft's general PSTN usage report.
Requires Teams Phone + Microsoft Calling Plan licensing: Each user needs a Teams Phone license and a Microsoft Calling Plan, which is an additional cost on top of Microsoft 365.
For a one-person business sending the occasional appointment reminder, native SMS may be enough. For a sales, support, clinical, or operations team that actually runs on text, you will outgrow it within days.
Receiving Texts in Microsoft Teams
Replies to native Teams SMS land automatically in the same 1:1 chat the message was sent from, no separate app or notification setup needed. The catch: that chat lives with one person. If a customer texts back and that person is in a meeting, out sick, or has left the company, nobody else on the team sees the reply. With Falkon SMS, incoming texts land in a shared inbox visible to the whole team, with assignment, tagging, and internal notes, so a reply never sits unseen in someone's personal chat.
How to Enable Native SMS in Microsoft Teams (Step-by-Step Admin Guide)
This is the path Microsoft documents in its Enable and manage SMS in Microsoft Teams article (last updated 04/25/2025). You need a Teams Administrator, Teams Communications Administrator, or Teams Telephony Administrator role.
Step 1: Confirm prerequisites
For each user who will send SMS, assign:
Microsoft Teams license
Teams Phone license
Microsoft Teams Calling Plan
The user's phone number must be a Microsoft Calling Plan number in the US, Puerto Rico, or Canada. Direct Routing and many Operator Connect numbers do not work with native SMS, those use the carrier's own SMS path.
Step 2: Set up a billing mechanism for SMS overages
Enable Pay-as-you-go for Calling Plans and prepay Communication Credits (or set monthly billing). Overages, including SMS beyond the pooled allotment, are billed against this.
Step 3: Create a Brand
In Teams admin center, go to Voice → Phone numbers → SMS, then complete Step 1: Create brand. You submit your legal business details (company name, EIN, address, contact) for verification with The Campaign Registry (TCR).
Step 4: Create a Campaign
After the Brand is approved, complete Step 2: Create campaign. You describe what kind of messages your business will send, appointment reminders, account notifications, marketing, so carriers can vet the use case. Without a Campaign, traffic will be filtered.
Step 5: Activate SMS on a phone number
In Teams admin center, go to Voice → Phone numbers → Numbers. Find the user's number. The SMS status column will show one of:
Not available: the phone number cannot support SMS in Teams.
Not Activated: the number is eligible. Select Enable SMS.
In Progress: activation can take up to two hours.
Activated: ready to send and receive SMS via Teams.
Step 6: Test from the user's Teams Chat
The user opens Teams, starts a new chat, types a mobile number into the To field, and sends a message. Replies thread back into the same Teams Chat.
Step 7: Pull the SMS usage report
In Teams admin center, go to Reports & analytics → Usage reports → PSTN and SMS Usage. Pick a date range and run the report. Use this to track per-user consumption against your pooled allotment.
If your goal is full business texting, shared inboxes, MMS, your existing number, automation, compliance, skip ahead. Native SMS will not get you there.
The Limits That Push Most Businesses to a Third-Party SMS App
Microsoft is explicit that native SMS in Teams is built for personal, one-to-one texting. In real businesses, communication is shared, archived, automated, and often regulated. The gaps that drive teams to a third-party SMS app for Microsoft Teams are consistent:
The number problem: Customers already know your main line. Asking them to text a brand-new Microsoft-issued number creates friction and erodes trust. Most businesses want to text from the same number that rings.
The team problem: When a single user owns the inbox, conversations stall the moment they take a day off. Shared inboxes, with assignments, tagging, notes, and visibility into who said what, are the norm for any business with more than one person.
The MMS problem: Sending a quote, a photo of a part, a receipt, a vCard, or a signed form is not a luxury. It is the conversation. Native SMS blocks all of it.
The compliance problem: Healthcare, legal, financial services, and any regulated industry need HIPAA, SOC 2, SEC, or FINRA-aligned controls. Microsoft does not extend a HIPAA BAA to native Teams SMS messages exchanged with patients.
The automation problem: Customers expect instant confirmation, after-hours auto-replies, and reminders that fire on schedule. Native SMS has no scheduling, templates, or triggered messages.
The integration problem: Texts that don't reach the CRM are lost institutional knowledge. Teams that live in HubSpot, Clio, Salesforce, or Microsoft Dynamics need every message to flow into the customer record automatically.
Calling Plans vs Operator Connect vs Direct Routing: What Each Means for SMS
This trips up almost every Teams admin, and it directly affects which SMS path you can use. Here is the practical view in 2026:
Microsoft Calling Plan: Microsoft is your carrier. You buy minutes and numbers from Microsoft. This is the only path that unlocks native Microsoft Teams SMS. SMS is limited to US, Puerto Rico, and Canada, plain text only, and gated by Brand and Campaign registration.
Operator Connect: A certified third-party carrier (Verizon, BT, Pure IP, etc.) provides PSTN connectivity directly inside Teams admin. SMS depends on the carrier's own SMS service, not Microsoft's. Some Operator Connect carriers offer SMS and MMS, but it is not the same as native Teams SMS.
Teams Phone Direct Routing: You bring your own SBC and carrier into Teams. Native Microsoft SMS is not available on Direct Routing numbers. You add SMS by routing the number to an SMS-enabled service. Falkon VoIP Direct Routing is built for this: it ports a Microsoft-issued (or any) Teams number and text-enables it through Falkon SMS, so the same number rings in Teams and texts through the Falkon SMS Teams app.
If you already use Microsoft Calling Plans and only need light, one-to-one SMS, native may be sufficient. If you use Operator Connect, Direct Routing, or want to keep an existing business number, a third-party Teams SMS integration is the path.
How to Add SMS to Microsoft Teams With Falkon SMS
Falkon SMS is a Microsoft Teams SMS integration available on Microsoft AppSource. It text-enables your existing business number, landline, toll-free, VoIP, or Microsoft Teams Calling Plan number, and surfaces a full business texting interface inside Microsoft Teams. There is no porting of voice service required for landline and most VoIP numbers; voice stays with your current provider.
Path A: Text-enable your existing landline, toll-free, or VoIP number
This is the fastest path. Most numbers are texting on the same day or next business day.
Book a Falkon SMS setup call. Onboarding walks you through carrier verification and 10DLC.
Create your Falkon SMS account. Add your team and assign roles (admin, agent, viewer).
Sign a Letter of Authorization (LOA) so Falkon can text-enable the number with your current carrier. Voice is untouched.
Install Falkon SMS from Microsoft AppSource. Add it to Teams so the SMS panel lives in your Teams sidebar.
Send your first text from Teams. Replies appear in the shared inbox, with assignment, notes, tags, and full history.
Path B: Text-enable a Microsoft Teams Calling Plan number
If your number is currently a Microsoft-issued Calling Plan number and you want richer SMS than the native experience, port it to Falkon VoIP Direct Routing. Voice continues working in Teams; SMS now runs through Falkon SMS.
Submit the VoIP Onboarding or Porting Form to start the SMS activation.
Sync your numbers. Either grant Falkon a Global Admin role (existing credentials or a temporary admin user), or have your IT team run a short PowerShell sequence to authorize number sync.
Complete Falkon SMS registration to finalize activation.
Now your MS Teams number is text-enabled. Start messaging from Teams. The same number now sends and receives SMS and MMS through Falkon, alongside Teams voice.
Path C: Get a new texting number from Falkon
If you do not yet have a business number, Falkon can provision a US or Canadian local or toll-free number, register it for 10DLC, and connect it to Microsoft Teams in one workflow.
Watch this video to explore how Falkon SMS helps businesses text inside Microsoft Teams.
Native Teams SMS vs Falkon SMS: Full Feature Comparison
A practical comparison of the two main paths most businesses choose between in 2026:
Capability | Native Microsoft Teams SMS | Falkon SMS for Microsoft Teams |
Where the messages live | Personal 1:1 Teams Chat | Falkon SMS app inside Teams (shared inbox) |
Country coverage (2026) | US, Puerto Rico, Canada | US and Canada |
Number you text from | Microsoft Calling Plan number only | Your existing landline, toll-free, VoIP, or Teams number |
MMS / rich media | Not supported | Full MMS (images, PDFs, video, vCard) |
Shared team inbox | No | Yes, assignments, tags, internal notes |
Bulk / broadcast messaging | No | Yes, with personalization + scheduling |
No | Yes | |
Templates and snippets | No | Yes |
Triggered messages from CRM | No | Yes |
CRM and app integrations | None native | Clio, HubSpot, Webex, Slack, Outlook, Teams |
HIPAA compliance + BAAÂ | No BAA for Teams SMSÂ | HIPAA-compliant with signed BAAÂ |
SOC 2 Type I | Not specific to SMS | Yes |
SEC / FINRA archival workflow | Limited | Supported |
Per-user message limit | ~200/user/month pooled | Plan-based for business volume |
Required licensing | Teams + Teams Phone + Calling Plan | Teams (any license) + Falkon SMS |
10DLC handling | Admin completes in Teams admin center | Done for you by Falkon |
Audit logs/message archival | Limited PSTN report | Full conversation archive |
Secure file sharing (OTP, expiring links) | No | Yes |
Auto-replies and after-hours coverage | No | Yes |
Operator Connect / Direct Routing | Limited | Works alongside any carrier |
The simple read: native is for personal texting from a Calling Plan number. Falkon SMS is built for business texting across your team, on your existing number, with the compliance posture regulated industries need.
10DLC Registration for Microsoft Teams SMS (Done For You)
10DLC, or ten-digit long code, is the US and Canadian carrier framework that verifies business senders, scores their trust, and decides whether their messages get delivered or filtered as spam. It applies to any business texting from a standard ten-digit number, including Microsoft Teams.
The registration includes:
Brand registration, your legal business identity, submitted to The Campaign Registry.
Campaign registration, what you will text about (alerts, reminders, marketing, customer care), how recipients opt in, and how they opt out.
Traffic vetting, a trust score that influences throughput and deliverability.
If you use native Teams SMS, your admin completes this inside Teams admin center under Voice → Phone numbers → SMS. The process is real work, and errors cause messages to silently fail.
If you use Falkon SMS, the Falkon onboarding team submits and manages your 10DLC registration on your behalf. Most businesses are registered and sending within a few business days. Failed registrations are corrected and resubmitted without extra paperwork from you.
If your current 10DLC registration was blocked or your messages are being filtered, Falkon has a 10DLC recovery workflow. Register your number for 10DLC now.
Blocked by 10DLC? We'll fix it.
Get registered today and keep your business texting without interruption.
MMS, Rich Media, and Secure File Sharing in Teams
For any team that needs to send more than plain text (and that is most teams), MMS support is the dividing line.
With Falkon SMS for Microsoft Teams, you can send and receive inside Teams:
Product photos, damage photos, and signed contracts
PDFs of invoices, statements, claims, and intake forms
Short videos and GIFs
vCards for instant contact saves
Appointment cards, receipts, and maps
For regulated workflows, Falkon SMS also supports secure file sharing via text. Sensitive documents are sent as expiring, password-protected links with optional one-time-password (OTP) verification and biometric access for recipients. The content lives in encrypted storage; the text itself never carries the file. Access events are logged for compliance.
Native Microsoft Teams SMS does not support MMS or any of these secure file workflows.
Industry Use Cases for SMS in Microsoft Teams
The reasons businesses add SMS to Teams differ by industry. The pattern that holds across all of them: customers already prefer text, and the team already lives in Teams.
Healthcare and home care: Appointment confirmations, no-show reminders, refill notifications, intake forms, post-visit follow-up, care coordination between providers, and billing reminders, all from a HIPAA-compliant shared inbox in Teams. Falkon SMS is a HIPAA-compliant texting solution with a signed BAA; native Teams SMS is not.
Legal practices and law firms: Client case updates, court date reminders, document requests, billing notifications, intake for new matters, and time-sensitive deadlines. Falkon SMS integrates with Clio so every text auto-syncs to the matter file. Privileged communications are preserved with retention and audit.
Real estate, title, and escrow: Showing confirmations, document signatures, status updates, lender coordination, and closing reminders, all on the same business number agents already give out, and all visible to the team if an agent is unavailable.
Insurance and claims: First notice of loss, photo intake (MMS), adjuster scheduling, and status notifications. MMS support is essential and is the single biggest reason claims teams drop native Teams SMS.
Pharmacies and clinics: Prescription ready, refill reminders, and outreach campaigns sent in compliance with HIPAA and state regulations, with consent and opt-out tracked automatically.
Finance and accounting: Statement notifications, payment reminders, document requests, secure file sharing for tax records, and SEC-aligned message archival. Falkon SMS supports SEC and FINRA-aligned workflows.
Recruiting and HR: Interview scheduling, offer follow-up, document collection, and onboarding nudges, all from a number the candidate already has saved as your business.
Restaurants, gyms, salons, churches, schools, nonprofits: Reservation, class, and event reminders. Bulk announcements to opted-in lists. Two-way conversation with a shared inbox so any team member can answer.
Falkon SMS publishes industry-specific texting workflows for each of these. See all industries that Falkon SMS supports.
Pricing: What Teams SMS Actually Costs in 2026
For native Microsoft Teams SMS, the cost is layered:
A Microsoft Teams Phone license per user
A Microsoft Teams Calling Plan per user
Pay-as-you-go Communication Credits for SMS overages beyond the pooled allotment
The combined per-user cost typically lands in the $15 to $40 per month range before factoring in SMS overages, depending on the calling plan and region.
For Falkon SMS, pricing is a single per-user business texting plan that includes SMS, MMS, shared inbox, integrations, compliance features, and 10DLC handling. There is no requirement to also buy a Microsoft Calling Plan. Current plans, volume tiers, and add-ons are listed at Falkon SMS pricing page.
The right way to compare cost: add up Microsoft Calling Plan + Teams Phone + expected overages for native, and compare that to the Falkon plan that matches your message volume. For most businesses, Falkon costs less per user even before counting the features that native does not include at any price.
Troubleshooting: Teams SMS Not Working
The most common reasons Teams SMS fails to send or receive in 2026:
Brand or Campaign was never registered, or was rejected: Native Teams SMS will silently fail until both are approved. Check status in Teams admin center under Voice → Phone numbers → SMS.
The phone number is not a Microsoft Calling Plan number: Native SMS only works on Microsoft-issued Calling Plan numbers. Operator Connect and Direct Routing numbers do not show "Activated" in the SMS status column.
The user is missing a Teams Phone license or Calling Plan: Both are required for SMS.
You hit your pooled monthly limit: Pull the PSTN and SMS Usage report for the user.
The recipient sent STOP: Native SMS enforces opt-out at the platform level. The user will not see new messages reach that recipient until the recipient texts START.
You are outside the supported geography: Native Teams SMS supports US (including Puerto Rico) and Canada only.
Carrier filtering is dropping the message: Often caused by content that looks like spam, missing opt-in evidence, or a poor 10DLC trust score.
If you have switched to Falkon SMS and a message is not delivering, the Falkon support team can pull message-level delivery reports from the carrier with a single ticket and re-route or re-register if needed.
Frequently Asked Questions About Microsoft Teams SMS
Can Microsoft Teams send text messages?
Yes. Since 2025, Microsoft Teams supports native one-to-one SMS for users on a Microsoft Calling Plan number in the US, Puerto Rico, and Canada, once Brand and Campaign registration is complete. Falkon SMS adds business texting with shared inboxes, MMS, automation, on top of this without requiring a Calling Plan.
Can Microsoft Teams receive text messages?
Yes. Replies to native Teams SMS thread back into the sender's personal Teams Chat automatically. There's no shared visibility, though, if a customer texts back and the recipient is out, no one else on the team sees it. Falkon SMS routes replies into a shared inbox so any team member can respond.
Can you text through Teams without a Calling Plan?
Not with native SMS, which requires a Microsoft Calling Plan number. Falkon SMS lets you text through Microsoft Teams using your existing landline, toll-free, or VoIP number, no Calling Plan required.
Can you text from Microsoft Teams on your existing business number?
Not with native SMS, it only works on Microsoft-issued Calling Plan numbers. Falkon SMS text-enables your existing business number so customers keep texting the number they already know, right from Teams.
Does native Microsoft Teams SMS support MMS?
No. Native Teams SMS is plain text only, no images, PDFs, videos, GIFs, or emojis. Falkon SMS supports full MMS inside Teams.
Can multiple team members respond to the same text conversation in Microsoft Teams?
With native Teams SMS, no, every conversation lives in a single user's personal chat. With Falkon SMS, yes. The shared inbox lets multiple team members see, assign, tag, and respond to the same conversation with full visibility.
Is texting from Microsoft Teams HIPAA compliant?
Native Teams SMS is not covered under Microsoft's HIPAA BAA for messages exchanged with patients and should not be used for protected health information. Falkon SMS for Microsoft Teams is HIPAA-compliant with a signed BAA and provides the access controls, audit trail, and retention that HIPAA requires.
Can I text-enable my existing landline, toll-free, or VoIP number?
Not with native Teams SMS, which requires a Microsoft-issued Calling Plan number. Falkon SMS can text-enable virtually any existing US or Canadian business number, landline, toll-free, or VoIP, usually without changing your phone provider.
How long does 10DLC registration take?
Microsoft's native Brand and Campaign approval through Teams admin center typically takes a few business days to a couple of weeks, depending on TCR vetting load and the accuracy of the submission. Falkon SMS handles 10DLC for you and most customers are approved within a few business days; failed submissions are corrected and resubmitted at no additional cost.
Does Microsoft Teams SMS work on iPhone and Android?
Yes. Native Teams SMS works in the Microsoft Teams mobile apps on iOS and Android for users on a Calling Plan. Falkon SMS also works in the Microsoft Teams mobile app and as a standalone iOS, Android, macOS, Windows, web, and Chrome extension experience.
How much does it cost to add SMS to Microsoft Teams?
Native Teams SMS requires a Teams Phone license and a Microsoft Calling Plan per user (typically $15 to $40+ per user per month combined) plus SMS overage charges via Communication Credits. Falkon SMS is sold as a dedicated business texting plan and does not require a Microsoft Calling Plan.
What is the difference between native Teams SMS, Operator Connect SMS, and a Teams SMS app?
Native Teams SMS is Microsoft's plain-text 1:1 SMS for Calling Plan numbers. Operator Connect SMS depends on what your carrier offers, some support SMS and MMS, others do not. A Teams SMS app like Falkon SMS is independent of how your voice is delivered and gives you business texting features (shared inbox, MMS, automation, integrations, compliance) on top of any setup.
Can I migrate from native Teams SMS to Falkon SMS later?
Yes. Most businesses start with whatever they have and move to Falkon when they hit the limits, usually the shared inbox or MMS gap. Falkon handles porting (when needed), 10DLC, and message history setup.
Ready to Add SMS to Microsoft Teams?
Microsoft made native Teams SMS real in 2025. For light, one-to-one personal texting on a Microsoft Calling Plan, it works. For a business that needs a shared inbox, MMS, automation, compliance, integrations, and the ability to text from a number customers already know, that is where Falkon SMS for Microsoft Teams fits.
Falkon SMS is SOC 2 Type I certified, HIPAA-compliant, supports US and Canada, integrates with Microsoft Teams, Outlook, Webex, HubSpot, Clio, and Slack, and handles 10DLC end to end. It is available in the Microsoft AppSource and the Microsoft Teams app store.
Upgrade your Microsoft Teams texting with Falkon SMS
Stay connected with your team and customers efficiently and enhance your overall business operations with ease.