Microsoft to retire Azure Communication Services: What Dynamics 365 customers need to know

Oct 2, 2026

What Dynamics 365 customers need to plan for as ACS voice, messaging, and custom communication services move toward retirement

Microsoft has announced the retirement of Azure Communication Services (ACS) as a standalone offering, with retiring services reaching end of service on September 30, 2028. Beginning October 23, 2026, new customers will no longer be able to sign up for retiring ACS services. Organizations with ACS resources created before that date can continue using their existing resources and affected services during the transition period.

The change reaches well beyond Azure developers. Dynamics 365 Contact Center uses ACS for some voice, SMS, and WhatsApp configurations, while custom applications and integrations may also depend directly on ACS services. Microsoft is not providing an automatic migration, so affected workloads will need to be assessed, reconfigured, tested, and moved to a supported alternative before the retirement deadline.

​

Azure Communication Services

What Microsoft announced about the Azure Communication Services retirement

Microsoft is shifting its communications strategy toward capabilities integrated more closely with Teams, Dynamics 365, and Azure, while relying on Communications Platform as a Service providers for some scenarios.

Affected ACS capabilities fall into two groups: retired services, which will no longer be available after September 30, 2028, and services with breaking changes, which will remain available only when used in supported Teams-aligned scenarios.

Status
Retired
Breaking change
ACS services affected
Email, SMS, Advanced Messaging with WhatsApp, Chat, Rooms, Number Management (Direct Offer), Direct Routing, Job Router, Web and Mobile UI Library SDKs
Voice and Video Calling SDK, Call Automation, Call Recording, Call Diagnostics, Audio Streaming, Closed Captions

Key Azure Communication Services retirement dates

Organizations should begin by identifying where ACS is used and determining the appropriate migration path for each affected workload.

Timing
September 30, 2026
October 23, 2026
September 30, 2028
What happens
Microsoft announces the retirement. Organizations without an existing ACS resource can no longer acquire or port phone numbers into ACS.
New customers can no longer sign up for retiring ACS services.
Retired services reach end of service. Supporting data and telemetry for retired standalone services are decommissioned.

Affected services remain supported during the transition. Microsoft says existing service-level agreements continue through September 30, 2028, while support, security updates, and bug fixes remain available under applicable support plans. Some retiring services, including ACS SMS, are moving into maintenance mode rather than receiving continued feature development.

How the retirement affects Dynamics 365 Contact Center and Customer Service

Microsoft’s Dynamics 365 migration guidance specifically identifies three affected Dynamics 365 Contact Center configurations: voice through ACS Direct Offer or Direct Routing, SMS through ACS, and WhatsApp through ACS. Dynamics 365 Contact Center itself will continue operating after September 30, 2028. However, configurations that still depend on retired ACS capabilities will stop working unless they have been migrated.

Voice environments already using Microsoft Teams Phone extensibility are not affected. SMS channels already using Twilio or Infobip are also outside the ACS retirement, as are WhatsApp configurations already running through Twilio.

Organizations using Dynamics 365 Customer Service should review their own communication architecture rather than assume that every channel is affected. Microsoft’s current migration guidance is specifically focused on Contact Center configurations, so Customer Service customers with ACS-backed voice or custom communications should confirm their dependencies as part of the assessment.

Voice migration to Teams Phone extensibility

Microsoft positions Teams Phone extensibility as the strategic voice platform for Dynamics 365 Contact Center. Organizations currently using ACS for voice need to choose a migration path based on their existing carrier relationships, telephony infrastructure, geographic requirements, and operating model.

Current voice setup
ACS Direct Offer
ACS Direct Routing
ACS Direct Routing
Target path
Teams Calling Plan
Teams Direct Routing
Operator Connect
Best suited to
Organizations wanting Microsoft-managed telephony
Organizations keeping existing carriers and session border controllers
Organizations preferring a certified carrier to manage connectivity

These paths require the appropriate Microsoft Teams and Teams Phone licensing. Organizations should also account for resource accounts, number assignment, emergency calling requirements, and any changes to session border controller configurations.

SMS, WhatsApp, and phone numbers

The messaging migration is not simply a matter of moving an existing ACS connection into Contact Center. For Dynamics 365 Contact Center, Microsoft’s currently documented replacements for ACS-based SMS are Twilio and Infobip. For WhatsApp, Microsoft lists WhatsApp through Twilio as a supported provider-based option. Its migration overview also identifies Meta Direct as a migration path.

Microsoft also says it intends to provide equivalent SMS services within Dynamics 365 Contact Center before ACS reaches retirement. Until those capabilities are available and documented, organizations should plan around the supported provider options that exist today.

Existing numbers can often be moved, but portability depends on the destination provider, carrier, geography, and local requirements. Microsoft warns that migrating ACS SMS numbers to another provider requires re-verification with an SMS aggregator and may cause downtime.

