{"id":41404,"date":"2026-11-04T15:27:49","date_gmt":"2026-11-04T14:27:49","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/?p=41404"},"modified":"2026-11-04T15:27:55","modified_gmt":"2026-11-04T14:27:55","slug":"microsoft-acs-retirement-finding-an-sms-api-you-can-trust","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/en\/microsoft-acs-retirement-finding-an-sms-api-you-can-trust\/","title":{"rendered":"Microsoft ACS Retirement: Finding an SMS API You Can Trust"},"content":{"rendered":"\n
Microsoft has announced the retirement of standalone Azure Communication Services (ACS) SMS<\/a>. For enterprises running automated workflows in Azure Logic Apps, Power Automate, and Copilot Studio, this means planning for a replacement that can support their long-term messaging needs. Microsoft recommends migrating business messaging to specialized providers in its ecosystem.<\/p>\n\n\n\n Choosing a replacement also means looking at how it handles volume, compliance, and resilience in the face of mission critical messages. Here\u2019s how Retarus\u2019 SMS API for Microsoft, now listed on Microsoft Learn<\/a>, handles these major considerations.<\/p>\n\n\n\n One major limitation of many SMS API providers is they accept only one phone number per call. Even the few connectors that support multiple recipients can only send the same broadcast text to everyone. When a workflow needs to send personalized SMS messages to hundreds of customers, each with its own order number, flight gate, or appointment time, conventional connectors require repeated loops. These loops slow down processing, increase workflow costs, and can quickly reach platform throttling limits.<\/p>\n\n\n\n The certified Retarus SMS Connector uses an enterprise job model that supports multiple messages and recipients in a single call. As part of Retarus\u2019 SMS API for Microsoft<\/a>, it supports both of the following scenarios:<\/p>\n\n\n\n One broadcast alert to up to 3,000 recipients<\/strong>: Send the same urgent update to 300 passengers on a delayed flight or an entire on-call team in one step.<\/p>\n\n\n\n Hundreds of personalized texts in the same batch:<\/strong> Bundle hundreds of custom messages in the same API call, each with its own dynamic text and customerRef<\/em> pulled directly from SAP S\/4HANA, Microsoft Dynamics 365, or SharePoint. Each customer receives their individual confirmation, while Azure Logic Apps or Power Automate executes just one action.<\/p>\n\n\n\nSend Up to 3,000 Recipients Personalized or Broadcast SMS in One Call<\/h2>\n\n\n\n
