What the Azure SMS connection test checks in Blesta
Use Test connection to check the saved PD Azure SMS gateway without sending a text to a recipient. Understand its limited result before relying on it as evidence that live SMS will work.
Before starting, read the Azure SMS eligibility guide and confirm that your existing Azure resource and sender remain suitable.
Run the saved gateway check
- Open PD Modules → Azure SMS → Gateways.
- Configure the intended Azure Communication Services gateway.
- Check that the Connection string came from the intended resource and that From identifies its sender.
- Choose Test connection and read the complete response.
The module sends a connection probe with no recipients. It interprets the expected validation response as a connection result. This is different from creating a deliverable message, and it is not a general check of every Azure capability or an independent proof of sender eligibility.
Read a failure in context
For an invalid or incomplete connection string, copy the whole current value from the intended resource’s Keys page. Do not combine the endpoint from one resource with a key from another, or replace the credential with app-registration values.
If the connection cannot be reached, check the saved endpoint against the portal value and the hosting server’s supported outbound HTTPS access. A returned status alone is not a reason to assume a sender is ready or to switch to a broader account role.
A test refusal and a real-send refusal are different observations. A later send can fail because of the From sender, destination or verification even after a passing connection check. Record which action failed.
Verify live delivery separately
Confirm the resource, sender and destination in Azure before a deliberately approved real test. A Test / Debug Log only rehearsal verifies module wording without contacting Azure; it cannot validate this connection string. Send test SMS through the Azure gateway is a separate live action.
If a real attempt times out, investigate its Unknown result before repeating it. Azure might already have accepted the request. Keep the action time and redacted provider reference or error, and do not include credential material in a ticket.
See the PD Azure SMS Blesta guide for related tasks, or explore PD Azure SMS.
