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
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ To add the Project Synergy application:
97
97
98
98
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.
99
99
100
-
1. In the Azure portal, navigate to **Enterprise applications** using the left-hand side menu. Alternatively, you can search for it in the search bar; it's under the **Services** subheading.
100
+
1. 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.
101
101
1. Set the **Application type** filter to **All applications** using the drop-down menu.
102
102
1. Select **Apply**.
103
103
1. Search for **Project Synergy** using the search bar. The application should appear.
@@ -110,22 +110,21 @@ The user who sets up Azure Communications Gateway needs to have the Admin user r
110
110
111
111
## Find the Application ID for your Azure Communication Gateway resource
112
112
113
-
Each Azure Communications Gateway resource automatically receives a [system-assigned managed identity](../active-directory/managed-identities-azure-resources/overview.md), which Azure Communications Gateway uses to connect to the Operator Connect environment. You need to find the Object ID and Application ID of the managed identity, so that you can connect Azure Communications Gateway to the Operator Connect or Teams Phone Mobile environment in [Set up application roles for Azure Communications Gateway](#set-up-application-roles-for-azure-communications-gateway) and [Add the Application IDs for Azure Communications Gateway to Operator Connect](#add-the-application-ids-for-azure-communications-gateway-to-operator-connect).
113
+
Each Azure Communications Gateway resource automatically receives a [system-assigned managed identity](../active-directory/managed-identities-azure-resources/overview.md), 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](#set-up-application-roles-for-azure-communications-gateway) and [Add the Application IDs for Azure Communications Gateway to Operator Connect](#add-the-application-ids-for-azure-communications-gateway-to-operator-connect).
114
114
115
115
1. Sign in to the [Azure portal](https://azure.microsoft.com/).
116
-
1. In the search bar at the top of the page, search for your Communications Gateway resource.
117
-
1. Select your Communications Gateway resource.
118
-
1. Select **Identity**.
119
-
1. In **System assigned**, copy the **Object (principal) ID**.
120
-
1. Search for the value of **Object (principal) ID** with the search bar. 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.
116
+
1. If you don't already know the name of your Communications Gateway resource, search for **Communications Gateways** and note the name of the resource.
117
+
1. 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.
121
118
1. Select the enterprise application.
122
-
1. Check that the **Object ID** matches the **Object (principal) ID** value that you copied.
119
+
1. Check that the **Name** matches the name of your Communications Gateway resource.
123
120
1. Make a note of the **Application ID**.
124
121
125
122
## Set up application roles for Azure Communications Gateway
126
123
127
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 tenant](#add-the-project-synergy-application-to-your-azure-tenant).
128
125
126
+
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.
127
+
129
128
> [!IMPORTANT]
130
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).
131
130
@@ -154,6 +153,7 @@ Do the following steps in the tenant that contains your Project Synergy applicat
Copy file name to clipboardExpand all lines: articles/communications-gateway/manage-enterprise-operator-connect.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,13 @@ Azure Communications Gateway's Number Management Portal (preview) enables you to
16
16
> [!IMPORTANT]
17
17
> The Operator Connect and Teams Phone Mobile programs require that full API integration to your BSS is completed prior to launch in the Teams Admin Center. This can either be directly to the Operator Connect API or through the Azure Communications Gateway's Provisioning API (preview).
18
18
19
+
You can:
20
+
21
+
* Manage your agreement with an enterprise customer.
22
+
* Manage numbers for the enterprise.
23
+
* View civic addresses for an enterprise.
24
+
* Configure a custom header for a number.
25
+
19
26
## Prerequisites
20
27
21
28
Confirm that you have **Reader** access to the Azure Communications Gateway resource and appropriate permissions for the AzureCommunicationsGateway enterprise application:
@@ -60,22 +67,16 @@ Each number is automatically assigned to the Operator Connect or Teams Phone Mob
60
67
61
68
## Manage your agreement with an enterprise customer
62
69
63
-
When an enterprise customer uses the Teams Admin Center to request service, the Operator Connect APIs create a *consent*. The consent represents the relationship between you and the enterprise.
64
-
65
-
The Number Management Portal displays a consent as a *Request for Information* and allows you to update the status. Finding the Request for Information for an enterprise is also the easiest way to manage numbers for an enterprise.
70
+
When an enterprise customer uses the Teams Admin Center to request service, the Operator Connect APIs create a *consent*. The consent represents the relationship between you and the enterprise. The Number Management Portal displays a consent as a *Request for Information* and allows you to update the status.
66
71
67
72
1. From the overview page for your Communications Gateway resource, find the **Number Management (Preview)** section in the sidebar.
68
73
1. Select **Requests for Information**.
69
74
1. Find the enterprise that you want to manage. You can use the **Add filter** options to search for the enterprise.
70
75
1. If you need to change the status of the relationship, select the enterprise **Tenant ID** then select **Update relationship status**. Use the drop-down to select the new status. For example, if you're agreeing to provide service to a customer, set the status to **Agreement signed**. If you set the status to **Consent declined** or **Contract terminated**, you must provide a reason.
71
76
72
-
## Create an Account for the enterprise
77
+
If you're providing service to an enterprise for the first time, you must also create an *Account* for the enterprise.
73
78
74
-
You must create an *Account* for each enterprise that you manage with the Number Management Portal.
75
-
76
-
1. From the overview page for your Communications Gateway resource, find the **Number Management (Preview)** section in the sidebar.
77
-
1. Select **Accounts**.
78
-
1. Select **Create account**.
79
+
1. Select the enterprise, then select **Create account**.
79
80
1. Fill in the enterprise **Account name**.
80
81
1. Select the checkboxes for the services you want to enable for the enterprise.
81
82
1. Fill in any additional information requested under the **Communications Services Settings** heading.
Copy file name to clipboardExpand all lines: articles/communications-gateway/prepare-to-deploy.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,14 +34,13 @@ We strongly recommend that you have a support plan that includes technical suppo
34
34
35
35
## Choose the Azure tenant to use
36
36
37
-
We recommend that you use an existing Microsoft Entra tenant for Azure Communications Gateway, because using an existing tenant uses your existing identities for fully integrated authentication. If you need to manage identities separately from the rest of your organization, create a new dedicated tenant first.
37
+
We recommend that you use an existing Microsoft Entra tenant for Azure Communications Gateway, because using an existing tenant uses your existing identities for fully integrated authentication. If you need to manage identities separately from the rest of your organization, or to set up different permissions for the Number Management Portal for different Azure Communications Gateway resources, create a new dedicated tenant first.
38
38
39
39
The Operator Connect and Teams Phone Mobile environments inherit identities and configuration permissions from your Microsoft Entra tenant through a Microsoft application called Project Synergy. You must add this application to your Microsoft Entra tenant as part of [Connect Azure Communications Gateway to Operator Connect or Teams Phone Mobile](connect-operator-connect.md) (if your tenant does not already contain this application).
40
40
41
41
> [!IMPORTANT]
42
42
> For Operator Connect and Teams Phone Mobile, production deployments and lab deployments must connect to the same Microsoft Entra tenant. Microsoft Teams configuration for your tenant shows configuration for your lab deployments and production deployments together.
43
43
44
-
45
44
## Get access to Azure Communications Gateway for your Azure subscription
46
45
47
46
Access to Azure Communications Gateway is restricted. When you've completed the previous steps in this article:
Copy file name to clipboardExpand all lines: articles/communications-gateway/provision-user-roles.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,8 @@ Your staff might need different user roles, depending on the tasks they need to
36
36
| Monitor logs and metrics. |**Reader** access to the Azure Communications Gateway resource. |
37
37
| Use the Number Management Portal (preview) |**Reader** access to the Azure Communications Gateway resource and appropriate roles for the AzureCommunicationsGateway enterprise application: <!-- Must be kept in sync with step below for configuring and with manage-enterprise-operator-connect.md --><br>- To view configuration: **ProvisioningAPI.ReadUser**.<br>- To add or make changes to configuration: **ProvisioningAPI.ReadUser** and **ProvisioningAPI.WriteUser**.<br>- To remove configuration: **ProvisioningAPI.ReadUser** and **ProvisioningAPI.DeleteUser**.<br>- To view, add, make changes to, or remove configuration: **ProvisioningAPI.AdminUser**. |
38
38
39
+
> [!IMPORTANT]
40
+
> The roles that you assign for the Number Management Portal apply to all Azure Communications Gateway resources in the same tenant.
0 commit comments