Merge pull request #273068 from rcdun/acg_move_information_to_collect

1521897 Move 'Collect information' steps for ACG into prepare-to-depl…

Author: v-dirichards

articles/communications-gateway/deploy.md

@@ -14,112 +14,13 @@ This article guides you through planning for and creating an Azure Communication
 
 ## Prerequisites
 
-You must have completed [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md).
+Complete [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md). Ensure you have access to all the information that you collected by following that procedure.
 
 [!INCLUDE [communications-gateway-tsp-restriction](includes/communications-gateway-tsp-restriction.md)]
 
 [!INCLUDE [communications-gateway-deployment-prerequisites](includes/communications-gateway-deployment-prerequisites.md)]
 
-## Collect basic information for deploying an Azure Communications Gateway
-
- Collect all of the values in the following table for the Azure Communications Gateway resource.
-
-|**Value**|**Field name(s) in Azure portal**|
- |---------|---------|
- |The name of the Azure subscription to use to create an Azure Communications Gateway resource. You must use the same subscription for all resources in your Azure Communications Gateway deployment. |**Project details: Subscription**|
- |The Azure resource group in which to create the Azure Communications Gateway resource. |**Project details: Resource group**|
- |The name for the deployment. This name can contain alphanumeric characters and `-`. It must be 3-24 characters long. |**Instance details: Name**|
- |The management Azure region: the region in which your monitoring and billing data is processed. We recommend that you select a region near or colocated with the two regions for handling call traffic. |**Instance details: Region** |
- |The type of deployment. Choose from **Standard** (for production) or **Lab**. |**Instance details: SKU** |
- |The voice codecs to use between Azure Communications Gateway and your network. We recommend that you only specify any codecs if you have a strong reason to restrict codecs (for example, licensing of specific codecs) and you can't configure your network or endpoints not to offer specific codecs. Restricting codecs can reduce the overall voice quality due to lower-fidelity codecs being selected. |**Call Handling: Supported codecs**|
- |Whether your Azure Communications Gateway resource should handle emergency calls as standard calls or directly route them to the Emergency Routing Service Provider (US only; only for Operator Connect or Teams Phone Mobile). |**Call Handling: Emergency call handling**|
- |A comma-separated list of dial strings used for emergency calls. For Microsoft Teams, specify dial strings as the standard emergency number (for example `999`). For Zoom, specify dial strings in the format `+<country-code><emergency-number>` (for example `+44999`). (Only for Operator Connect, Teams Phone Mobile and Zoom Phone Cloud Peering).|**Call Handling: Emergency dial strings**|
- |Whether to use an autogenerated `*.commsgw.azure.com` domain name or to use a subdomain of your own domain by delegating it to Azure Communications Gateway. Delegated domains are limited to 34 characters. For more information on this choice, see [the guidance on creating a network design](prepare-to-deploy.md#create-a-network-design). | **DNS: Domain name options** |
- |(Required if you choose an autogenerated domain) The scope at which the autogenerated domain name label for Azure Communications Gateway is unique. Communications Gateway resources are assigned an autogenerated domain name label that depends on the name of the resource.  Selecting **Tenant** gives a resource with the same name in the same tenant but a different subscription the same label. Selecting **Subscription** gives a resource with the same name in the same subscription but a different resource group the same label. Selecting **Resource Group** gives 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. |**DNS: Auto-generated Domain Name Scope**|
- | (Required if you choose a delegated domain) The domain to delegate to this Azure Communications Gateway deployment | **DNS: DNS domain name** |
-
-## Collect configuration values for service regions
-
-Collect all of the values in the following table for both service regions in which you want to deploy Azure Communications Gateway.
-
-> [!NOTE]
-> Lab deployments have one Azure region and connect to one site in your network.
-
- |**Value**|**Field name(s) in Azure portal**|
- |---------|---------|
- |The Azure region to use for call traffic.<br><br>If you are enabling Azure Operator Call Protection Preview there are restrictions on where your Azure resources can be deployed; see [Choosing Management and Service Regions](reliability-communications-gateway.md#choosing-management-and-service-regions) |**Service Region One/Two: Region**|
- |The IPv4 address belonging to your network that Azure Communications Gateway should use to contact your network from this region. |**Service Region One/Two: Operator IP address**|
- |The set of IP addresses/ranges that are permitted as sources for signaling traffic from your network. Provide an IPv4 address range using CIDR notation (for example, 192.0.2.0/24) or an IPv4 address (for example, 192.0.2.0). You can also provide a comma-separated list of IPv4 addresses and/or address ranges.|**Service Region One/Two: Allowed Signaling Source IP Addresses/CIDR Ranges**|
- |The set of IP addresses/ranges that are permitted as sources for media traffic from your network. Provide an IPv4 address range using CIDR notation (for example, 192.0.2.0/24) or an IPv4 address (for example, 192.0.2.0). You can also provide a comma-separated list of IPv4 addresses and/or address ranges.|**Service Region One/Two: Allowed Media Source IP Address/CIDR Ranges**|
-
-## Collect configuration values for each communications service
-
-Collect the values for the communications services that you're planning to support.
-
-> [!IMPORTANT]
-> Some options apply to multiple services, as shown by **Options common to multiple communications services** in the following tables. You must choose configuration that is suitable for all the services that you plan to support.
-
-For Microsoft Teams Direct Routing:
-
-|**Value**|**Field name(s) in Azure portal**|
-|---------|---------|
-| IP addresses or address ranges (in CIDR format) in your network that should be allowed to connect to Azure Communications Gateway's Provisioning API, in a comma-separated list. Use of the Provisioning API is required to provision numbers for Direct Routing. | **Options common to multiple communications services: Allowed source IP addresses/CIDR ranges for connecting to the Communications Gateway Provisioning Platform** |
-| Whether to add a custom SIP header to messages entering your network by using Azure Communications Gateway's Provisioning API | **Options common to multiple communications services: Add custom SIP header** |
-| (Only if you choose to add a custom SIP header) The name of any custom SIP header | **Options common to multiple communications services: Custom SIP header name** |
-
-For Operator Connect:
-
-|**Value**|**Field name(s) in Azure portal**|
-|---------|---------|
-| Whether to add a custom SIP header to messages entering your network by using Azure Communications Gateway's Provisioning API | **Options common to multiple communications services: Add custom SIP header** |
-| (Only if you choose to add a custom SIP header) The name of any custom SIP header | **Options common to multiple communications services: Custom SIP header name** |
-| (Only if you choose to add a custom SIP header) IP addresses or address ranges (in CIDR format) in your network that should be allowed to connect to the Provisioning API, in a comma-separated list. | **Options common to multiple communications services: Allowed source IP addresses/CIDR ranges for connecting to the Communications Gateway Provisioning Platform** |
-
-For Teams Phone Mobile:
-
-|**Value**|**Field name(s) in Azure portal**|
-|---------|---------|
-|The number used in Teams Phone Mobile to access the Voicemail Interactive Voice Response (IVR) from native dialers.|**Teams Phone Mobile: Teams voicemail pilot number**|
-| How you plan to use Mobile Control Point (MCP) to route Teams Phone Mobile calls to Microsoft Phone System. Choose from **Integrated** (to deploy MCP in Azure Communications Gateway), **On-premises** (to use an existing on-premises MCP) or **None** (if you'll use another method to route calls). |**Teams Phone Mobile: MCP**|
-
-For Zoom Phone Cloud Peering:
-
-|**Value**|**Field name(s) in Azure portal**|
-|---------|---------|
-| The Zoom region to connect to | **Zoom: Zoom region** |
-| IP addresses or address ranges (in CIDR format) in your network that should be allowed to connect to Azure Communications Gateway's Provisioning API, in a comma-separated list. Use of the Provisioning API is required to provision numbers for Zoom Phone Cloud Peering. | **Options common to multiple communications services: Allowed source IP addresses/CIDR ranges for connecting to the Communications Gateway Provisioning Platform** |
-| Whether to add a custom SIP header to messages entering your network by using Azure Communications Gateway's Provisioning API | **Options common to multiple communications services: Add custom SIP header** |
-| (Only if you choose to add a custom SIP header) The name of any custom SIP header | **Options common to multiple communications services: Custom SIP header name** |
-
-There are no configuration options required for Azure Operator Call Protection Preview.
-
-## Collect values for service verification numbers
-
-Collect all of the values in the following table for all the service verification numbers required by Azure Communications Gateway.
-
-For Operator Connect and Teams Phone Mobile:
-
-|**Value**|**Field name(s) in Azure portal**|
-|---------|---------|
-|A name for the test line.  We recommend names of the form OC1 and OC2 (for Operator Connect) and TPM1 and TPM2 (for Teams Phone Mobile). |**Name**|
-|The phone number for the test line, in E.164 format and including the country code. |**Phone Number**|
-|The purpose of the test line (always **Automated**).|**Testing purpose**|
-
-For Zoom Phone Cloud Peering:
-
-|**Value**|**Field name(s) in Azure portal**|
-|---------|---------|
-|The phone number for the test line, in E.164 format and including the country code. |**Phone Number**|
-
-Microsoft Teams Direct Routing and Azure Operator Call Protection Preview don't require service verification numbers.
-
-## Decide if you want tags
-
-Resource naming and tagging is useful for resource management. It enables your organization to locate and keep track of resources associated with specific teams or workloads and also enables you to more accurately track the consumption of cloud resources by business area and team.
-
-If you believe tagging would be useful for your organization, design your naming and tagging conventions following the information in the [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/decision-guides/resource-tagging/).
-
-## Start creating an Azure Communications Gateway resource
+## Create an Azure Communications Gateway resource
 
 Use the Azure portal to create an Azure Communications Gateway resource.
 
@@ -132,10 +33,10 @@ Use the Azure portal to create an Azure Communications Gateway resource.
 
     :::image type="content" source="media/deploy/create.png" alt-text="Screenshot of the Azure portal. Shows the existing Azure Communications Gateway. A Create button allows you to create more Azure Communications Gateways.":::
 
-1. Use the information you collected in [Collect basic information for deploying an Azure Communications Gateway](#collect-basic-information-for-deploying-an-azure-communications-gateway) to fill out the fields in the **Basics** configuration tab and then select **Next: Service Regions**.
-1. Use the information you collected in [Collect configuration values for service regions](#collect-configuration-values-for-service-regions) to fill out the fields in the **Service Regions** tab and then select **Next: Communications Services**.
-1. Select the communications services that you want to support in the **Communications Services** configuration tab, use the information that you collected in [Collect configuration values for each communications service](#collect-configuration-values-for-each-communications-service) to fill out the fields, and then select **Next: Test Lines**.
-1. Use the information that you collected in [Collect values for service verification numbers](#collect-values-for-service-verification-numbers) to fill out the fields in the **Test Lines** configuration tab and then select **Next: Tags**.
+1. Use the information you collected in [Collect basic information for deploying an Azure Communications Gateway](prepare-to-deploy.md#collect-basic-information-for-deploying-an-azure-communications-gateway) to fill out the fields in the **Basics** configuration tab and then select **Next: Service Regions**.
+1. Use the information you collected in [Collect configuration values for service regions](prepare-to-deploy.md#collect-configuration-values-for-service-regions) to fill out the fields in the **Service Regions** tab and then select **Next: Communications Services**.
+1. Select the communications services that you want to support in the **Communications Services** configuration tab, use the information that you collected in [Collect configuration values for each communications service](prepare-to-deploy.md#collect-configuration-values-for-each-communications-service) to fill out the fields, and then select **Next: Test Lines**.
+1. Use the information that you collected in [Collect values for service verification numbers](prepare-to-deploy.md#collect-values-for-service-verification-numbers) to fill out the fields in the **Test Lines** configuration tab and then select **Next: Tags**.
     - Don't configure numbers for integration testing.
     - Microsoft Teams Direct Routing and Azure Operator Call Protection Preview don't require service verification numbers.
 1. (Optional) Configure tags for your Azure Communications Gateway resource: enter a **Name** and **Value** for each tag you want to create.
@@ -154,7 +55,7 @@ Check your configuration and ensure it matches your requirements. If the configu
 Once your resource has been provisioned, a message appears saying **Your deployment is complete**. Select **Go to resource group**, and then check that your resource group contains the correct Azure Communications Gateway resource.
 
 > [!NOTE]
-> You will not be able to make calls immediately. You need to complete the remaining steps in this guide before your resource is ready to handle traffic.
+> You can't make calls immediately. You need to complete the remaining steps in this guide before your resource is ready to handle traffic.
 
 :::image type="content" source="media/deploy/go-to-resource-group.png" alt-text="Screenshot of the Create an Azure Communications Gateway portal, showing a completed deployment screen.":::
 

articles/communications-gateway/emergency-calls-zoom.md

@@ -26,7 +26,7 @@ Azure Communications Gateway routes emergency calls from Zoom clients to your ne
 You must:
 
 1. Identify the combinations of country codes and emergency short codes that you need to support.
-2. Specify these combinations (prefixed with `+`) when you [deploy Azure Communications Gateway](deploy.md#collect-basic-information-for-deploying-an-azure-communications-gateway), or by editing your existing configuration.
+2. Specify these combinations (prefixed with `+`) when you [deploy Azure Communications Gateway](deploy.md#create-an-azure-communications-gateway-resource), or by editing your existing configuration.
 3. Configure your network to treat calls to these numbers as emergency calls.
 
 If your network can't route emergency calls in the format  `+<country-code><emergency-short-code>`, contact your onboarding team or raise a support request to discuss your requirements for number conversion.

articles/communications-gateway/integrate-with-provisioning-api.md

@@ -33,7 +33,7 @@ Whether you integrate with the Provisioning API depends on your chosen communica
 
 You must have completed [Deploy Azure Communications Gateway](deploy.md).
 
-You must have access to a machine with an IP address that is permitted to access the Provisioning API (preview). This allowlist of IP addresses (or ranges) was configured as part of [deploying Azure Communications Gateway](deploy.md#collect-configuration-values-for-each-communications-service).
+You must have access to a machine with an IP address that is permitted to access the Provisioning API (preview). This allowlist of IP addresses (or ranges) was configured as part of [deploying Azure Communications Gateway](deploy.md#create-an-azure-communications-gateway-resource).
 
 ## Learn about the Provisioning API (preview) and plan your BSS client changes
 

articles/communications-gateway/interoperability-teams-direct-routing.md

@@ -87,7 +87,7 @@ The following diagram shows the call flow for an INVITE from a number that is as
 :::image-end:::
 
 > [!NOTE]
-> The name of the custom header must be configured as part of [deploying Azure Communications Gateway](deploy.md#collect-configuration-values-for-each-communications-service). The name is the same for all messages. In this example, the name of the custom header is `X-MS-Operator-Content`.
+> The name of the custom header must be configured as part of [deploying Azure Communications Gateway](deploy.md#create-an-azure-communications-gateway-resource). The name is the same for all messages. In this example, the name of the custom header is `X-MS-Operator-Content`.
 
 The following diagram shows the call flow for an INVITE from a number that isn't assigned to a customer. Azure Communications Gateway rejects the call with a 403.