Skip to content

Commit e725612

Browse files
committed
Explain why Communications Gateway needs a custom domain name
1 parent 984c4bd commit e725612

File tree

2 files changed

+9
-8
lines changed

2 files changed

+9
-8
lines changed

articles/communications-gateway/deploy.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ If you haven't filled in the configuration correctly, you'll see an error messag
4747

4848
Check your configuration and ensure it matches your requirements. If the configuration is correct, select **Create**.
4949

50-
You now need to wait for your resource to be provisioned and connected to the Teams environment. Upon completion your onboarding team will reach out to you and the Provisioning Status filed on the resource overview will show as "Complete". We recommend you check in periodically to see if your resource has been provisioned. This process can take up to two weeks as updating ACLs in the Azure and Teams environments is done on a periodic basis.
50+
You now need to wait for your resource to be provisioned and connected to the Microsoft Teams environment. When your resource has been provisioned and connected, your onboarding team will reach out to you and the Provisioning Status filed on the resource overview will show as "Complete". We recommend you check in periodically to see if your resource has been provisioned. This process can take up to two weeks, because updating ACLs in the Azure and Teams environments is done on a periodic basis.
5151

5252
Once your resource has been provisioned, a message will appear saying **Your deployment is complete**. Select **Go to resource group**, and then check that your resource group contains the correct Azure Communications Gateway resource.
5353

@@ -56,20 +56,21 @@ Once your resource has been provisioned, a message will appear saying **Your dep
5656
## 3. Complete the JSON onboarding file
5757

5858
Your onboarding team will require additional information to complete your Operator Connect onboarding. If you're being onboarded to Operator Connect/Teams Phone Mobile by Microsoft, the onboarding team will reach out to you.
59-
Wait for your onboarding team to confirm that the process is complete before testing your portal access.
59+
60+
Wait for your onboarding team to confirm that the onboarding process is complete before testing your portal access.
6061

6162
## 4. Test your portal access
6263

6364
Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and ensure you're able to sign in.
6465

65-
## 5. Register your Fully Qualified Domain Name (FQDN)
66+
## 5. Register your deployment's domain name in Active Directory
6667

67-
Your Azure Communications Gateway will require a custom domain name inside your Active Directory tenant. Follow this step to set up the custom domain name that Teams will use to recognize an Azure Communications Gateway that belongs to you.
68+
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.
6869

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

7475
## Next steps
7576

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ To configure MAPS, follow the instructions in [Azure Internet peering for Commun
172172
|The voice codecs to use between Azure Communications Gateway and your network. |**Instance details: Supported Codecs**|
173173
|The Unified Communications as a Service (UCaaS) platform(s) Azure Communications Gateway should support. These platforms are Teams Phone Mobile and Operator Connect Mobile. |**Instance details: Supported Voice Platforms**|
174174
|Whether your Azure Communications Gateway resource should handle emergency calls as standard calls or directly route them to the Emergency Services Routing Proxy (US only). |**Instance details: Emergency call handling**|
175-
|The scope at which Azure Communications Gateway's autogenerated domain name label is unique. Communications Gateway resources get assigned an autogenerated label that depends on the name of the resource. Selecting **Tenant** will give a resource with the same name in the same tenant but a different subscription the same label. Selecting **Subscription** will give a resource with the same name in the same subscription but a different resource group the same label. Selecting **Resource Group** will give a resource with the same name in the same resource group the same label. Selecting **No Re-use** means the label doesn't depend on the name, resource group, subscription or tenant. |**Instance details: Auto-generated Domain Name Scope**|
175+
|The scope at which Azure Communications Gateway's autogenerated domain name label is unique. Communications Gateway resources get assigned an autogenerated domain name label that depends on the name of the resource. You'll need to register the domain name later when you deploy Azure Communications Gateway. Selecting **Tenant** will give a resource with the same name in the same tenant but a different subscription the same label. Selecting **Subscription** will give a resource with the same name in the same subscription but a different resource group the same label. Selecting **Resource Group** will give a resource with the same name in the same resource group the same label. Selecting **No Re-use** means the label doesn't depend on the name, resource group, subscription or tenant. |**Instance details: Auto-generated Domain Name Scope**|
176176
|The number used in Teams Phone Mobile to access the Voicemail Interactive Voice Response (IVR) from native dialers.|**Instance details: Teams Voicemail Pilot Number**|
177177
|A list of dial strings used for emergency calling.|**Instance details: Emergency Dial Strings**|
178178
|Whether an on-premises Mobile Control Point is in use.|**Instance details: Enable on-premises MCP functionality**|

0 commit comments

Comments
 (0)