Connect PD Azure SMS to an eligible existing Azure Communication Services resource. The gateway expects the resource’s Connection string and a provisioned From (sender); it does not create or register the sender.

Before starting, read the Azure SMS eligibility guide and confirm that your existing Azure resource and sender remain suitable.

Obtain the correct credential

Open the intended Communication Services resource in the Azure portal and find Settings → Keys. Copy its complete connection string through your approved credential-handling process. It contains both endpoint and access key, so treat the whole value as a secret.

This gateway does not use the tenant ID, subscription ID, application/client ID and client secret from an Azure app registration. Those values are not a replacement for its Connection string. If you cannot retrieve the resource’s keys, ask an Azure administrator to review the specific key-access permission; seeing a resource as Reader does not establish permission to reveal its keys.

Add the gateway

1. Open PD Modules → Azure SMS → Gateways → Add a gateway.
2. Choose Azure Communication Services and give the gateway a recognisable name.
3. Paste the full Connection string into its credential field.
4. Enter the resource’s send-ready number or supported sender ID in From (sender).
5. Review Request delivery reports, then save.
6. Use Test connection and read the result. Set the intended gateway as default when ready.

The saved secret is not displayed back as plain text. Check the intended resource when updating it rather than assuming every connection string belongs to the same sender.

Confirm the intended workflow

Use the phone number on the client’s contact. Selecting a custom-field source does not make Blesta read a different mobile field. The receiving number is separate from From, which identifies the sender.

A passing connection check does not establish sender ownership, destination eligibility or phone delivery. Rehearse wording through a separate Test / Debug Log only gateway; an intended real send is a different action. If setup fails, preserve the gateway label, time and redacted error without sharing the connection string.

See the PD Azure SMS Blesta guide for related tasks, or explore PD Azure SMS.