An Azure communication platform for deploying applications across devices and platforms.
If the forms depend on standalone Azure Communication Services features, action is required before September 30, 2028.
Key points:
- Standalone ACS is retiring as a standalone offering effective September 30, 2028.
- Existing ACS resources created before October 23, 2026 can continue to be used during the transition period.
- After September 30, 2028, retired ACS services won’t be supported or usable, and related API/SDK operations might return errors.
- If the forms do not use ACS, no ACS-specific settings change is indicated by this notice.
What to do now:
- In Azure portal, check whether the forms or their backend workflows use Azure Communication Services resources.
- Review Azure Advisor:
- Azure portal > Advisor > Recommendations > Operational Excellence
- Azure portal > Advisor > Service Retirement These tools can identify subscriptions and resources affected by ACS retirement.
- Check Azure Service Health for the advisory tied to the notification and confirm which resources are impacted.
- If ACS is being used, plan to transition impacted workloads before September 30, 2028 to avoid disruption.
- If the workload uses supported ACS-connected services, ACS identity continues to work with supported services.
Important detail:
- During the retirement period, existing functionality remains supported with critical security and stability updates, but Microsoft is not committing to new feature development for retiring services.
- Existing Azure resources such as resource groups and connection strings remain available from the notification date through September 30, 2028.
- Retirement and breaking changes guide for Azure Communication Services
- Retirement and breaking changes guide for Azure Communication Services
- Retirement and breaking changes guide for Azure Communication Services
- Retirement and breaking changes guide for Azure Communication Services
- Troubleshooting in Azure Communication Services