Azure Communication Services (ACS) is Retiring. What does it mean for your Dynamics 365 Contact Center?

Hello everyone and welcome to my blog. If you run a Dynamics 365 Contact Center, you have probably seen the recent buzz around Azure Communication Services (ACS) retiring, and a fair bit of panic along with it. In today’s blog, let’s cut through the noise and understand what is actually being retired, what it means for your contact center, and what you should start planning for.

A bit of background first. For the last few years, Azure Communication Services has quietly been the engine behind a lot of the real-time communication in the Microsoft stack – the voice calling, SMS and chat capabilities that many organizations plugged into their Dynamics 365 Contact Center and Omnichannel setups. So when Microsoft announces that ACS is going away, it is natural to wonder whether your contact center is about to stop working. Let’s clear that up.

So what exactly is being retired?

Here is the single most important thing to understand, and it is where most of the confusion comes from. Dynamics 365 Contact Center is NOT being retired. The product continues as it is. What Microsoft is retiring is Azure Communication Services as a standalone offering, and specifically the communication channels in your contact center that are built on top of ACS.

In other words, your contact center keeps running. But if certain channels in it depend on ACS under the hood, those specific channels will stop working once the retirement date hits. So the real question is not “is my contact center retiring”, it is “which of my channels depend on ACS, and what do I move them to”.

The timeline you need to know

There are a couple of dates worth putting on your calendar:

  • Retirement date – September 30, 2028: This is the date ACS retires as a standalone offering. The ACS-based channels described below will stop working after this date.
  • New sign-ups blocked – October 23, 2026: From this date, new customers can no longer sign up for the retiring Azure Communication Services capabilities. Existing customers continue to be supported until the retirement date.

Microsoft has published an official retirement guide with the authoritative dates and I would strongly recommend bookmarking it, because retirement timelines do occasionally get revised. I have linked it at the bottom of this post.

Which channels actually break?

As per Microsoft’s migration guidance, the retirement affects the following ACS-dependent configurations in Dynamics 365 Contact Center:

  • Voice – telephony that uses ACS Direct Offer or ACS Direct Routing.
  • SMS – SMS channels provisioned through ACS.
  • WhatsApp – WhatsApp configured through ACS.

If you are only using, say, the native Microsoft-provided voice or channels that do not sit on ACS, you have far less to worry about. The first action item for every admin is therefore to audit your channels and identify exactly what is running on ACS today.

What is the replacement path?

This is the good news. Microsoft is not leaving you stranded – there is a defined migration path for each channel.

  • Voice: Microsoft is positioning Teams Phone extensibility as the strategic voice platform for Dynamics 365 Contact Center going forward. If you are on ACS-based voice today, this is the direction to plan towards.
  • SMS: Microsoft has stated its intent to provide equivalent, native SMS capability within Dynamics 365 Contact Center before ACS reaches retirement. In the meantime, the migration guide also points to partner options for SMS.
  • WhatsApp and routing: Microsoft’s guidance directs these scenarios towards native Dynamics 365 Contact Center capabilities and approved partners. The exact partner list is maintained in the official doc, so always check there for the current options.

What should you do now?

You have time until September 2028, but if you have ever managed a channel migration you know it is never as simple as flipping a switch, especially where live customer phone numbers and messaging are involved. Here is how I would approach it:

  1. Audit. List every voice, SMS and WhatsApp channel in your contact center and mark which ones are provisioned through ACS Direct Offer or Direct Routing.
  2. Map each channel to its replacement. Voice to Teams Phone extensibility, SMS to the upcoming native capability or a partner, and so on.
  3. Plan the number migration. Porting phone numbers and re-provisioning messaging takes lead time – start the conversation with your telephony provider early.
  4. Pilot before 2028, not in 2028. Give yourself a comfortable runway to test the new channels with a small agent group before cutting over fully.

Final thoughts

So, to sum it up – do not panic. Your Dynamics 365 Contact Center is here to stay. What is changing is the plumbing underneath some of its channels, and Microsoft has given a clear migration path and a reasonable runway to get there. The organizations that come out of this smoothly will be the ones that audit early and migrate deliberately, rather than waiting for the 2028 deadline to force their hand.

For the authoritative dates, the full list of affected configurations and the official replacement options, refer to Microsoft’s documentation:

Have you started auditing your contact center channels for ACS dependencies yet? Let me know in the comments how your migration planning is going.

Hope this helped. You will also like the below posts.

Debajit Dutta


Discover more from Debajit's Power Apps & Dynamics 365 Blog

Subscribe to get the latest posts sent to your email.

Leave a Comment

Your email address will not be published. Required fields are marked *

Discover more from Debajit's Power Apps & Dynamics 365 Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading