Connect Azure Communications Gateway to Operator Connect or Teams Phone Mobile

Artiklu
03/22/2024

After you deploy Azure Communications Gateway and connect it to your core network, you need to connect it to Microsoft Phone System. You also need to onboard to the Operator Connect or Teams Phone Mobile environments.

This article describes how to set up Azure Communications Gateway for Operator Connect and Teams Phone Mobile. After you finish the steps in this article, you can prepare for live traffic with Operator Connect, Teams Phone Mobile and Azure Communications Gateway.

Tip

This article assumes that your Azure Communications Gateway onboarding team from Microsoft is also onboarding you to Operator Connect and/or Teams Phone Mobile. If you've chosen a different onboarding partner for Operator Connect or Teams Phone Mobile, you need to ask them to arrange changes to the Operator Connect and/or Teams Phone Mobile environments.

Prerequisites

You must deploy Azure Communications Gateway.

You must have access to a user account with the Microsoft Entra Global Administrator role.

You must allocate "service verification" test numbers. These numbers are used by the Operator Connect and Teams Phone Mobile programs for continuous call testing. Production deployments need six numbers for each service. Lab deployments need three numbers for each service.

If you selected the service you're setting up as part of deploying Azure Communications Gateway, you've allocated numbers for the service already.
Otherwise, choose the phone numbers now (in E.164 format and including the country code) and names to identify them. We recommend names of the form OC1 and OC2 (for Operator Connect) and TPM1 and TPM2 (for Teams Phone Mobile).

You must also allocate at least one test number for each service for integration testing.

If you want to set up Teams Phone Mobile and you didn't select it when you deployed Azure Communications Gateway, choose:

The number used in Teams Phone Mobile to access the Voicemail Interactive Voice Response (IVR) from native dialers.
The method for routing Teams Phone Mobile calls to Microsoft Phone System. Choose from:
- Integrated MCP (MCP in Azure Communications Gateway).
- On-premises MCP.
- Another method to route calls.

Enable Operator Connect or Teams Phone Mobile support

Note

If you selected Operator Connect or Teams Phone Mobile when you deployed Azure Communications Gateway, skip this step and go to Add the Project Synergy application to your Azure tenant.

Sign in to the Azure portal.
In the search bar at the top of the page, search for your Communications Gateway resource and select it.
In the side menu bar, under Communications services, select Operator Connect or Teams Phone Mobile (as appropriate) to open a page for the service.
Select Operator Connect settings or Teams Phone Mobile settings.
Fill in the fields, then select Review + create and Create.
Select the Overview page for your resource.
Select Add test lines and add the service verification lines you chose in Prerequisites. Set the Testing purpose to Automated.

Important

Do not add the numbers for integration testing. You will configure numbers for integration testing when you carry out integration testing and prepare for live traffic.
Wait for your resource to be updated. When your resource is ready, the Provisioning Status field on the resource overview changes to "Complete." We recommend that you check in periodically to see if the Provisioning Status field is "Complete." This step might take up to two weeks.

Add the Project Synergy application to your Azure tenant

Before starting this step, check that the Provisioning Status field for your resource is "Complete".

Note

This step and the next step (Assign an Admin user to the Project Synergy application) set you up as an Operator in the Teams Phone Mobile and Operator Connect environments. If you've already gone through onboarding, go to Find the Application ID for your Azure Communication Gateway resource.

The Operator Connect and Teams Phone Mobile programs require your Microsoft Entra tenant to contain a Microsoft application called Project Synergy. Operator Connect and Teams Phone Mobile inherit permissions and identities from your Microsoft Entra 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.

To add the Project Synergy application:

Check whether the Microsoft Entra ID (AzureAD) module is installed in PowerShell. Install it if necessary.
1. Open PowerShell.
2. Run the following command and check whether AzureAD appears in the output.
```
Get-Module -ListAvailable
```
3. If AzureAD doesn't appear in the output, install the module.
  1. Close your current PowerShell window.
  2. Open PowerShell as an admin.
  3. Run the following command.
```
Install-Module AzureAD
```
  4. Close your PowerShell admin window.
Sign in to the Azure portal as a Microsoft Entra Global Admin.
Select Microsoft Entra ID.
Select Properties.
Scroll down to the Tenant ID field. Your tenant ID is in the box. Make a note of your tenant ID.
Open PowerShell.

Run the following cmdlet, replacing <TenantID> with the tenant ID you noted down in step 5.

Connect-AzureAD -TenantId "<TenantID>"
New-AzureADServicePrincipal -AppId eb63d611-525e-4a31-abd7-0cb33f679599 -DisplayName "Operator Connect"

Assign an Admin user to the Project Synergy application

