Skip to content

Commit 39feba9

Browse files
committed
Improve description of collection of additional information during onboarding
1 parent b8721c8 commit 39feba9

File tree

1 file changed

+12
-5
lines changed

1 file changed

+12
-5
lines changed

articles/communications-gateway/deploy.md

Lines changed: 12 additions & 5 deletions
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: how-to
8-
ms.date: 12/16/2022
8+
ms.date: 03/16/2023
99
---
1010

1111
# Deploy Azure Communications Gateway
@@ -55,19 +55,26 @@ Once your resource has been provisioned, a message appears saying **Your deploym
5555

5656
## 3. Complete the JSON onboarding file
5757

58-
Your onboarding team needs more information to complete your Operator Connect onboarding. If you're being onboarded to Operator Connect or Teams Phone Mobile by Microsoft, the onboarding team will contact you. Fill in the JSON onboarding file and give it to your onboarding team.
58+
> [!NOTE]
59+
>This step is required to set you up as an Operator in the Teams Phone Mobile (TPM) and Operator Connect (OC) environments. Skip this step if you have already onboarded to TPM or OC.
5960
60-
Wait for your onboarding team to confirm that the onboarding process is complete before testing your portal access.
61+
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.
62+
63+
1. Wait for your onboarding team to provide you with a form to collect the additional information.
64+
1. Complete the form and give it to your onboarding team.
65+
1. Wait for your onboarding team to confirm that the onboarding process is complete before testing your portal access.
66+
67+
If you don't already have an onboarding team, contact [email protected], providing your Azure subscription ID and contact details.
6168

6269
## 4. Test your portal access
6370

64-
Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and ensure you're able to sign in.
71+
Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and check that you're able to sign in.
6572

6673
## 5. Register your deployment's domain name in Active Directory
6774

6875
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.
6976

70-
1. Navigate to your Azure Communications Gateway resource and select **Properties**. You'll see a field named **Domain name**. This name is your deployment's domain name.
77+
1. Navigate to your Azure Communications Gateway resource and select **Properties**. Find the field named **Domain name**. This name is your deployment's domain name.
7178
1. Complete the following procedure: [Add your custom domain name to Azure AD](../active-directory/fundamentals/add-custom-domain.md#add-your-custom-domain-name-to-azure-ad).
7279
1. 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.
7380
1. Complete the following procedure: [Verify your custom domain name](../active-directory/fundamentals/add-custom-domain.md#verify-your-custom-domain-name).

0 commit comments

Comments
 (0)