Skip to content

Commit a1e39da

Browse files
Merge pull request #263646 from rcdun/1169130_operator_connect_ownership
1169130 Document OC/TPM configuration that customers must not change
2 parents 7cf8570 + 5a109ae commit a1e39da

5 files changed

+28
-8
lines changed

articles/communications-gateway/connect-operator-connect.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ If you want to set up Teams Phone Mobile and you didn't select it when you deplo
4242
## Enable Operator Connect or Teams Phone Mobile support
4343

4444
> [!NOTE]
45-
> If you selected Operator Connect or Teams Phone Mobile when you [deployed Azure Communications Gateway](deploy.md), skip this step and go to [Add the Project Synergy application to your Azure tenancy](#add-the-project-synergy-application-to-your-azure-tenancy).
45+
> If you selected Operator Connect or Teams Phone Mobile when you [deployed Azure Communications Gateway](deploy.md), skip this step and go to [Add the Project Synergy application to your Azure tenant](#add-the-project-synergy-application-to-your-azure-tenant).
4646
4747
1. Sign in to the [Azure portal](https://azure.microsoft.com/).
4848
1. In the search bar at the top of the page, search for your Communications Gateway resource and select it.
@@ -55,7 +55,7 @@ If you want to set up Teams Phone Mobile and you didn't select it when you deplo
5555
> 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](prepare-for-live-traffic-operator-connect.md).
5656
1. 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.
5757

58-
## Add the Project Synergy application to your Azure tenancy
58+
## Add the Project Synergy application to your Azure tenant
5959

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

@@ -102,7 +102,9 @@ The user who sets up Azure Communications Gateway needs to have the Admin user r
102102
1. Select your **Project Synergy** application.
103103
1. Select **Users and groups** from the left hand side menu.
104104
1. Select **Add user/group**.
105-
1. Specify the user you want to use for setting up Azure Communications Gateway and give them the **Admin** role.
105+
1. Specify the user who should set up Azure Communications Gateway and give them the **Admin** role.
106+
107+
[!INCLUDE [communications-gateway-oc-configuration-ownership](includes/communications-gateway-oc-configuration-ownership.md)]
106108
107109
## Find the Object ID and Application ID for your Azure Communication Gateway resource
108110
@@ -121,7 +123,7 @@ Each Azure Communications Gateway resource automatically receives a [system-assi
121123
122124
## Set up application roles for Azure Communications Gateway
123125
124-
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 tenancy](#add-the-project-synergy-application-to-your-azure-tenancy).
126+
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](#add-the-project-synergy-application-to-your-azure-tenant).
125127
126128
> [!IMPORTANT]
127129
> 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](#add-the-application-ids-for-azure-communications-gateway-to-operator-connect).
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
author: rcdun
3+
ms.author: rdunstan
4+
ms.service: communications-gateway
5+
ms.topic: include
6+
ms.date: 01/19/2024
7+
---
8+
9+
> [!CAUTION]
10+
> 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).
11+
>
12+
> - Calling Profiles with a `CommsGw` **Suffix** in the configuration portal or **NameSuffix** on the Operator Connect APIs
13+
> - Trunks with FQDNs ending with `.commsgw.azure.com`
14+
>
15+
> We manage this configuration for you. Editing this configuration is likely to cause issues with your Azure Communications Gateway service.

articles/communications-gateway/interoperability-operator-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: rcdun
55
ms.author: rdunstan
66
ms.service: communications-gateway
77
ms.topic: conceptual
8-
ms.date: 09/01/2023
8+
ms.date: 01/31/2024
99
ms.custom: template-concept
1010
---
1111

articles/communications-gateway/manage-enterprise-operator-connect.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ If you're uploading new numbers for an enterprise customer:
3636

3737
|Information for each number |Notes |
3838
|---------|---------|
39-
|Calling profile |One of the Calling Profiles created by Microsoft for you.|
39+
|Calling profile |One of the `CommsGw` Calling Profiles we created for you.|
4040
|Intended usage | Individuals (calling users), applications or conference calls.|
4141
|Capabilities |Which types of call to allow (for example, inbound calls or outbound calls).|
4242
|Civic address | A physical location for emergency calls. The enterprise must have configured this address in the Teams Admin Center. Only required for individuals (calling users) and only if you don't allow the enterprise to update the address.|
@@ -56,6 +56,7 @@ Numbers
5656
+441632960004
5757
```
5858

59+
[!INCLUDE [communications-gateway-oc-configuration-ownership](includes/communications-gateway-oc-configuration-ownership.md)]
5960

6061
## Go to your Communications Gateway resource
6162

articles/communications-gateway/prepare-for-live-traffic-operator-connect.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,11 @@ In this article, you learn about the steps that you and your onboarding team mus
3636

3737
|Configuration portal |Required permissions |
3838
|---------|---------|
39-
|[Operator Connect portal](https://operatorconnect.microsoft.com/) | `Admin` role or `PartnerSettings.Read` and `NumberManagement.Write` roles (configured on the Project Synergy enterprise application that you set up when [you connected to Operator Connect or Teams Phone Mobile](connect-operator-connect.md#add-the-project-synergy-application-to-your-azure-tenancy))|
39+
|[Operator Connect portal](https://operatorconnect.microsoft.com/) | `Admin` role or `PartnerSettings.Read` and `NumberManagement.Write` roles (configured on the Project Synergy enterprise application that you set up when [you connected to Operator Connect or Teams Phone Mobile](connect-operator-connect.md#add-the-project-synergy-application-to-your-azure-tenant))|
4040
|[Teams Admin Center](https://admin.teams.microsoft.com/) for your test tenant |User management|
4141

42+
[!INCLUDE [communications-gateway-oc-configuration-ownership](includes/communications-gateway-oc-configuration-ownership.md)]
43+
4244
## Methods
4345

4446
In some parts of this article, the steps you must take depend on whether your deployment includes the Number Management Portal. This article provides instructions for both types of deployment. Choose the appropriate instructions.
@@ -61,7 +63,7 @@ Integration testing requires setting up your test tenant for Operator Connect or
6163
> [!IMPORTANT]
6264
> Do not assign the service verification numbers to test users. Your onboarding team arranges configuration of your service verification numbers.
6365
64-
1. Ask your onboarding team for the name of the Calling Profile that you must use for these test numbers. The name typically has the suffix `commsgw`. This Calling Profile was created for you during the Azure Communications Gateway deployment process.
66+
1. Ask your onboarding team for the name of the Calling Profile that you must use for these test numbers. The name typically has the suffix `CommsGw`. We created this Calling Profile for you during the Azure Communications Gateway deployment process.
6567
1. In your test tenant, request service from your company.
6668
1. Sign in to the [Teams Admin Center](https://admin.teams.microsoft.com/) for your test tenant.
6769
1. Select **Voice** > **Operators**.

0 commit comments

Comments
 (0)