Add the Communications Gateway service principal in the portal after onboarding

Author: rcdun

articles/communications-gateway/deploy.md

@@ -62,15 +62,33 @@ Before your onboarding team can finish onboarding you to the Operator Connect an
 
 1. Wait for your onboarding team to provide you with a form to collect the additional information. 
 1. Complete the form and give it to your onboarding team.
-1. Wait for your onboarding team to confirm that the onboarding process is complete before testing your portal access.
+1. Wait for your onboarding team to confirm that the onboarding process is complete.
 
 If you don't already have an onboarding team, contact [email protected], providing your Azure subscription ID and contact details.
 
-## 4. Test your portal access
+## 4. Test your Operator Connect portal access
 
-Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and check that you're able to sign in.
+> [!IMPORTANT]
+> Before testing your Operator Connect portal access, wait for your onboarding team to confirm that the onboarding process is complete.
 
-## 5. Register your deployment's domain name in Active Directory
+Go to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and check that you're able to sign in.
+
+## 5. Add the application ID for Azure Communications Gateway to Operator Connect
+
+You must enable the Azure Communications Gateway application within the Operator Connect or Teams Phone Mobile environment. Enabling the application allows Azure Communications Gateway to use the roles that you set up in [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md#10-set-up-application-roles-for-azure-communications-gateway).
+
+To enable the Azure Communications Gateway application, add the application ID of the service principal representing Azure Communications Gateway to your Operator Connect or Teams Phone Mobile environment:
+
+1. Optionally, check the application ID of the service principal to confirm that you're adding the right application.
+    1. Search for `AzureCommunicationsGateway` with the search bar: it's under the **Azure Active Directory** subheading.
+    1. On the overview page, check that the value of **Object ID** is `8502a0ec-c76d-412f-836c-398018e2312b`.
+1. Log into the [Operator Connect portal](https://operatorconnect.microsoft.com/operator/configuration).
+1. Add a new **Application Id**, pasting in the following value. This value is the application ID for Azure Communications Gateway.
+    ```
+    8502a0ec-c76d-412f-836c-398018e2312b
+    ```
+
+## 6. Register your deployment's domain name in Active Directory
 
 Microsoft Teams only sends traffic to domains that you've confirmed 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 Active Directory 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.
 

articles/communications-gateway/prepare-to-deploy.md

@@ -129,11 +129,14 @@ If the **Microsoft.VoiceServices** resource provider isn't already registered in
 1. Search for the **Microsoft.VoiceServices** resource provider.
 1. Check if the resource provider is already marked as registered. If it isn't, choose the resource provider and select **Register**.
 
-## 10. Set up application roles for Azure Communications Gateway in your Project Synergy application
+## 10. 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 an AzureCommunicationsGateway service principal under the Project Synergy Enterprise Application. You created the Project Synergy application in [1. Add the Project Synergy application to your Azure tenancy](#1-add-the-project-synergy-application-to-your-azure-tenancy). Microsoft created the Azure Communications Gateway service principal for you when you followed [9. Register the Microsoft Voice Services resource provider](#9-register-the-microsoft-voice-services-resource-provider).
+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 an AzureCommunicationsGateway service principal under the Project Synergy Enterprise Application. You created the Project Synergy application in [1. Add the Project Synergy application to your Azure tenancy](#1-add-the-project-synergy-application-to-your-azure-tenancy). We created the Azure Communications Gateway service principal for you when you followed [9. Register the Microsoft Voice Services resource provider](#9-register-the-microsoft-voice-services-resource-provider).
 
-You need to do the following steps in the tenant that contains your Project Synergy application.
+> [!IMPORTANT]
+> Granting permissions has two parts: configuring the service principal with the appropriate roles (this step) and adding the ID of the service principal to the Operator Connect or Teams Phone Mobile environment. You'll add the service principal to the Operator Connect or Teams Phone Mobile environment later, as part of [deploying Azure Communications Gateway](deploy.md).
+
+Do the following steps in the tenant that contains your Project Synergy application.
 
 1. Sign in to the [Azure portal](https://ms.portal.azure.com/) as an Azure Active Directory Global Admin.
 1. Select **Azure Active Directory**.
@@ -180,21 +183,6 @@ You need to do the following steps in the tenant that contains your Project Syne
     }
     ```
 
-## 11. Add the application ID for Azure Communications Gateway to Operator Connect
-
-Before you can use the roles that you set up in [10. Set up application roles for Azure Communications Gateway in your Project Synergy application](#10-set-up-application-roles-for-azure-communications-gateway-in-your-project-synergy-application), you must enable the Azure Communications Gateway application within the Operator Connect or Teams Phone Mobile environment.
-
-To enable the Azure Communications Gateway application and the roles, add the application ID of the AzureCommunicationsGateway service principal to your Operator Connect or Teams Phone Mobile environment:
-
-1. Optionally, check the application ID of the service principal to confirm that you're adding the right application.
-    1. Search for `AzureCommunicationsGateway` with the search bar: it's under the **Azure Active Directory** subheading.
-    1. On the overview page, check that the value of **Object ID** is `8502a0ec-c76d-412f-836c-398018e2312b`.
-1. Log into the [Operator Connect Number Management Portal](https://operatorconnect.microsoft.com/operator/configuration).
-1. Add a new **Application Id**, pasting in the following value. This value is the application ID for Azure Communications Gateway.
-    ```
-    8502a0ec-c76d-412f-836c-398018e2312b
-    ```
-
 ## Next steps
 
 - [Create an Azure Communications Gateway resource](deploy.md)