Teams WhatsApp Integration: How to Connect WhatsApp to Microsoft Teams
Microsoft publishes no WhatsApp app for Teams, but it does publish a WhatsApp product: Azure Communication Services. That gap explains why four different routes exist, why they cost different amounts, and why one of them is unavailable to US government tenants.
WaBulkSend runs on Meta's official WhatsApp Cloud API. Not affiliated with Microsoft Corporation or Meta Platforms, Inc.
Which Teams route fits your tenant?
No sign inPower Platform WhatsApp connector:
Microsoft's connector reference lists the tyntec WhatsApp Business connector as excluded from US Government (GCC), US Government (GCC High), and US Department of Defense (DoD) regions, and from Azure Government regions in Logic Apps. A government tenant has to reach WhatsApp another way, usually a custom app calling Meta's Cloud API from a service you host yourself.
On a commercial tenant you can use the tyntec WhatsApp Business connector in Power Automate, Power Apps, and Copilot Studio, where Microsoft classes it as Premium, or in Azure Logic Apps, where it is Standard. Microsoft caps it at 100 API calls per connection per 60 seconds.
Meta bills you per delivered template on your own WhatsApp Business account whichever route you pick. Teams licensing adds no WhatsApp charges of its own.
Short answer: Microsoft ships no native WhatsApp app for Teams and Meta publishes none either, so every working setup puts a third party in between. Four routes work in practice. Azure Communication Services is Microsoft's own WhatsApp product and the closest thing to an official answer, though it is a developer SDK rather than something you install into a channel. The Power Platform route uses the tyntec WhatsApp Business connector, the only WhatsApp connector in Microsoft's own connector catalog, which Microsoft excludes from GCC, GCC High, and DoD regions. A bridge app such as Social Intents installs into the workspace and mirrors conversations into a channel for two-way replies. A governance overlay such as LeapXpert exists for a different problem entirely: capturing employee WhatsApp chats for recordkeeping. Whichever you pick, Teams never becomes the sender. It is a viewing and reply surface on a WhatsApp Business account you still own and pay Meta for.
Last updated August 2026. Microsoft, Microsoft Teams, Power Automate, and Azure are trademarks of Microsoft Corporation. WhatsApp is a trademark of Meta Platforms, Inc. WaBulkSend is not affiliated with either.
Does Microsoft Teams have a WhatsApp integration?
Not a native one. There is no WhatsApp app from Meta in the Teams app store, and Microsoft does not publish a WhatsApp channel inside Teams the way it publishes one for email or for Teams Phone calling. What Microsoft does publish is a WhatsApp product one layer down, in Azure, which is the piece most comparison articles miss entirely.
That distinction changes the shopping list. If you want WhatsApp conversations visible inside a Teams channel, you are buying a bridge. If you want WhatsApp messages sent by a workflow your organization already runs in Power Automate, you are buying a connector. If you are a developer, Microsoft will sell you the channel directly. Here are the four routes side by side.
| Route | What it actually is | Two-way replies | Best for |
|---|---|---|---|
| Azure Communication Services Microsoft's own WhatsApp product |
A messaging SDK. Microsoft's docs say you can "create new or connect existing WhatsApp Business Accounts to Azure Communication Services" and support "business-initiated and customer-initiated conversations". | Yes, through code. Inbound messages arrive as Azure Event Grid notifications rather than as Teams messages. | Engineering teams already standardized on Azure. |
| Power Platform connector Power Automate, Logic Apps |
The tyntec WhatsApp Business connector, published by tyntec GmbH and listed in Microsoft's connector reference. Microsoft describes it as "enabling a one-way WhatsApp channel", although the connector also exposes an incoming message trigger. | Limited. You can build a flow both ways, but there is no thread state, so a Teams reply needs an adaptive card or form step you design yourself. | Alerts and notifications inside an existing Power Platform estate. |
| Bridge app installs into the workspace |
A vendor runs a shared inbox on your WhatsApp Business account and mirrors it into a Teams channel. Social Intents documents that its integration "uses Meta's official WhatsApp Business API" and requires a Meta WhatsApp Business Account with a verified phone number. | Yes, and this is the point of it. Each conversation becomes a threaded chat in the connected channel and agents answer in the thread. | Support and sales teams that live in Teams all day. |
| Governance overlay compliance recordkeeping |
A different product for a different problem. LeapXpert describes Leap Work as a solution that "enables consumer messaging on WhatsApp from within Microsoft Teams", and states that "all external chat conversations are captured and stored securely for compliance or proof of business interaction". | Yes, one to one and group, with data leakage prevention, information barriers, and ethical walls layered on. | Regulated firms whose staff already message clients on WhatsApp. |
Vendor descriptions are quoted from each vendor's own public documentation and are examples of a pattern rather than endorsements. If you are choosing a workflow tool rather than a Microsoft one, the n8n WhatsApp integration, the Make WhatsApp integration, and the Zapier WhatsApp integration all behave differently on triggers and cost. The Slack WhatsApp integration faces the same structural gap.
Microsoft does sell WhatsApp, just not inside Teams
Azure Communication Services has a feature called Advanced Messaging, and WhatsApp is one of its channels. Microsoft's documentation is direct about what it does: it "enables you to send and receive WhatsApp messages using the Azure Communication Services Messaging SDK", for "product inquiry and customer service scenarios", and for notifications such as "appointment reminders, shipping updates, two-factor authentication".
The published feature list is short and worth reading literally, because it tells you exactly where the Teams gap sits.
You bring your own WhatsApp Business Account
Microsoft lists the ability to "create new or connect existing WhatsApp Business Accounts to Azure Communication Services". Azure is acting as the sending layer on an account that stays yours, the same arrangement most solution providers use.
Templates still gate outbound messages
The docs list "initiate conversations with WhatsApp users using templates" as its own feature. Azure does not remove Meta's template approval step, and it does not remove the customer service window that governs free-form replies.
Replies arrive in Event Grid, not in Teams
Microsoft describes replying to inquiries and triggering automation "using Azure Event Grid notifications". Getting those into a Teams channel is work you do yourself, which is precisely why the bridge app market exists.
Delivery reporting is included
The feature list covers delivery reports "for messages sent, delivered, and read", which is the same webhook data Meta's Cloud API exposes. You are not losing visibility by going through Azure.
A breaking change Microsoft flags in its own docs
WhatsApp usernames let a person show a handle instead of a phone number, and Meta introduced a business-scoped user ID to go with them. Microsoft's Advanced Messaging documentation carries an explicit warning: the from and to fields in Advanced Messaging events "may now be empty when a user hides their phone number", and handlers should use the new fromBSUID and toBSUID fields instead.
Anything you wired up before 2026 that keys a Teams thread on a phone number will drop messages silently rather than error. That is a small code change and an easy one to miss. The full picture of what changes and what does not is on our WhatsApp usernames and BSUID page.
Is there a WhatsApp connector for Microsoft Teams?
There is one WhatsApp connector in Microsoft's connector catalog, and Microsoft did not build it. The tyntec WhatsApp Business connector is published by tyntec GmbH, and Microsoft's own reference page describes it as enriching Power Apps, Power Automate, and Azure Logic Apps "by enabling a one-way WhatsApp channel". That description undersells it slightly, since the connector also ships an incoming message trigger, but the framing is a fair warning: this is a notification pipe, not a conversation surface.
The details below come straight from Microsoft's connector reference, and the region exclusions in particular catch US public sector buyers by surprise.
| Detail | What Microsoft publishes |
|---|---|
| Licensing class | Premium in Power Automate, Power Apps, and Copilot Studio. Standard in Azure Logic Apps. |
| Region exclusions | Excluded from US Government (GCC), US Government (GCC High), US Department of Defense (DoD), and China Cloud operated by 21Vianet. In Logic Apps it is excluded from Azure Government regions, Azure China regions, and DoD. |
| Throttling | 100 API calls per connection per 60 seconds. That is a hard ceiling on how fast a flow can fan out. |
| Free-form actions | Text, image, video, audio, document, location, sticker, contact, list, and quick reply. Every one is marked "Usable only in support window (24 hours after last message from customer)". |
| Template actions | Text, image, video, document, location, quick reply, and dynamic URL button. Marked "Usable anytime. Requires registered template." |
| Prerequisites | A Power Apps or Power Automate plan with the custom connector feature, a tyntec API key, a WhatsApp Business Account provided by tyntec, and a message template approved by WhatsApp. |
| Connection sharing | Not shareable. If the Power App is shared with another user, that user is prompted to create a new connection. |
Details read from Microsoft's connector reference page for tyntec WhatsApp Business on 2026-08-31. Microsoft updates connector pages without notice, so verify the region list before you commit a public sector project to it.
The prerequisite most teams read past
The connector requires a WhatsApp Business Account provided by tyntec. If you already run a number through a different solution provider, you are not plugging that number into Power Automate without moving it. Number migration between providers is possible and carries your display name, quality rating, messaging tier, and approved green-quality templates across, but it needs two-factor authentication disabled on the source account and a payment method already set on the destination.
That is a real project, not a checkbox. If Power Automate is the only reason you are considering the move, price the alternative first: a small service that calls Meta's Cloud API directly and posts into Teams with an incoming webhook does the same job and keeps your existing provider. Our WhatsApp Cloud API page covers what that build involves.
How do I connect WhatsApp to Microsoft Teams?
The bridge app route is the one most support teams end up on, because it is the only one that puts a customer conversation in front of an agent without anyone writing code. The steps below follow the pattern Social Intents documents, and they generalize to most vendors in this category.
Get a WhatsApp Business Account with a verified number
Social Intents lists "a Meta WhatsApp Business Account with a verified phone number" as a prerequisite, and every serious vendor asks the same. The number must be one you own, must be able to receive a voice call or SMS, and must not already be registered to another WhatsApp account. Short codes are not supported.
Check who can approve apps in your tenant
The other documented prerequisite is "permission to install and authorize apps in your Microsoft Teams workspace". In most enterprises that is a Teams administrator, not the support manager buying the tool, and app consent policies may block third-party apps outright. Find that out in week one rather than after the contract.
Pick the number, then pick the team and channel
You choose the WhatsApp Business number, approve the permissions, sign in with a Microsoft 365 account, and select the team and channel that will receive conversations. Use a dedicated channel. Mixing customer messages into a general channel is how they get missed, and it makes the audit trail far harder to read later.
Answer in the thread and watch the clock
Each conversation appears as a threaded chat titled with the customer's name or phone number, and replies typed in the thread go back to the customer on WhatsApp. The catch is Meta's, not Microsoft's: free-form replies only work for 24 hours after the customer's last message. After that you need an approved template, and a reply typed at hour 30 is rejected by the API rather than queued.
Set a staffing rule before you set up the channel
A Teams channel makes WhatsApp look like internal chat, and people answer internal chat when they get to it. WhatsApp does not work that way. The 24 hour window is the only free reply path you have, and once it closes, continuing the conversation costs a delivered template every time. Decide who owns the channel during business hours, and set an away message for the hours nobody does. Teams offers no native way to enforce that, which is one of the honest limits of this route compared to a purpose-built shared inbox with assignment and SLA timers.
The compliance version of this question is a different product
A large share of Microsoft Teams and WhatsApp searches are not about customer support at all. They come from regulated firms where staff already message clients on personal WhatsApp, and the compliance team needs those conversations captured. Connecting a WhatsApp Business number to a support channel does nothing for that problem, because the messages in question never touch the business number.
That is the market LeapXpert sits in. It describes Leap Work as a solution that "enables consumer messaging on WhatsApp from within Microsoft Teams", letting "Teams users to use one-on-one WhatsApp messaging and group chats with external parties from within the Microsoft Teams platform and interface", with "all external chat conversations captured and stored securely for compliance or proof of business interaction". The surrounding controls it lists are data leakage prevention for outbound communication, antivirus and antimalware integration, information barriers, and ethical walls.
Buy a bridge app if
Customers message one published business number and you want a team to answer it from Teams. The record you need is a support history, and the WhatsApp Business Account is the system of record.
Buy a governance overlay if
Named employees have client relationships and message from their own handsets. The record you need is an archive that survives an examination, and the risk you are managing is an unmonitored channel.
Buy neither if
What you actually want is to send one message to a list of customers. Teams has no contact list, no template manager, and no delivery reporting, so a campaign run through it is a loop over a spreadsheet with no visibility.
How much does a Microsoft Teams WhatsApp integration cost?
Three separate bills, and only one of them is Microsoft's. The number that surprises people is the third, because it scales with sending rather than with seats.
| Cost layer | Who bills it | How it scales |
|---|---|---|
| Microsoft licensing | Microsoft, on your existing agreement | Per seat. Teams adds nothing for WhatsApp, but the Power Platform route needs a Premium connector entitlement, which is a licensing step of its own. |
| The middle layer | tyntec, Social Intents, LeapXpert, or Azure | Per seat or per message depending on the vendor. Azure's pricing page bills Advanced Messaging per user message and links the WhatsApp channel fee out to Meta's own pricing docs rather than restating a rate. |
| Meta's message fees | Meta, on your WhatsApp Business Account | Per delivered template, by category and destination country. Since July 1, 2025 Meta charges per message rather than per conversation, and only when a template is delivered. |
Meta's live pricing documentation still states that service conversations have been free for all businesses since November 1, 2024. Work the delivered-template numbers for your own volume on the WhatsApp pricing calculator, and see WhatsApp Business API pricing for how the categories differ.
Two throughput ceilings worth knowing before you design the flow
Meta documents default throughput of up to 80 messages per second, with a separate brake of one message every 6 seconds to the same user. On top of that, a new business portfolio starts at a messaging limit of 250 unique customers in a rolling 24 hours, rising through 2,000, 10,000, 100,000, and unlimited as quality and usage justify it.
The Power Platform connector adds its own ceiling of 100 API calls per connection per 60 seconds, which works out below 2 messages per second. That is fine for alerts and completely wrong for a campaign. See the messaging limits calculator to check where your list sits against the tiers.
Frequently asked questions
Does Microsoft Teams have a WhatsApp integration?
Not natively. Meta publishes no WhatsApp app in the Teams app store and Microsoft ships no WhatsApp channel inside Teams. Microsoft does publish a WhatsApp product one layer down, in Azure Communication Services, but that is a developer SDK rather than something you install into a channel. Every setup that puts WhatsApp inside Teams uses a third party.
Can I use WhatsApp in Microsoft Teams?
Yes, through a bridge app installed into your workspace. The vendor runs a shared inbox on your WhatsApp Business Account and mirrors each conversation into a Teams channel as a threaded chat, titled with the customer's name or phone number. Your team replies in the thread and the message goes back to the customer on WhatsApp.
Is there a WhatsApp connector for Microsoft Teams?
There is one WhatsApp connector in Microsoft's connector catalog and Microsoft did not build it. The tyntec WhatsApp Business connector, published by tyntec GmbH, works in Power Automate, Power Apps, Copilot Studio, and Azure Logic Apps. Microsoft describes it as enabling a one-way WhatsApp channel, so treat it as a notification pipe.
Can you reply to WhatsApp messages from Microsoft Teams?
Yes, with a bridge app or a custom app, and with one hard rule attached. Free-form replies work only within 24 hours of the customer's last message. Microsoft's connector reference marks every free-form action as usable only in that support window. After it closes, reaching that person requires a template Meta has already approved.
How do I connect WhatsApp to Microsoft Teams?
Four steps. Get a WhatsApp Business Account with a verified phone number you own. Confirm someone can install and authorize apps in your Teams tenant. Choose the WhatsApp number, approve permissions, sign in with Microsoft 365, and pick the team and channel. Then answer in the thread, inside the 24 hour window.
Can Microsoft Teams send bulk WhatsApp messages?
No, and the ceilings make that clear. Teams has no contact list, no template manager, no scheduling, and no delivery reporting. The Power Platform connector is throttled to 100 API calls per connection per 60 seconds, which is under 2 messages a second. Send campaigns from a platform built for it and keep Teams for the replies.
Does the WhatsApp connector work in GCC or DoD tenants?
No. Microsoft's connector reference excludes the tyntec WhatsApp Business connector from US Government (GCC), US Government (GCC High), and US Department of Defense (DoD) regions, and from Azure Government regions in Logic Apps. Government tenants need a service they host themselves calling Meta's Cloud API directly.
Do I need the WhatsApp Business API to connect Microsoft Teams?
For any route worth running, yes. The free WhatsApp Business app has no API at all, so tools that claim to work with it drive a logged-in session through WhatsApp Web, which WhatsApp's terms prohibit and which gets numbers banned. Registering on the Cloud API needs a number you own that can receive a call or SMS.
What is the difference between Microsoft Teams and WhatsApp for business?
Teams is an internal collaboration tool your employees are licensed for, with directory-based identity and admin controls. WhatsApp is an external channel where customers already are, with no seat licensing but per-message fees, template approval, and a 24 hour reply window. They solve different halves of the same conversation.
Can I connect WhatsApp to Slack instead?
The situation is structurally identical. Slack publishes no WhatsApp app and Meta publishes none for Slack, so the same patterns apply: a workflow tool, a bridge app on the official Cloud API, or a custom app against the messages webhook. The 24 hour window, template approval, and per-delivered-message billing are unchanged.
Keep Teams for conversations, send campaigns properly
Teams is a reasonable place to answer a customer and a poor place to run a send. WaBulkSend is pre-launch and building campaign sending on Meta's official Cloud API. The plan is that the outbound side will handle approved templates, scheduling, and delivery reporting, while your team keeps replying wherever it already works.
Join the waitlist