Troubleshooting Overview
This guide provides a structured, hypothesis-driven approach to diagnosing and resolving issues across Azure Communication Services (ACS).
How It Works
graph TD
A[Observe Symptom] --> B[List Hypotheses]
B --> C[Collect Evidence]
C --> D{Validate?}
D -- No --> B
D -- Yes --> E[Identify Root Cause]
E --> F[Mitigate/Resolve]
Start Here
Quick Routing
graph TD
Start[Symptom] --> SMS[SMS Issues]
Start --> Email[Email Issues]
Start --> Chat[Chat/Messaging]
Start --> Call[Voice/Video/Teams]
SMS --> SMS_Del[Delivery Failure]
Email --> Em_Del[Bounces/Spam]
Chat --> Ch_Con[Connectivity/Latency]
Call --> Cal_Qual[Poor Quality/Drops]
Symptom Table
Representative Error Patterns
| Error Code | Meaning | Likely Cause |
429 | Too Many Requests | Throttling/Rate limits exceeded |
401 | Unauthorized | Expired token or invalid credential |
403 | Forbidden | Insufficient permissions for resource |
404 | Not Found | Resource (thread, user) deleted or invalid |
Topics
See Also
Sources
- Internal Support Playbooks
- Azure SDK Troubleshooting Guides