ACS Advanced Messaging for WhatsApp retirement - What is the recommended migration path?

Info Omniwish 35 Reputation points
2026-09-24T11:35:43.91+00:00

Hello ACS Community,

We are currently using Azure Communication Services Advanced Messaging for WhatsApp in our application for sending and receiving WhatsApp messages.

We recently received a Microsoft notification stating that standalone Azure Communication Services Advanced Messaging for WhatsApp will be retired on September 30, 2028.

Our current architecture is:

  • Backend: Node.js / Express
  • Frontend: React
  • Database: MongoDB
  • Messaging service: Azure Communication Services Advanced Messaging
  • Channel: WhatsApp
  • We use ACS for sending/receiving WhatsApp messages and handling message events/webhooks.

We would like to understand the recommended migration path.

Could someone from the ACS team please clarify:

  1. What is the Microsoft-recommended replacement for ACS Advanced Messaging for WhatsApp?
  2. Should existing customers migrate directly to the Meta WhatsApp Business Platform / Cloud API, or is Microsoft recommending another service/partner?
  3. Will existing ACS WhatsApp phone numbers, WhatsApp Business Accounts, templates, and message history be transferable to the new solution?
  4. Is there an official migration guide or migration tool available?
  5. Can we continue using our existing ACS Advanced Messaging resource until September 30, 2028, or are there earlier deadlines we need to be aware of?
  6. Are there any changes we need to make now regarding WhatsApp Business-Scoped User IDs (BSUIDs)?
  7. What is the recommended approach for migrating our existing webhooks/Event Grid integration?
  8. Are there any limitations or differences in supported WhatsApp features between ACS Advanced Messaging and the recommended replacement?
  9. Is Microsoft planning to provide a native replacement for standalone ACS Advanced Messaging before the retirement date?

We want to start planning the migration early and would appreciate guidance on the officially supported migration path.

Azure Communication Services
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Divyesh Govaerdhanan 11,890 Reputation points MVP Volunteer Moderator
    2026-09-24T19:38:47.5833333+00:00

    Hello Info Omniwish,

    Welcome to Microsoft Q&A,

    Yes, the retirement is real, and your existing setup keeps working until then. Microsoft has published guidance, and here is what it says for your questions, in order:

    1. Replacement (Q1, Q2, Q9): The ACS retirement guide says ACS WhatsApp retires on September 30, 2028, and lists these options: Dynamics 365, partner solutions from Microsoft Marketplace such as Infobip and Telesign, or moving your WhatsApp Business Account to another Business Solution Provider (BSP). For Dynamics 365 Contact Center users, the migration article recommends Meta Direct or WhatsApp through Twilio. I couldn't find any announced native Microsoft replacement for the standalone service.
    2. Deadlines (Q5): Existing integrations continue to function. No new features will be added, but existing capabilities stay supported during the transition. Complete the migration before September 30, 2028.
    3. Numbers and accounts (Q3): You can use WhatsApp's phone number migration process to move a number from an ACS WhatsApp channel to another BSP, if the destination BSP supports it. The docs don't cover moving templates or message history, so export or archive your own history now and confirm template handling with your chosen provider.
    4. BSUIDs (Q6): The guide says your app owns the customer mapping and must handle WhatsApp usernames and Business-Scoped User IDs. If you key users by phone number today, plan to store the BSUID alongside it.
    5. Events and webhooks (Q7, Q8): ACS uses Event Grid for inbound messages and delivery status. A replacement provider will use its own webhooks or event streams, so expect to rework that layer. The guide says events, media and interactive support vary by provider, so check each candidate before you choose.
    6. Migration guide or tool (Q4): Microsoft says it will provide migration guidance and support during the transition. Details are in the retirement guide. I couldn't find a dedicated migration tool for custom apps.

    Since you run a custom Node.js app, the practical path is a BSP or Marketplace partner with a REST API and webhooks. Start with a small pilot, then move the number.

    Please click Accept Answer and upvote if this helped.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.