{"id":11742,"date":"2026-05-08T15:17:10","date_gmt":"2026-05-08T13:17:10","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/en\/?p=11742"},"modified":"2026-05-08T15:17:14","modified_gmt":"2026-05-08T13:17:14","slug":"retarus-sms-connector-is-now-available-for-microsoft-power-platform-logic-apps-and-copilot-studio","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/en\/retarus-sms-connector-is-now-available-for-microsoft-power-platform-logic-apps-and-copilot-studio\/","title":{"rendered":"Retarus SMS Connector is now available for Microsoft Power Platform, Logic Apps, and Copilot Studio"},"content":{"rendered":"\n
Microsoft users can now bring enterprise-grade SMS directly into low-code workflows with the Retarus SMS connector, which is listed on Microsoft Learn for Power Automate, Power Apps, Logic Apps, and Copilot Studio. The connector gives organizations a direct way to send SMS, query job status, retrieve per-recipient delivery results, and access API version details from within Microsoft\u2019s automation environment.<\/p>\n\n\n\n
The key value of the new connector is simple: SMS can now become a native action inside Microsoft workflows instead of a separate integration project. When teams build a flow in Power Automate, create an app in Power Apps, work with Logic Apps, or design conversational automations in Copilot Studio, they can search the Microsoft connector catalog for Retarus SMS<\/strong> and use it as part of their business process design.<\/p>\n\n\n\n The official Microsoft connector page is here: Retarus SMS connector on Microsoft Learn<\/a>. From a practical perspective, the connector is available where Microsoft users, integration architects, process owners, analysts and managera already work.<\/p>\n\n\n\n In Power Automate, users add a new step, search for Retarus SMS, create a connection with their Retarus credentials, and then insert SMS actions into a flow just like any other Microsoft or third-party connector.<\/p>\n\n\n\n The SMS connector supports five core operations. These are enough to cover both straightforward alerting scenarios and more advanced transactional messaging patterns.<\/p>\n\n\n\n This matters because it moves the discussion beyond \u201csend a text\u201d to real process integration.<\/p>\n\n\n\n A Power Automate flow can send a message, capture the returned job ID, check delivery progress, and trigger follow-up steps based on message outcome.<\/p>\n\n\n\n One of the most compelling modern use cases is in Copilot Studio, where Microsoft explicitly lists the connector as available. That means organizations can combine conversational experiences and AI-guided process orchestration with enterprise SMS as an execution channel.<\/p>\n\n\n\n A strong example is an AI-assisted service escalation process. Imagine a Copilot-driven support experience that identifies a high-priority outage, gathers the right context from the user, creates a case, and then triggers a Retarus SMS message to the on-call engineer and backup contact Because the connector also supports status retrieval, the workflow can continue by checking whether the job was processed and logging the result back into the case or operations system.<\/p>\n\n\n\n
Microsoft lists the connector for Copilot Studio as Premium, for Power Apps as Premium, for Power Automate as Premium, and for Logic Apps as Standard, with availability across all standard regions.<\/a><\/p>\n\n\n\nHow the connector is provided in Microsoft<\/h2>\n\n\n\n
What you can do with it<\/h2>\n\n\n\n
\n
A strong Copilot use case<\/h2>\n\n\n\n