Skip to content

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

Scenario Action
First time responding to an ACS incident Go to First 10 Minutes
Known channel issue (SMS, Email, etc.) Browse Playbooks
Need specialized telemetry data Review Evidence Map
Performing advanced analysis Use KQL Query Library

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

Channel Common Symptom Potential Playbook
SMS Message not received SMS Delivery Failure
Email Verification failing Domain Verification
Chat Real-time events missing Real-time Notifications
Voice/Video Call drops after 30s Call Drops
Teams Interop Cannot join meeting Teams Join Failures

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