Attention, Dynamics 365 users: your WhatsApp countdown has begun.
Microsoft has announced that Azure Communication Services (ACS) Advanced Messaging with WhatsApp retires on September 30, 2028. If your customer conversations on WhatsApp flow through ACS, you have about 24 months to move your number and templates and rewire your automations. That’s a comfortable window for a planned migration and a painful one for a rushed one.
Key Takeaways
- ACS is retiring as a standalone offering on September 30, 2028. WhatsApp (Advanced Messaging) is on the retired list, not the “breaking change” list.
- From October 23, 2026, new customers can’t sign up for retiring ACS services.
- Existing ACS WhatsApp integrations keep working until retirement, with no new features and support limited to fixes.
- Teams integration doesn’t extend retiring services. Microsoft states that it doesn’t extend the availability of services identified as retiring.
- Dynamics 365 teams can move to WhatsApp4Dynamics by Inogic, which connects WhatsApp to Dynamics 365 CRM through Meta WhatsApp Business and Twilio Platform.
What Microsoft Announced
Microsoft sorts ACS products into two buckets:
- Retired: unavailable after September 30, 2028. This includes Email, SMS, Chat, Rooms, Direct Routing, Job Router, the UI Libraries and Advanced Messaging with WhatsApp.
- Breaking change: still available, but supported only alongside Teams-aligned services. This covers the Calling SDK, Call Automation, Recording, Audio Streaming and Closed Captions.
After the retirement date, API and SDK operations that depend on retired services may return errors.
Who is affected
Check three places:
- Custom apps built on the ACS Messaging SDK and Event Grid for WhatsApp.
- Dynamics 365 channels configured through ACS – Microsoft describes the Dynamics WhatsApp channel as configured through ACS, and Dynamics workloads follow its separate Dynamics 365 ACS retirement guide.
- Anything downstream of your Event Grid subscriptions, such as Logic Apps, Functions and reporting.
To find affected resources, Microsoft points to the Azure Advisor Service Retirement workbook and the open-source ACS Resource Explorer.
Why not wait until 2028
Beyond the feature freeze and the sign-up cutoff, two things make early planning cheaper:
- Identity changes. Microsoft’s comparison flags WhatsApp usernames and Business-Scoped User IDs (BSUIDs) as something your app or Dynamics contact records must handle. If your logic treats the phone number as the customer key, audit it now.
- Number and template lead time. Moving a number uses WhatsApp’s phone number migration process, and the destination provider must support it. Templates are defined per WhatsApp Business Account (WABA), so inventory them before cutover.
Microsoft’s own guidance points Dynamics 365 customers to Dynamics 365 Contact Center and lists partner providers. If your goal is WhatsApp inside Dynamics 365 CRM, connected straight to Meta, the rest of this guide is for you.
Why a direct Meta API architecture is worth considering?
ACS adds a layer between WhatsApp and your CRM:
- Today: Customer → WhatsApp → Meta → ACS (Messaging SDK / Event Grid) → your app or Dynamics channel
- Direct: Customer → WhatsApp → Meta Cloud API → WhatsApp4Dynamics → Dynamics 365
Removing that layer has practical effects:
- Fewer moving parts – There’s no Event Grid plumbing to maintain and no ACS retirement dependency.
- Simpler billing – Microsoft describes ACS WhatsApp as an ACS usage fee plus Meta fees, billed through Azure. A direct setup pays Meta’s rates directly, plus the app license.
- Predictable pricing rules – Meta has charged per message since July 1, 2025, and it may update prices only on the first day of each quarter, so budget reviews map to four dates a year.
- Reach – WhatsApp crossed 3 billion monthly active users in 2025, so your customers are already there.
The trade-off is that you own your Meta Business Manager setup, WABA and API credentials.
Related reading: Meta API vs Twilio API: Which WhatsApp Integration Fits Your Dynamics 365 Strategy?
What WhatsApp4Dynamics gives your Team
WhatsApp4Dynamics is a part of Inogic Omnichannel suite integrating WhatsApp, Text SMS and Live Chat with Dynamics 365 CRM (Online | Dataverse). It connects WhatsApp Business through the Meta API or Twilio and puts the conversation where your customer data already lives.
Setup in practice: register your number and get API credentials from Meta, install the app, open WhatsApp4Dynamics > Configurations, and enter your Meta API details.
Conversations that carry CRM Context
- Chat from any record: An agent opens a Case, Opportunity, Lead or Contact and starts a WhatsApp chat without typing a number. Example: a service rep sees a delayed-shipment Case and messages the customer from the same screen.
- Records from chats: Create Leads, Contacts, Cases and custom-entity records from a conversation. Dynamic Field Mapping auto-fills CRM records with real-time chat data, so nobody copies details by hand.
- Chat history that stays: Conversations are stored as timestamped chat sessions linked to CRM records, so a new owner inherits the full context.
- Assignment and internal chat: Route chats to the right person, and consult a colleague behind the scenes without involving the customer.
Templates and automation
- Templates with variables: Send text, media, buttons and quick replies, with static and dynamic variables. Example: “Hi {first name}, your appointment is confirmed for {date}.”
- Event-driven messages: Trigger WhatsApp messages from workflows and Power Automate when CRM data changes, such as order confirmations, appointment reminders and service updates.
- Pre- and post-chat questionnaires: Capture an intake answer before a chat or feedback after it, and write the response back to the record.
- Rich media and languages: Share images, videos, PDFs and Word documents, and message in the customer’s language.
Related reading: Boost Customer Interaction Using WhatsApp in CRM: A Complete Integration Guide
AI assistance
InoWiz AI adds smart reply suggestions, chat summaries and sentiment analysis, so an agent picking up a long thread doesn’t have to scroll through it. AI-powered chatbot option that answers from Dataverse, SharePoint, websites and uploaded documents.
Related reading: How to Integrate WhatsApp with Dynamics 365 for Marketing Campaigns: A Complete Guide
Where it Works: Industry Examples
| Industry | Example flow |
| Healthcare | Appointment is booked → reminder template goes out → patient replies to reschedule → record updates; a post-visit questionnaire collects feedback |
| Banking and finance | Transaction or status alert sent from a CRM trigger; customer sends a document as a PDF or image and the agent attaches it to the case |
| Retail | Order confirmation and delivery updates by template; a return query turns into a Case from the chat |
| Education | An enquiry from a prospective student becomes a Lead; counselors follow up and share brochures and documents in the chat |
| Travel | Booking confirmation and itinerary PDF sent automatically; on-trip support handled from the customer’s record |
Related reading: 7 Industry Use Cases for AI-Powered WhatsApp and Dynamics 365 CRM Messaging
| Don’t wait for 2028 to plan migration from Azure Communication Services
Microsoft’s retirement date is fixed, but your migration pace isn’t. Start now with a 15-day trial of WhatsApp4Dynamics and see your WhatsApp conversations, templates and automation working inside Dynamics 365.
|
FAQs
Is Azure Communication Services being retired?
Yes. Microsoft is retiring ACS as a standalone offering on September 30, 2028, while Teams-aligned scenarios such as Teams Phone Extensibility remain supported.
When does ACS WhatsApp (Advanced Messaging) retire?
ACS Advanced Messaging with WhatsApp retires on September 30, 2028. Existing integrations keep working until then, with no new features.
Can new customers still use ACS WhatsApp?
No. From October 23, 2026, new customers can’t sign up for retiring ACS services.
How do I integrate WhatsApp with Dynamics 365 without ACS?
Use WhatsApp4Dynamics, which connects the Meta WhatsApp Business Platform API to Dynamics 365. Enter your Meta API details under Configurations, then chat from CRM records.
Do I need a BSP to use the WhatsApp Business Platform?
Not necessarily. Meta’s Cloud API can be accessed directly with Meta Business Manager credentials, which is how WhatsApp4Dynamics is set up.
Can WhatsApp conversations create Leads and Cases in Dynamics 365?
Yes. WhatsApp4Dynamics creates Leads, Contacts, Cases and custom-entity records directly from chats.