The user who sets up Azure Communications Gateway needs to have the Admin user role in the Project Synergy application. Assign them this role in the Azure portal.

In the Azure portal, go to Microsoft Entra ID and then Enterprise applications using the left-hand side menu. Alternatively, you can search for Enterprise applications in the search bar; it's under the Services subheading.
Set the Application type filter to All applications using the drop-down menu.
Select Apply.
Search for Project Synergy using the search bar. The application should appear.
Select your Project Synergy application.
Select Users and groups from the left hand side menu.
Select Add user/group.
Specify the user who should set up Azure Communications Gateway and give them the Admin role.

Caution

Do not change any of the following Operator Connect configuration in your tenant (whether through the Operator Connect configuration portal or through Operator Connect APIs).

Calling Profiles with a CommsGw Suffix in the configuration portal or NameSuffix on the Operator Connect APIs
Trunks with FQDNs ending with .commsgw.azure.com

We manage this configuration for you. Editing this configuration is likely to cause issues with your Azure Communications Gateway service.

Find the Application ID for your Azure Communication Gateway resource

Each Azure Communications Gateway resource automatically receives a system-assigned managed identity, which Azure Communications Gateway uses to connect to the Operator Connect API. You need to find the Application ID of the managed identity, so that you can connect Azure Communications Gateway to the Operator Connect API in Set up application roles for Azure Communications Gateway and Add the Application IDs for Azure Communications Gateway to Operator Connect.

Sign in to the Azure portal.
If you don't already know the name of your Communications Gateway resource, search for Communications Gateways and note the name of the resource.
Search for the name of your Communications Resource. You should see an enterprise application with that value under the Microsoft Entra ID subheading. You might need to select Continue searching in Microsoft Entra ID to find it.
Select the enterprise application.
Check that the Name matches the name of your Communications Gateway resource.
Make a note of the Application ID.

Set up application roles for Azure Communications Gateway

Azure Communications Gateway contains services that need to access the Operator Connect API on your behalf. To enable this access, you must grant specific application roles to the system-assigned managed identity for Azure Communications Gateway under the Project Synergy Enterprise Application. You created the Project Synergy Enterprise Application in Add the Project Synergy application to your Azure tenant.

You must carry out this step once for each Azure Communications Gateway resource that you want to use for Operator Connect or Teams Phone Mobile.

Important

Granting permissions has two parts: configuring the system-assigned managed identity for Azure Communications Gateway with the appropriate roles (this step) and adding the application ID of the managed identity to the Operator Connect or Teams Phone Mobile environment. You'll add the application ID to the Operator Connect or Teams Phone Mobile environment later, in Add the Application IDs for Azure Communications Gateway to Operator Connect.

Do the following steps in the tenant that contains your Project Synergy application.

Check whether the Microsoft Graph (Microsoft.Graph) module is installed in PowerShell. Install it if necessary.
1. Open PowerShell.
2. Run the following command and check whether Microsoft.Graph appears in the output.
```
Get-Module -ListAvailable
```
3. If Microsoft.Graph doesn't appear in the output, install the module.
  1. Close your current PowerShell window.
  2. Open PowerShell as an admin.
  3. Run the following command.
```
Install-Module -Name Microsoft.Graph -Scope CurrentUser
```
  4. Close your PowerShell admin window.
Sign in to the Azure portal as a Microsoft Entra Global Administrator.
Select Microsoft Entra ID.
Select Properties.
Scroll down to the Tenant ID field. Your tenant ID is in the box. Make a note of your tenant ID.
Open PowerShell.
Run the following cmdlet, replacing <TenantID> with the tenant ID you noted down in step 5.
```
Connect-MgGraph -Scopes "Application.Read.All", "AppRoleAssignment.ReadWrite.All" -TenantId "<TenantID>"
```
If you're prompted to grant permissions for Microsoft Graph Command Line Tools, select Accept to grant permissions.
Run the following cmdlet, replacing <CommunicationsGatewayName> with the name of your Azure Communications Gateway resource.
```
$acgName = "<CommunicationsGatewayName>"
```

Run the following PowerShell commands. These commands add the following roles for Azure Communications Gateway: TrunkManagement.Read, TrunkManagement.Write, partnerSettings.Read, NumberManagement.Read, NumberManagement.Write, Data.Read, Data.Write.

# Get the Service Principal ID for Project Synergy (Operator Connect)
$projectSynergyApplicationId = "eb63d611-525e-4a31-abd7-0cb33f679599"
$projectSynergyEnterpriseApplication = Get-MgServicePrincipal -Filter "AppId eq '$projectSynergyApplicationId'" # "Application.Read.All"

