Understanding Azure Communication Services SMS
Azure Communication Services (ACS) SMS delivery failures stem from toll-free verification requirements, carrier filtering, opt-out management, and number capability mismatches. This guide covers every failure scenario and resolution.
Why This Problem Matters in Production
In enterprise Azure environments, Azure Communication Services SMS delivery issues rarely occur in isolation. They typically surface during peak usage periods, complex deployment scenarios, or when multiple services interact under load. Understanding the underlying architecture helps you move beyond symptom-level fixes to root cause resolution.
Before diving into the diagnostic commands below, it is important to understand the service’s operational model. Azure distributes workloads across multiple fault domains and update domains. When problems arise, they often stem from configuration drift between what was deployed and what the service runtime expects. This mismatch can result from ARM template changes that were not propagated, manual portal modifications that bypassed your infrastructure-as-code pipeline, or service-side updates that changed default behaviors.
Production incidents involving Azure Communication Services SMS delivery typically follow a pattern: an initial trigger event causes a cascading failure that affects dependent services. The key to efficient troubleshooting is isolating the blast radius early. Start by confirming whether the issue is isolated to a single resource instance, affects an entire resource group, or spans the subscription. This scoping exercise determines whether you are dealing with a configuration error, a regional service degradation, or a platform-level incident.
The troubleshooting approach in this guide follows the industry-standard OODA loop: Observe the symptoms through metrics and logs, Orient by correlating findings with known failure patterns, Decide on the most likely root cause and remediation path, and Act by applying targeted fixes. This structured methodology prevents the common anti-pattern of random configuration changes that can make the situation worse.
Service Architecture Background
To troubleshoot Azure Communication Services SMS delivery effectively, you need a mental model of how the service operates internally. Azure services are built on a multi-tenant platform where your resources share physical infrastructure with other customers. Resource isolation is enforced through virtualization, network segmentation, and quota management. When you experience performance degradation or connectivity issues, understanding which layer is affected helps you target your diagnostics.
The control plane handles resource management operations such as creating, updating, and deleting resources. The data plane handles the runtime operations that your application performs, such as reading data, processing messages, or serving requests. Control plane and data plane often have separate endpoints, separate authentication requirements, and separate rate limits. A common troubleshooting mistake is diagnosing a data plane issue using control plane metrics, or vice versa.
Azure Resource Manager (ARM) orchestrates all control plane operations. When you create or modify a resource, the request flows through ARM to the resource provider, which then provisions or configures the underlying infrastructure. Each step in this chain has its own timeout, retry policy, and error reporting mechanism. Understanding this chain helps you interpret error messages and identify which component is failing.
Common SMS Error Codes
| Error Code | Meaning | Resolution |
|---|---|---|
| 4001 | Message rejected by carrier | Check toll-free verification status |
| 4003 | Number not capable of SMS | Verify number capabilities in portal |
| 4010 | Recipient opted out | Check opt-out list, request re-opt-in |
| 5000 | Internal server error | Retry with exponential backoff |
| 5002 | Throttling | Reduce send rate, request higher limits |
| 9999 | Unknown failure | Check Azure status page, open support ticket |
Toll-Free Verification
Since 2023, US toll-free numbers require verification before sending SMS. Unverified numbers have severely limited throughput and messages may be filtered.
# Check phone number capabilities
az communication phonenumber show \
--phonenumber "+18005551234" \
--connection-string "endpoint=https://myacs.communication.azure.com/;accesskey=..."Verification Requirements
- Business name and EIN/Tax ID
- Business address matching registration
- Use case description (marketing, OTP, notifications)
- Sample messages you plan to send
- Expected monthly volume
- Opt-in mechanism description (how users consent)
Submit verification through the Azure portal under Communication Services → Phone Numbers → Toll-Free Verification. Processing takes 5–10 business days.
Short Code vs Toll-Free vs 10DLC
| Type | Throughput | Setup Time | Cost | Best For |
|---|---|---|---|---|
| Short Code | Highest (100+ MPS) | 8-12 weeks | $$$ | High-volume marketing, OTP |
| Toll-Free | Medium (verified) | 5-10 days | $$ | Transactional, notifications |
| 10DLC | Varies by brand score | 1-2 weeks | $ | General business messaging |
Sending SMS with the SDK
using Azure.Communication.Sms;
var client = new SmsClient("endpoint=https://myacs.communication.azure.com/;accesskey=...");
try
{
SmsSendResult result = await client.SendAsync(
from: "+18005551234",
to: "+14155551234",
message: "Your verification code is 123456",
options: new SmsSendOptions(enableDeliveryReport: true)
{
Tag = "verification-code"
});
Console.WriteLine($"MessageId: {result.MessageId}");
Console.WriteLine($"Successful: {result.Successful}");
if (!result.Successful)
{
Console.WriteLine($"Error: {result.ErrorMessage}");
}
}
catch (RequestFailedException ex)
{
Console.WriteLine($"SMS send failed: {ex.Message}");
Console.WriteLine($"Error Code: {ex.ErrorCode}");
}Batch Sending
var recipients = new[]
{
"+14155551234",
"+14155555678",
"+14155559012"
};
var results = await client.SendAsync(
from: "+18005551234",
to: recipients,
message: "Service maintenance scheduled for tonight 10 PM PST.",
options: new SmsSendOptions(enableDeliveryReport: true));
foreach (var result in results.Value)
{
if (!result.Successful)
{
Console.WriteLine($"Failed to send to {result.To}: {result.ErrorMessage}");
}
}Correlation and Cross-Service Diagnostics
Modern Azure architectures involve multiple services working together. A problem in Azure Communication Services SMS delivery may actually originate in a dependent service. For example, a database timeout might be caused by a network security group rule change, a DNS resolution failure, or a Key Vault access policy that prevents secret retrieval for the connection string.
Use Azure Resource Graph to query the current state of all related resources in a single query. This gives you a snapshot of the configuration across your entire environment without navigating between multiple portal blades. Combine this with Activity Log queries to build a timeline of changes that correlates with your incident window.
Application Insights and Azure Monitor provide distributed tracing capabilities that follow a request across service boundaries. When a user request touches multiple Azure services, each service adds its span to the trace. By examining the full trace, you can see exactly where latency spikes or errors occur. This visibility is essential for troubleshooting in microservices architectures where a single user action triggers operations across dozens of services.
For complex incidents, consider creating a war room dashboard in Azure Monitor Workbooks. This dashboard should display the key metrics for all services involved in the affected workflow, organized in the order that a request flows through them. Having this visual representation during an incident allows the team to quickly identify which service is the bottleneck or failure point.
Opt-Out Management
ACS automatically handles STOP/START keywords for US toll-free numbers. When a recipient texts STOP, they are added to the opt-out list and no further messages can be sent.
// Check opt-out status
var optOutClient = new SmsClient(connectionString);
var optOutResults = await optOutClient.CheckOptOutsAsync(
from: "+18005551234",
to: new[] { "+14155551234" });
foreach (var result in optOutResults.Value)
{
Console.WriteLine($"{result.To}: OptedOut = {result.IsOptedOut}");
}
// Remove from opt-out list (only if user re-consented)
await optOutClient.RemoveOptOutsAsync(
from: "+18005551234",
to: new[] { "+14155551234" });Delivery Reports and Event Grid
{
"eventType": "Microsoft.Communication.SMSDeliveryReportReceived",
"data": {
"messageId": "abc-123",
"from": "+18005551234",
"to": "+14155551234",
"deliveryStatus": "Delivered",
"deliveryStatusDetails": "Message delivered to handset",
"deliveryAttempts": [
{
"timestamp": "2024-01-15T10:30:00Z",
"httpStatusCode": 200,
"resultType": "success"
}
]
}
}# Create Event Grid subscription for SMS delivery reports
az eventgrid event-subscription create \
--name "sms-delivery-reports" \
--source-resource-id "/subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Communication/communicationServices/{acs}" \
--endpoint "https://myapp.azurewebsites.net/api/sms-webhook" \
--included-event-types "Microsoft.Communication.SMSDeliveryReportReceived" "Microsoft.Communication.SMSReceived"Troubleshooting Checklist
- Verify number capabilities — confirm your number supports SMS (not just voice)
- Check toll-free verification — unverified toll-free numbers are heavily filtered
- Check opt-out status — the recipient may have texted STOP
- Validate phone number format — use E.164 format (+1XXXXXXXXXX)
- Check rate limits — toll-free: ~1 MPS unverified, higher when verified
- Review diagnostic logs — enable Azure Monitor diagnostics for detailed error codes
- Test with a different recipient — isolate carrier-specific filtering
- Check Azure service health — confirm no regional outages
Enable Diagnostic Logging
# Enable diagnostic logs for ACS
az monitor diagnostic-settings create \
--name "acs-sms-logs" \
--resource "/subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Communication/communicationServices/{acs}" \
--workspace "{log-analytics-workspace-id}" \
--logs '[{"category":"SMSOperational","enabled":true}]'// Query SMS delivery failures
ACSSmsSendRequestOperational
| where TimeGenerated > ago(24h)
| where ResultType != "Succeeded"
| project TimeGenerated, MessageId, To, ResultType, ResultDescription
| order by TimeGenerated descMonitoring and Alerting Strategy
Reactive troubleshooting is expensive. For every hour spent diagnosing a production issue, organizations lose revenue, customer trust, and engineering productivity. A proactive monitoring strategy for Azure Communication Services SMS delivery should include three layers of observability.
The first layer is metric-based alerting. Configure Azure Monitor alerts on the key performance indicators specific to this service. Set warning thresholds at 70 percent of your limits and critical thresholds at 90 percent. Use dynamic thresholds when baseline patterns are predictable, and static thresholds when you need hard ceilings. Dynamic thresholds use machine learning to adapt to your workload’s natural patterns, reducing false positives from expected daily or weekly traffic variations.
The second layer is log-based diagnostics. Enable diagnostic settings to route resource logs to a Log Analytics workspace. Write KQL queries that surface anomalies in error rates, latency percentiles, and connection patterns. Schedule these queries as alert rules so they fire before customers report problems. Consider implementing a log retention strategy that balances diagnostic capability with storage costs, keeping hot data for 30 days and archiving to cold storage for compliance.
The third layer is distributed tracing. When Azure Communication Services SMS delivery participates in a multi-service transaction chain, distributed tracing via Application Insights or OpenTelemetry provides end-to-end visibility. Correlate trace IDs across services to pinpoint exactly where latency or errors originate. Without this correlation, troubleshooting multi-service failures becomes a manual, time-consuming process of comparing timestamps across different log streams.
Beyond alerting, implement synthetic monitoring that continuously tests critical user journeys even when no real users are active. Azure Application Insights availability tests can probe your endpoints from multiple global locations, detecting outages before your users do. For Azure Communication Services SMS delivery, create synthetic tests that exercise the most business-critical operations and set alerts with a response time threshold appropriate for your SLA.
Operational Runbook Recommendations
Document the troubleshooting steps from this guide into your team’s operational runbook. Include the specific diagnostic commands, expected output patterns for healthy versus degraded states, and escalation criteria for each severity level. When an on-call engineer receives a page at 2 AM, they should be able to follow a structured decision tree rather than improvising under pressure.
Consider automating the initial diagnostic steps using Azure Automation runbooks or Logic Apps. When an alert fires, an automated workflow can gather the relevant metrics, logs, and configuration state, package them into a structured incident report, and post it to your incident management channel. This reduces mean time to diagnosis (MTTD) by eliminating the manual data-gathering phase that often consumes the first 15 to 30 minutes of an incident response.
Implement a post-incident review process that captures lessons learned and feeds them back into your monitoring and runbook systems. Each incident should result in at least one improvement to your alerting rules, runbook procedures, or service configuration. Over time, this continuous improvement cycle transforms your operations from reactive fire-fighting to proactive incident prevention.
Finally, schedule regular game day exercises where the team practices responding to simulated incidents. Azure Chaos Studio can inject controlled faults into your environment to test your monitoring, alerting, and runbook effectiveness under realistic conditions. These exercises build muscle memory and identify gaps in your incident response process before real incidents expose them.
Summary
SMS delivery failures in Azure Communication Services trace back to toll-free verification (complete it in the Azure portal), carrier filtering (use verified numbers), opt-out management (check with the opt-out API), and number capability mismatches (verify your number supports SMS). Enable delivery reports via Event Grid and diagnostic logs via Azure Monitor to track failures in real time. For high-volume scenarios, consider short codes or 10DLC registration.
For more details, refer to the official documentation: What is Azure Communication Services?, SMS overview, Authenticate to Azure Communication Services.