Azure Communications Gateway documentation

The Azure Communications Gateway service will retire on October 30, 2025, and no new customers are being onboarded. To prevent any service disruption, please transition to another Microsoft Teams Direct Routing certified Session Border Controller (SBC) before October 30, 2025.

• Azure Communications Gateway documentation
• Overview
  • What is Azure Communications Gateway?
  • Get started
  • What's new?
• Planning
  • Your network and Communications Gateway
  • Onboarding and Included Benefits
  • Lab deployments
  • Connectivity
  • Reliability
  • Security
    • Overview of security
    • Security baseline
  • Provisioning API and portal
  • Plan and manage costs
  • Limits, quotas and restrictions
• Deployment
  • Prepare for deployment
  • Prepare for VNet injection preview
  • Deploy Azure Communications Gateway
  • Integrate with the Provisioning API
• Integration with Operator Connect and Teams Phone Mobile
  • Overview of interoperability
  • Setup
    • Connect
    • Prepare for live traffic
  • Mobile Control Point
  • Emergency calling
  • Use the Number Management Portal
• Integration with Microsoft Teams Direct Routing
  • Overview of interoperability
  • Setup
    • Connect
    • Prepare for live traffic
  • Emergency calling
  • Manage Direct Routing customers
• Integration with Zoom Phone Cloud Peering
  • Overview of interoperability
  • Setup
    • Connect
    • Prepare for live traffic
  • Emergency calling
  • Manage Zoom Phone Cloud Peering customers
• Maintenance
  • Set up user roles
  • Monitor Communications Gateway
  • Maintenance notifications
  • Get support or request changes
• Reference
  • Provisioning API Reference
  • Azure Communications Gateway product page
  • Overview of Operator Connect
  • Overview of Teams Phone Mobile
  • Overview of multitenant Microsoft Teams Direct Routing
  • Overview of Zoom Phone Cloud Peering
  • Monitoring data reference