You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communications-gateway/connect-operator-connect.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ If you want to set up Teams Phone Mobile and you didn't select it when you deplo
42
42
## Enable Operator Connect or Teams Phone Mobile support
43
43
44
44
> [!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).
46
46
47
47
1. Sign in to the [Azure portal](https://azure.microsoft.com/).
48
48
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
55
55
> 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).
56
56
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.
57
57
58
-
## Add the Project Synergy application to your Azure tenancy
58
+
## Add the Project Synergy application to your Azure tenant
59
59
60
60
Before starting this step, check that the **Provisioning Status** field for your resource is "Complete".
61
61
@@ -102,7 +102,9 @@ The user who sets up Azure Communications Gateway needs to have the Admin user r
102
102
1. Select your **Project Synergy** application.
103
103
1. Select **Users and groups** from the left hand side menu.
104
104
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.
## Find the Object ID and Application ID for your Azure Communication Gateway resource
108
110
@@ -121,7 +123,7 @@ Each Azure Communications Gateway resource automatically receives a [system-assi
121
123
122
124
## Set up application roles for Azure Communications Gateway
123
125
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).
125
127
126
128
> [!IMPORTANT]
127
129
> 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).
> 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.
Copy file name to clipboardExpand all lines: articles/communications-gateway/manage-enterprise-operator-connect.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ If you're uploading new numbers for an enterprise customer:
36
36
37
37
|Information for each number |Notes |
38
38
|---------|---------|
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.|
40
40
|Intended usage | Individuals (calling users), applications or conference calls.|
41
41
|Capabilities |Which types of call to allow (for example, inbound calls or outbound calls).|
42
42
|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.|
Copy file name to clipboardExpand all lines: articles/communications-gateway/prepare-for-live-traffic-operator-connect.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,9 +36,11 @@ In this article, you learn about the steps that you and your onboarding team mus
36
36
37
37
|Configuration portal |Required permissions |
38
38
|---------|---------|
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))|
40
40
|[Teams Admin Center](https://admin.teams.microsoft.com/) for your test tenant |User management|
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
61
63
> [!IMPORTANT]
62
64
> Do not assign the service verification numbers to test users. Your onboarding team arranges configuration of your service verification numbers.
63
65
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.
65
67
1. In your test tenant, request service from your company.
66
68
1. Sign in to the [Teams Admin Center](https://admin.teams.microsoft.com/) for your test tenant.
0 commit comments