For a real Azure send, first confirm the existing resource and sender against the current eligibility and service-change guide. Configuration changes do not remove Azure’s onboarding restrictions.

A long SMS can be billed as several message parts even when a phone displays one conversation bubble. Use PD Azure SMS’s Count segments before sending, and treat it as a length estimate rather than a final currency quote.

Measure the message

1. Open PD Modules → Azure SMS → Send SMS.
2. Enter the intended text, or fill the composer from a template and review it.
3. Choose Count segments.
4. Review the encoding and segment count, then edit and count again if necessary.

This preview does not send an SMS. Keep the intended recipient and Send via choice under review before using the separate Send SMS action.

Why a short message can become several parts

For GSM-7 text, the usual single-part capacity is 160 units. Longer messages use 153 per part because multipart information takes space. Characters from the GSM extension set, including braces and the euro symbol, consume extra units.

Unicode messages normally have a single-part capacity of 70 units and multipart capacity of 67. An emoji can use more than one unit. Adding one character outside the GSM alphabet can therefore change the encoding and increase the count for the whole message. These are the module’s preview capacities. Microsoft’s Azure SMS FAQ also explains the different single-segment capacities and carrier behaviour for long messages.

Keep the estimate useful

Count the actual intended wording, including links and personalised values, rather than an empty template. A longer customer name or ticket subject can change the final message length. For campaigns, the preview estimates audience and segments; personalised messages and provider processing can change the final billed total.

Shorten unnecessary wording without removing the reason for the text or the action the recipient needs. Do not split one meaningful notice into repeated manual sends just to reach a displayed count. Azure charges vary by destination and sending setup; the module’s segment count is not a guaranteed monetary charge.

Check the Azure send separately

The length preview does not validate the Azure sender, current account eligibility or destination. A short message can still be refused. If an intended send fails, read its recorded error and the original wording before shortening and repeating it; do not assume length explains every failure. Keep the Azure message reference when investigating an accepted message whose later delivery is in doubt.

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