Skip to content

Learning Paths

Use this page to choose a reading path based on your role and goal. Each path is numbered, so read the pages in order for the best result. Every path ends with a checklist of concrete outcomes you should be able to demonstrate.

Pick one primary path first

If you fit multiple roles, pick the one that matches your current goal, complete that path, then read a second path opportunistically. Trying to follow every path in parallel dilutes progress.

Choose Your Path

Role Goal Time Budget Start With
Developer Integrate calling, chat, SMS, or email into an app 2-3 hours Overview, Platform Hub
Operator Provision and monitor ACS resources in production 2-4 hours Platform Hub, Operations Hub
Troubleshooter Diagnose calling quality, chat, SMS, and email delivery failures 2-4 hours + on-call reference Troubleshooting Hub 
flowchart TD
    A[Start Here] --> B[Platform Concepts]
    B --> C{Choose your path}
    C --> D[Developer: SDK Integration]
    C --> E[Operator: Provision and Monitor]
    C --> F[Troubleshooter: Channel Diagnosis]
    D --> G[Production Readiness]
    E --> G
    F --> G

Developer Path

Integrate Azure Communication Services into an application. Focuses on identity tokens, SDK selection per channel (calling, chat, SMS, email), and secure implementation patterns.

Time: 2-3 hours

flowchart TD
    A[Platform Overview] --> B[Identity and Tokens]
    B --> C[Choose SDK Guide]
    C --> D[Messaging Channels]
    D --> E[Security Best Practices]

Read in order:

  1. Overview
  2. Platform Hub — how ACS works, resource types, messaging channels
  3. Platform: Authentication — identity, access tokens, and token lifetimes
  4. Choose one SDK guide:
  5. Platform: Messaging Channels — pick calling, chat, SMS, or email
  6. Best Practices: Security

Outcomes

  • You can issue an ACS user identity and access token from a trusted server.
  • You can send or receive on your chosen channel (calling, chat, SMS, or email) from client code.
  • You can validate token expiry and refresh flows without leaking the connection string.
  • You know which SDK surface belongs to your channel and where the recipes live.

Microsoft Learn anchors

Operator Path

Provision and monitor ACS resources in production. Focuses on resource lifecycle, diagnostic logging, cost, and scale limits per channel.

Time: 2-4 hours

flowchart TD
    A[Platform Deep-Dive] --> B[Provisioning]
    B --> C[Monitoring and Diagnostics]
    C --> D[Scaling and Limits]
    D --> E[Cost Optimization]

Read in order:

  1. Platform Hub — how ACS works, resource types
  2. Operations sequence:
  3. Best Practices sequence:
  4. Reference sequence:

Outcomes

  • You can provision an ACS resource with the right domain and channel configuration.
  • You can wire diagnostic logging to Log Analytics and validate the tables land.
  • You can set service-health alerts and workload alerts for a critical channel.
  • You can identify the top-cost channel and apply a scale or filtering change.

Microsoft Learn anchors

Troubleshooter Path

Diagnose fast during a live incident. Focuses on channel-specific symptom mapping (calling quality, chat, SMS, email), diagnostic logs, and KQL.

Time: 2-4 hours + on-call reference

flowchart TD
    A[Troubleshooting Hub] --> B[Decision Tree]
    B --> C[First 10 Minutes by Channel]
    C --> D[KQL Query Packs]
    D --> E[Playbooks]

Read in order:

  1. Troubleshooting Hub
  2. Troubleshooting Methodology and Mental Model
  3. Decision Tree
  4. First 10 Minutes by channel:
  5. KQL Query Packs
  6. Playbooks Hub
  7. Reference: CLI Cheatsheet

Outcomes

  • You can select the right First 10 Minutes runbook from a channel symptom description.
  • You can write a KQL query against ACS diagnostic tables to isolate a failure window.
  • You can pick the right playbook without guessing which channel owns the symptom.
  • You can correlate ACS diagnostics with Azure Service Health to rule out platform events.

Microsoft Learn anchors

Track Selection Matrix

Situation Start with Then continue to
First integration into an app Developer Path Operator Path
Standing up an ACS resource for a workload Operator Path Developer Path
Preparing for launch Operator Path Troubleshooter Path
Active incident on a channel Troubleshooter Path Operator Path (hardening)

Live incident? Skip the path.

If you are actively responding to a page, jump straight to Troubleshooting Hub, the Decision Tree, and the First 10 Minutes runbook for your channel.

See Also

Sources