Prepare to deploy Azure Communications Gateway

This article guides you through each of the tasks you need to complete before you can start to deploy Azure Communications Gateway. In order to be successfully deployed, the Azure Communications Gateway has dependencies on the state of your Operator Connect or Teams Phone Mobile environments.

The following sections describe the information you need to collect and the decisions you need to make prior to deploying Azure Communications Gateway.



You must be a telecommunications operator to use Azure Communications Gateway.

For Operator Connect or Teams Phone Mobile, you must also have signed an Operator Connect or Teams Phone Mobile agreement with Microsoft. For more information on these programs, see Operator Connect or Teams Phone Mobile.

For Zoom Phone Cloud Peering, you must also have started the onboarding process with Zoom to become a Zoom Phone Cloud Peering provider. For more information on Cloud Peering, see Zoom's Cloud Peering information.


You must fully understand the onboarding process for your chosen communications service and any dependencies introduced by the onboarding process.

Allow sufficient elapsed time for the deployment and onboarding process. For example, you might need wait up to two weeks for a new Azure Communications Gateway resource to be provisioned before you can connect it to your network.

You must own globally routable numbers for two types of testing:

  • Integration testing by your staff during deployment and integration
  • Service verification (continuous call testing) by your chosen communication services

The following table describes how many numbers you need to allocate.

Service Numbers for integration testing Service verification numbers
Operator Connect 1 (minimum) - Production deployments: 6
- Lab deployments: 3
Teams Phone Mobile 1 (minimum) - Production deployments: 6
- Lab deployments: 3
Microsoft Teams Direct Routing 1 (minimum) None (not applicable)
Zoom Phone Cloud Peering 1 (minimum) - US and Canada: 6
- Rest of world: 2


Service verification numbers must be usable throughout the lifetime of your deployment.

If you want to set up a lab deployment, you must have deployed a standard deployment or be about to deploy one. You can't use a lab deployment as a standalone Azure Communications Gateway deployment.

Arrange onboarding

You need a Microsoft onboarding team to deploy Azure Communications Gateway. Azure Communications Gateway includes an onboarding program called Included Benefits. If you're not eligible for Included Benefits or you require more support, discuss your requirements with your Microsoft sales representative.

The Operator Connect and Teams Phone Mobile programs also require an onboarding partner who manages the necessary changes to the Operator Connect or Teams Phone Mobile environments and coordinates with Microsoft Teams on your behalf. The Azure Communications Gateway Included Benefits project team fulfills this role, but you can choose a different onboarding partner to coordinate with Microsoft Teams on your behalf.

Ensure you have a suitable support plan

We strongly recommend that you have a support plan that includes technical support, such as Microsoft Unified Support.

Choose the Azure tenant to use

We recommend that you use an existing Microsoft Entra tenant for Azure Communications Gateway, because using an existing tenant uses your existing identities for fully integrated authentication. If you need to manage identities separately from the rest of your organization, or to set up different permissions for the Number Management Portal for different Azure Communications Gateway resources, create a new dedicated tenant first.

The Operator Connect and Teams Phone Mobile environments inherit identities and configuration permissions from your Microsoft Entra tenant through a Microsoft application called Project Synergy. You must add this application to your Microsoft Entra tenant as part of Connect Azure Communications Gateway to Operator Connect or Teams Phone Mobile (if your tenant does not already contain this application).


For Operator Connect and Teams Phone Mobile, production deployments and lab deployments must connect to the same Microsoft Entra tenant. Microsoft Teams configuration for your tenant shows configuration for your lab deployments and production deployments together.

Get access to Azure Communications Gateway for your Azure subscription

Access to Azure Communications Gateway is restricted. When you've completed the previous steps in this article:

  1. Contact your onboarding team and ask them to enable your subscription. If you don't already have an onboarding team, contact with your Azure subscription ID and contact details.
  2. Wait for confirmation that Azure Communications Gateway is enabled before moving on to the next step.

Create a network design

Decide how Azure Communications Gateway should connect to your network. You must choose:

  • The type of connection you want to use: for example, Microsoft Azure Peering Service Voice (recommended; sometimes called MAPS Voice).
  • The form of domain names Azure Communications Gateway uses towards your network: an autogenerated * domain name or a subdomain of a domain you already own (using domain delegation with Azure DNS).

For more information about your options, see Connectivity for Azure Communications Gateway.

For Teams Phone Mobile, you must decide how your network should determine whether a call involves a Teams Phone Mobile subscriber and therefore route the call to Microsoft Phone System. You can:

  • Use Azure Communications Gateway's integrated Mobile Control Point (MCP).
  • Connect to an on-premises version of Mobile Control Point (MCP) from Metaswitch.
  • Use other routing capabilities in your core network.

For more information on these options, see Call control integration for Teams Phone Mobile and Mobile Control Point in Azure Communications Gateway.

If you plan to route emergency calls through Azure Communications Gateway, read about emergency calling with your chosen communications service:

Connect your network to Azure

Configure connections between your network and Azure:

Next step