That makes number migration one of the areas organizations should begin planning well before the September 2028 deadline.

What changes for custom integrations and Power Platform solutions

Organizations that built applications directly on ACS face service-by-service decisions.

ACS service
Email
SMS and WhatsApp
Chat
Job Router
Rooms
Web and Mobile UI Library SDKs
Calling SDK
Call Automation, Recording, Audio Streaming, Closed Captions
Call Diagnostics
Migration path
Microsoft 365 High Volume Email or Exchange Online
CPaaS providers such as Infobip or Telesign, while Dynamics 365 customers should follow the Contact Center-specific paths
Microsoft Graph Chat APIs
Dynamics 365 Contact Center, or providers such as Luware and Talkdesk
Teams meeting interoperability and Microsoft Graph APIs
No direct Microsoft replacement is currently listed in the ACS retirement migration table
Teams meeting interoperability
Teams Phone extensibility for supported, documented scenarios
Teams Call Quality Dashboard

Many of these are not like-for-like replacements. Microsoft Graph Chat APIs rely on Teams-based scenarios, which may not fit applications designed around anonymous consumer chat. Microsoft 365 High Volume Email is currently positioned for internal high-volume email scenarios rather than as a universal replacement for ACS Email.

Job Router customers can consider Dynamics 365 Contact Center, where Microsoft continues to expand routing functionality with capabilities such as AI-driven queue management for Dynamics 365 Contact Center.

Power Platform makers should also review flows that use the premium ACS SMS and ACS Email connectors in Power Automate. Microsoft’s retirement guidance does not specifically address those Power Automate connectors, but any flow that ultimately depends on a retired ACS service should be included in the organization’s dependency assessment.

Organizations should also identify any chat history, call recordings, operational data, or telemetry they need to retain and export it before the retirement date.

Licensing and cost considerations

The Azure Communication Services retirement may also change the cost structure of customer communication workloads.

Microsoft notes that supported alternatives can introduce different licensing or service costs. Voice migrations can require Teams and Teams Phone licensing, Calling Plans or carrier agreements. Email alternatives may require Microsoft 365 licensing, while SMS and WhatsApp migrations can introduce third-party provider contracts.

Organizations moving workloads into Dynamics 365 Contact Center may also face additional Dynamics 365 licensing requirements depending on their existing entitlements and chosen configuration. These requirements should be confirmed before a migration path is finalized.

Custom calling applications moving from standalone ACS scenarios to Teams-aligned services may require development work in addition to licensing and configuration changes. For many organizations, costs may therefore move away from Azure consumption and toward per-user licensing, telecommunications agreements, or third-party CPaaS contracts.

Service teams that have been modernizing customer engagement, including adopting capabilities such as AI email classification in Dynamics 365 Customer Service, now need to add communications infrastructure to their planning.

For others, the ACS retirement may become part of a broader Contact Center strategy, particularly as Microsoft continues expanding the platform with capabilities such as workforce engagement management for Dynamics 365 Customer Service and Contact Center.

How Dynamics 365 customers should prepare

With the retirement deadline still two years away, organizations have time to plan, but migrations involving telephony, messaging providers, phone numbers, licensing, and custom integrations can take significant coordination. The first priority should be understanding exactly where ACS is being used and which replacement path applies to each workload.

  1. Inventory every ACS dependency. Review Dynamics 365 communication channels, Azure resources, Power Automate connections, phone numbers, integrations, and custom applications.
  2. Map each dependency to a supported replacement. Voice, messaging, email, routing, and application services may require different migration paths.
  3. Confirm licensing and commercial terms. Review Microsoft licensing, carrier agreements, and third-party provider costs before committing to a target architecture.
  4. Plan number migration early. Portability, verification, carrier coordination, and regional requirements can introduce delays or downtime.
  5. Identify data that must be retained. Export recordings, chat history, operational information, or telemetry that needs to remain available after retirement.
  6. Pilot before cutover. Test customer-facing voice and messaging workloads before moving production traffic.
  7. Complete the migration before September 30, 2028. Retired ACS capabilities will no longer be available after that date.

Next steps

The Azure Communication Services retirement gives Dynamics 365 customers time to plan, but the transition is more than a routine product update. Organizations using ACS-based voice, SMS, WhatsApp, or custom communications need to identify their dependencies and move each workload to a supported destination. Starting that assessment now gives teams more time to resolve licensing, provider, phone number, development, and testing requirements before the September 30, 2028 deadline. Organizations that need help assessing their communication architecture can work with an experienced Dynamics 365 implementation partner.

Keep checking back with Dynamics101 for the latest news, independent analysis, and expert perspective across the Microsoft Dynamics and Power Platform ecosystem.

​