# Required Operator Connect - Project Synergy Roles
$trunkManagementRead = "72129ccd-8886-42db-a63c-2647b61635c1"
$trunkManagementWrite = "e907ba07-8ad0-40be-8d72-c18a0b3c156b"
$partnerSettingsRead = "d6b0de4a-aab5-4261-be1b-0e1800746fb2"
$numberManagementRead = "130ecbe2-d1e6-4bbd-9a8d-9a7a909b876e"
$numberManagementWrite = "752b4e79-4b85-4e33-a6ef-5949f0d7d553"
$dataRead = "eb63d611-525e-4a31-abd7-0cb33f679599"
$dataWrite = "98d32f93-eaa7-4657-b443-090c23e69f27"
$requiredRoles = $trunkManagementRead, $trunkManagementWrite, $partnerSettingsRead, $numberManagementRead, $numberManagementWrite, $dataRead, $dataWrite

# Locate the Azure Communications Gateway resource by name
$acgServicePrincipal = Get-MgServicePrincipal -Filter ("displayName eq '$acgName'")

# Assign the required roles to the managed identity of the Azure Communications Gateway resource
$currentAssignments = Get-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $acgServicePrincipal.Id
foreach ($appRoleId in $requiredRoles) {
    $assigned = $currentAssignments | Where-Object { $_.AppRoleId -eq $AppRoleId }
    if (-not $assigned) {
        $params = @{
            principalId = $acgServicePrincipal.Id
            resourceId = $projectSynergyEnterpriseApplication.Id
            appRoleId = $appRoleId
        }
        New-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $acgServicePrincipal.Id -BodyParameter $params
    }
}

# Check the assigned roles
Get-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $acgServicePrincipal.Id

To end your current session, disconnect from Microsoft Graph.
```
Disconnect-MgGraph
```

Provide additional information to your onboarding team

Note

This step is required to set you up as an Operator in the Teams Phone Mobile and Operator Connect environments. Skip this step if you've finished onboarding.

Before your onboarding team can finish onboarding you to the Operator Connect and/or Teams Phone Mobile environments, you need to provide them with some additional information.

Wait for your onboarding team to provide you with a form to collect the additional information.
Complete the form and give it to your onboarding team.
Wait for your onboarding team to confirm that the onboarding process is complete.

If you don't already have an onboarding team, contact azcog-enablement@microsoft.com, providing your Azure subscription ID and contact details.

Test your Operator Connect portal access

Important

Before testing your Operator Connect portal access, wait for your onboarding team to confirm that the onboarding process is complete.

Go to the Operator Connect homepage and check that you're able to sign in.

Add the Application IDs for Azure Communications Gateway to Operator Connect

You must enable Azure Communications Gateway within the Operator Connect or Teams Phone Mobile environment. This process requires configuring your environment with two Application IDs:

The Application ID of the system-assigned managed identity that you found in Find the Application ID for your Azure Communication Gateway resource. This Application ID allows Azure Communications Gateway to use the roles that you set up in Set up application roles for Azure Communications Gateway.
A standard Application ID for an automatically created AzureCommunicationsGateway enterprise application. This ID is always 8502a0ec-c76d-412f-836c-398018e2312b.

To add the Application IDs:

Log into the Operator Connect portal.
Add a new Application Id for the Application ID that you found for the managed identity.
Add a second Application Id for the value 8502a0ec-c76d-412f-836c-398018e2312b.

Register your deployment's domain name in Microsoft Entra

Microsoft Teams only sends traffic to domains that you confirm that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN). You need to add this domain name to your Microsoft Entra tenant as a custom domain name, share the details with your onboarding team and then verify the domain name. This process confirms that you own the domain.

Navigate to the Overview of your Azure Communications Gateway resource and select Properties. Find the field named Domain. This name is your deployment's domain name.
Complete the following procedure: Add your custom domain name to Microsoft Entra ID.
Share your DNS TXT record information with your onboarding team. Wait for your onboarding team to confirm that the DNS TXT record has been configured correctly.
Complete the following procedure: Verify your custom domain name.

Next step

Prepare for live traffic with Operator Connect and Teams Phone Mobile

Ixxerja permezz ta’

Connect Azure Communications Gateway to Operator Connect or Teams Phone Mobile

Prerequisites

Enable Operator Connect or Teams Phone Mobile support

Add the Project Synergy application to your Azure tenant

Assign an Admin user to the Project Synergy application

Find the Application ID for your Azure Communication Gateway resource

Set up application roles for Azure Communications Gateway

Provide additional information to your onboarding team

Test your Operator Connect portal access

Add the Application IDs for Azure Communications Gateway to Operator Connect

Register your deployment's domain name in Microsoft Entra

Next step

Feedback

Riżorsi addizzjonali