Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
Send an SMS message Try sending SMS messages using a purchased number from dfps-comm-service-dev SMS Communication Service
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIR%3C/text%3E%3C/svg%3E)
Irantha Rajapaksha
0
Reputation points
Description:
We are currently experiencing issues with SMS messages not being delivered when sent via Azure Communication Services (ACS) using a purchased number.
We attempted to send a test message via the Try SMS interface in the Azure Portal and through the SDK (SmsClient.Send using C#), but the message was not received on the target mobile number.
Details:
- Azure Resource Name: dfps-comm-service-dev
Region: [Your ACS region, e.g., Australia East]
From Number (purchased): +61361050310
To Number: +61433366729 (formatted in E.164)
Message: "Hello World 👋🏻 via SMS"
Delivery Report Requested: Yes (Tag: “My tag”)
Environment: Development (not in production yet)
SDK Used: Azure.Communication.Sms (latest version)
Steps Taken:
Verified the number format and capabilities.
Confirmed that the ACS connection string is correctly set and working.
Ensured the destination number is active and able to receive SMS.
Tried both portal-based and SDK-based sending – no success.
No clear error message or delivery failure was returned in the portal.
Checked Azure Monitor logs – no delivery confirmation or error codes present.
Request:
We kindly request assistance in:
Verifying whether the message was processed by ACS.
Providing any relevant delivery report/error code for the failed SMS attempt.
Confirming if the purchased number is provisioned correctly for outbound SMS to Australian carriers.
Advising on next steps or additional configuration required.
Please let us know if you require message timestamps, correlation IDs, or further diagnostic data.
Thank you.Description:
We are currently experiencing issues with SMS messages not being delivered when sent via Azure Communication Services (ACS) using a purchased number.
We attempted to send a test message via the Try SMS interface in the Azure Portal and through the SDK (SmsClient.Send using C#), but the message was not received on the target mobile number.
Details:
Azure Resource Name: dfps-comm-service-dev
Region: [Your ACS region, e.g., Australia East]
From Number (purchased): +61361050310
To Number: +61433366729 (formatted in E.164)
Message: "Hello World 👋🏻 via SMS"
Delivery Report Requested: Yes (Tag: “My tag”)
Environment: Development (not in production yet)
SDK Used: Azure.Communication.Sms (latest version)
Steps Taken:
Verified the number format and capabilities.
Confirmed that the ACS connection string is correctly set and working.
Ensured the destination number is active and able to receive SMS.
Tried both portal-based and SDK-based sending – no success.
No clear error message or delivery failure was returned in the portal.
Checked Azure Monitor logs – no delivery confirmation or error codes present.
Request:
We kindly request assistance in:
Verifying whether the message was processed by ACS.
Providing any relevant delivery report/error code for the failed SMS attempt.
Confirming if the purchased number is provisioned correctly for outbound SMS to Australian carriers.
Advising on next steps or additional configuration required.
Please let us know if you require message timestamps, correlation IDs, or further diagnostic data.
Thank you.
Azure Communication Services
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 15%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBN%3C/text%3E%3C/svg%3E)
Bhargavi Naragani 7,445 Reputation points Microsoft External Staff Moderator2025-08-07T02:22:23.26+00:00 You're currently using the ACS-purchased number
+61361050310to send SMS messages via the SDK and Azure Portal. However, this number is classified as a local (geographic) number in Australia.According to Microsoft’s official guidance:
Local (geographic) numbers in Australia do not support SMS, neither sending nor receiving. Phone number capabilities for Australia
This means any attempt to send SMS using this number will silently fail, even if your API call appears successful.
You can verify if the number
+61361050310is a local number by checking its Number Type and Capabilities in the Azure Portal under Communication Services => Phone Numbers, where it will be listed as Geographic with Calling only and no SMS support.In Australia, only specific number types are enabled for SMS:
To successfully send SMS in Australia via Azure Communication Services, you have two supported options Sender type support by country – Australia:
- Request a Mobile Number for Australia - Mobile numbers (
+614...) support 2-way SMS https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/telephony/get-phone-number?tabs=windows&pivots=platform-azp-new - Use an Alphanumeric Sender ID (outbound only):
- This displays a brand name instead of a number (e.g.,
DFPSAlert) - Only supports 1-way SMS, replies are not supported
- Ideal for alerts, OTPs, marketing messages
- This displays a brand name instead of a number (e.g.,
Hope this helps, if you have any further concerns or queries, please feel free to reach out to us.
- Request a Mobile Number for Australia - Mobile numbers (
-
Bhargavi Naragani 7,445 Reputation points Microsoft External Staff Moderator
2025-08-11T03:57:48.5566667+00:00 Hi Irantha Rajapaksha,
Just checking in to see if information in comment was helpful. If you have any further updates on this issue, please feel free to post/comment back.
Sign in to comment
Sign in to answer