Microsoft is retiring Azure Communication Services (ACS) as a standalone offering to prioritize communications integrated with Microsoft Teams, Dynamics 365, and Azure, while relying on Communications Platform as a Service partners for other scenarios.
The retirement was announced on September 23, 2026 and takes effect on September 30, 2028. This is not an immediate shutdown: existing ACS resources remain available and supported during the transition period, with current SLAs, security updates, and break-fix support continuing through the retirement date.^1^
What this means for your applications
Microsoft divides ACS capabilities into two groups:
Fully retiring on September 30, 2028
- Email
- SMS
- Advanced Messaging with WhatsApp
- Chat, including Chat for Teams Meeting interoperability
- Rooms
- Number Management (Direct Offer)
- Direct Routing
- Job Router
- Web and Mobile UI Library SDKs
Remaining with breaking changes
- Voice and Video Calling SDK
- Call Diagnostics
- Call Automation
- Audio Streaming
- Call Recording
- Closed Captions
The second group will remain available, but after the deadline it must be used with supported Teams-aligned services and updated major-version SDKs.^2^
If you moved to ACS Email
ACS Email itself is in the fully retiring category. Microsoft lists these migration choices:
- Microsoft 365 High Volume Email for eligible internal-email scenarios
- Exchange Online
- Listed third-party providers for transactional or application email
These alternatives are not necessarily feature-equivalent, so the appropriate destination depends on whether your applications send internal mail, transactional notifications, bulk messages, or customer-facing email. Unfortunately, the retirement guide does not list another Azure-native, standalone transactional email service as a direct ACS Email replacement.^1^
Recommended next actions
- Inventory affected resources:
In Azure portal, open Advisor → Service Retirement, or Advisor → Recommendations → Operational Excellence. Export the results if multiple subscriptions are involved.
- Map each application to the ACS capability it uses:
Email, SMS, Chat, PSTN, and the other fully retiring services need replacement architectures. Calling and Call Automation need evaluation against the supported Teams-aligned scenarios.
- Avoid expanding dependency on retiring services:
Onboarding restrictions begin October 23, 2026. Existing resources created before that date can continue supporting current workloads, but Microsoft may introduce additional expansion restrictions during the transition.
- Select and test replacements well before September 2028:
Treat migrations such as ACS Email to Exchange Online or a third-party provider as application migrations—not merely connection-string changes.
- Export required data and telemetry:
If an application will not move to a supported ACS scenario, export relevant chat messages, recordings, and Azure Monitor telemetry before retirement. Supporting data for retired standalone services will be decommissioned after the deadline.
After September 30, 2028, retired capabilities will no longer be available; dependent API and SDK operations may return unsupported-operation errors. Azure lifecycle guidance therefore requires migration before a retirement date rather than continuing to run without support.^3^
References
- Retirement and breaking changes guide for Azure Communication Services
- What's new in Azure Communication Services
- Infrastructure Lifecycle FAQ - Microsoft Azure