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 or service provider and you must 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.
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 that you can use for testing, as follows.
|Type of testing||Numbers required|
|Automated validation testing by Microsoft Teams test suites||Minimum: 6. Recommended: 9 (to run tests simultaneously).|
|Manual test calls made by you and/or Microsoft staff during integration testing||Minimum: 1|
After deployment, the automated validation testing numbers use synthetic traffic to continuously check the health of your deployment.
1. Arrange onboarding
For Operator Connect and Teams Phone Mobile, you need an onboarding partner for integrating with Microsoft Phone System. If you're not eligible for onboarding to Microsoft Teams through Azure Communications Gateway's Included Benefits or you haven't arranged alternative onboarding with Microsoft through a separate arrangement, you need to arrange an onboarding partner yourself.
2. Ensure you have a suitable support plan
3. Choose the Azure tenant to use
The Operator Connect and Teams Phone Mobile programs require your Azure Active Directory tenant to contain a Microsoft application called Project Synergy. Operator Connect and Teams Phone Mobile inherit permissions and identities from your Azure Active Directory tenant through the Project Synergy application. The Project Synergy application also allows configuration of Operator Connect or Teams Phone Mobile and assigning users and groups to specific roles.
We recommend that you use an existing Azure Active Directory tenant for Azure Communications Gateway, because using an existing tenant uses your existing identities for fully integrated authentication. However, if you need to manage identities for Operator Connect separately from the rest of your organization, create a new dedicated tenant first.
4. 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, contact your onboarding team and ask them to enable your subscription. If you don't already have an onboarding team, contact email@example.com with your Azure subscription ID and contact details.
Wait for confirmation that Azure Communications Gateway is enabled before moving on to the next step.
5. Create a network design
You must use Microsoft Azure Peering Service (MAPS) or ExpressRoute Microsoft Peering to connect your on-premises network to Azure Communications Gateway.
- In most cases, we recommend using Microsoft Azure Peering Service (MAPS) to connect your network to Azure Communications Gateway.
- Alternatively, you can use an Azure ExpressRoute circuit to achieve Microsoft Peering and connect your network to Azure Communications Gateway. For more information, and examples of why you might want to use ExpressRoute Microsoft Peering, see Using ExpressRoute for Microsoft PSTN Services.
If you want to use ExpressRoute Microsoft Peering, consult with your onboarding team and ensure that it's available in your region.
Ensure your network is set up as shown in the following diagram and has been configured in accordance with the Network Connectivity Specification that you've been issued. You must have two Azure Regions with cross-connect functionality. For more information on the reliability design for Azure Communications Gateway, see Reliability in 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 Emergency calling for Operator Connect and Teams Phone Mobile with Azure Communications Gateway to learn about your options.
6. Configure MAPS or ExpressRoute
Connect your network to Azure Communications Gateway:
- To configure MAPS, follow the instructions in Azure Internet peering for Communications Services walkthrough.
- To configure ExpressRoute Microsoft Peering, follow the instructions in Tutorial: Configure peering for ExpressRoute circuit.