The From (sender) field identifies the number or sender ID PD Azure SMS will use. Enter an identity provisioned for the same Azure Communication Services resource as the saved connection string. A typed brand name or telephone number is not provisioned by saving the gateway.

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

Check the sender in Azure

Review the intended resource’s Phone numbers or Alphanumeric sender ID section. Confirm that the identity is ready for the intended destination and any required provider verification is complete. Sender support depends on the type and destination; a number usable for voice is not automatically an SMS sender.

Use the current Microsoft sender-type guidance and the resource’s actual available capabilities. Do not infer worldwide reach from an enabled sender. An alphanumeric identity is a one-way branded choice where supported, with registration required for some destinations.

Configure the module identity

1. Open PD Modules → Azure SMS → Gateways and configure the intended Azure gateway.
2. Confirm its Connection string belongs to the resource holding the sender.
3. Enter the supported identity in From (sender). Use full international format for a telephone number.
4. Save, then review the triggers and Default routing that will use this gateway.

The receiving client’s number is a separate value. Changing From does not repair an incorrect recipient number or client country.

Understand the current gateway boundary

This gateway uses the direct Azure SMS route. It does not send the partner details required by Messaging Connect. A partner-managed number advertised elsewhere in Azure is therefore not established as supported merely by pasting it into From.

A connection-test pass does not verify the sender or its delivery route. For an unexplained real-send refusal, inspect the original History error and the provider result. An HTTP 401 can involve the sender as well as the credential; do not automatically rotate a working key before checking the resource/sender match.

Keep the original action time, gateway label and redacted provider result. Do not try repeated live sends to discover which unverified sender might work.

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