Prepare for live traffic with Microsoft Teams Direct Routing and Azure Communications Gateway
Before you can launch your Microsoft Teams Direct Routing service, you and your onboarding team must:
- Test your service.
- Prepare for launch.
In this article, you learn about the steps that you and your Azure Communications Gateway onboarding team must take.
Important
Some steps can require days or weeks to complete. We recommend that you read through these steps in advance to work out a timeline.
Prerequisites
Complete the following procedures.
- Prepare to deploy Azure Communications Gateway
- Deploy Azure Communications Gateway
- Integrate with Azure Communications Gateway's Provisioning API
- Connect Azure Communications Gateway to Microsoft Teams Direct Routing
This procedure includes setting up test numbers for integration testing. The test numbers must be in a Microsoft 365 tenant other than the tenant for Azure Communications Gateway, as if you're providing service to a real customer. We call this tenant (which you control) a test customer tenant, corresponding to your test customer (to which you allocate the test numbers).
You must be able to do the following for your test customer tenant:
Sign in to the Microsoft 365 admin center as a Global Administrator
Use PowerShell to change Microsoft Teams Direct Routing configuration.
Provide user accounts licensed for Microsoft Teams in the test customer tenant. For more information on suitable licenses, see the Microsoft Teams documentation.
- You need two user or resource accounts to activate tenant-specific Azure Communications Gateway subdomains that you choose and add to Microsoft 365 as part of this procedure. Lab deployments require one account.
- You need at least one user account to use for testing calls. You can reuse one of the accounts that you use to activate the tenant-specific subdomains, or you can use an account with one of the other domain names for this tenant.
You must be able to provision Azure Communications Gateway during this procedure.
- To use Azure Communications Gateway's Number Management Portal (preview) for provisioning (recommended), you must have Reader access to the Azure Communications Gateway resource and ProvisioningAPI.ReadUser and ProvisioningAPI.WriteUser roles for the AzureCommunicationsGateway enterprise application.
- To use Azure Communications Gateway's Provisioning API (preview), you must be able to make requests using a client integrated with the API. You must also have access to the API Reference.
You must be able to make changes to your network's routing configuration.
Configure numbers for integration testing
Setting up test numbers requires configuration in the test customer tenant and on Azure Communications Gateway.
Follow Manage Microsoft Teams Direct Routing customers and numbers with Azure Communications Gateway for your test customer tenant and numbers. For steps that describe asking a customer to make changes to their tenant, make those changes yourself in your test customer tenant.
Important
Ensure you configure a dedicated test customer (Microsoft 365) tenant, not the Azure tenant that contains Azure Communications Gateway. Using a dedicated test customer tenant matches the configuration required for a real customer.
Carry out integration testing and request changes
Network integration includes identifying SIP interoperability requirements and configuring devices to meet these requirements. For example, this process often includes interworking header formats and/or the signaling and media flows used for call hold and session refresh.
You must test typical call flows for your network. Your onboarding team will provide an example test plan that we recommend you follow. Your test plan should include call flow, failover, and connectivity testing.
- If you decide that you need changes to Azure Communications Gateway, ask your onboarding team. Microsoft must make the changes for you.
- If you need changes to the configuration of devices in your core network, you must make those changes.
Test raising a ticket
You must test that you can raise tickets in the Azure portal to report problems with Azure Communications Gateway. See Get support or request changes for Azure Communications Gateway.
Learn about monitoring and maintenance
Your operations team can use a selection of key metrics to monitor Azure Communications Gateway. These metrics are available to anyone with the Reader role on the subscription for Azure Communications Gateway. See Monitoring Azure Communications Gateway.
Your operations team must have Azure Monitor alerts for:
- Azure Service Health notifications to stay informed about upcoming upgrades and scheduled maintenance activities.
- Azure resource health notifications to stay informed about changes in the health of Azure Communications Gateway.
Next steps
- Learn about getting support and requesting changes for Azure Communications Gateway.
- Learn about monitoring Azure Communications Gateway.
- Learn about maintenance notifications.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for