Merge pull request #257366 from rcdun/lab

Add lab deployments to Azure Communications Gateway

Author: v-ccolin

articles/communications-gateway/configure-test-customer-teams-direct-routing.md

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to
-ms.date: 10/09/2023
+ms.date: 01/08/2024
 
 #CustomerIntent: As someone deploying Azure Communications Gateway, I want to test my deployment so that I can be sure that calls work.
 ---
@@ -35,21 +35,37 @@ You must be able to sign in to the Microsoft 365 admin center for your test cust
 
 ## Choose a DNS subdomain label to use to identify the customer
 
-Azure Communications Gateway's per-region domain names might be as follows, where the `<deployment_id>` subdomain is autogenerated and unique to the deployment:
+Azure Communications Gateway has per-region domain names. You need to set up subdomains of these domain names for your test customer.  Microsoft Phone System and Azure Communications Gateway use this subdomain to match calls to tenants.
 
-* `r1.<deployment_id>.commsgw.azure.com`
-* `r2.<deployment_id>.commsgw.azure.com`
+1. Choose a DNS label to identify the test customer.
+    * The label can be up to 10 characters in length and can only contain letters, numbers, underscores, and dashes.
+    * You must not use wildcard subdomains or subdomains with multiple labels.
+    * For example, you could allocate the label `test`.
+1. Use this label to create a subdomain of each per-region domain name for your Azure Communications Gateway.
+1. Make a note of the label you choose and the corresponding subdomains.
 
-Choose a DNS label to identify the test customer. The label can be up to 10 characters in length and can only contain letters, numbers, underscores, and dashes. You must not use wildcard subdomains or subdomains with multiple labels. For example, you could allocate the label `test`.
+> [!TIP]
+> To find your deployment's per-region domain names:
+> 1. Sign in to the [Azure portal](https://azure.microsoft.com/).
+> 1. Search for your Communications Gateway resource and select it.
+> 1. Check that you're on the **Overview** of your Azure Communications Gateway resource.
+> 1. Select **Properties**.
+> 1. In each **Service Location** section, find the **Hostname** field.
 
-You use this label to create a subdomain of each per-region domain name for your Azure Communications Gateway. Microsoft Phone System and Azure Communications Gateway use this subdomain to match calls to tenants.
+For example, your per-region domain names might be as follows, where the `<deployment_id>` subdomain is autogenerated and unique to the deployment:
 
-For example, the `test` label combined with the per-region domain names creates the following deployment-specific domain names:
+* `r1.<deployment_id>.commsgw.azure.com`
+* `r2.<deployment_id>.commsgw.azure.com`
+
+If you allocate the label `test`, this label combined with the per-region domain names creates the following domain names for your test customer:
 
 * `test.r1.<deployment_id>.commsgw.azure.com`
 * `test.r2.<deployment_id>.commsgw.azure.com`
 
-Make a note of the label you choose and the corresponding subdomains.
+
+
+> [!TIP]
+> Lab deployments have one per-region domain name. Your test customer therefore also only has one customer-specific per-region domain name.
 
 ## Start registering the subdomains in the customer tenant and get DNS TXT values
 
@@ -60,7 +76,7 @@ To route calls to a customer tenant, the customer tenant must be configured with
     1. Register the first customer-specific per-region domain name (for example `test.r1.<deployment_id>.commsgw.azure.com`).
     1. Start the verification process using TXT records.
     1. Note the TXT value that Microsoft 365 provides.
-1. Repeat the previous step for the second customer-specific per-region domain name.
+1. (Production deployments only) Repeat the previous step for the second customer-specific per-region domain name.
 
 > [!IMPORTANT]
 > Don't complete the verification process yet. You must carry out [Use Azure Communications Gateway's Provisioning API to configure the customer and generate DNS records](#use-azure-communications-gateways-provisioning-api-to-configure-the-customer-and-generate-dns-records) first.
@@ -83,7 +99,7 @@ When you have used Azure Communications Gateway to generate the DNS records for
 
 1. Sign into the Microsoft 365 admin center for the customer tenant as a Global Administrator.
 1. Select **Settings** > **Domains**.
-1. Finish verifying the two customer-specific per-region domain names by following [Add a subdomain to the customer tenant and verify it](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-subdomain-to-the-customer-tenant-and-verify-it).
+1. Finish verifying the customer-specific per-region domain names by following [Add a subdomain to the customer tenant and verify it](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-subdomain-to-the-customer-tenant-and-verify-it).
 
 ## Configure the customer tenant's call routing to use Azure Communications Gateway
 

articles/communications-gateway/connect-operator-connect.md

@@ -26,8 +26,7 @@ You must [deploy Azure Communications Gateway](deploy.md).
 
 You must have access to a user account with the Microsoft Entra Global Administrator role.
 
-You must allocate six "service verification" test numbers for each of Operator Connect and Teams Phone Mobile. These numbers are used by the Operator Connect and Teams Phone Mobile programs for continuous call testing.
-
+You must allocate "service verification" test numbers. These numbers are used by the Operator Connect and Teams Phone Mobile programs for continuous call testing. Production deployments need six numbers for each service. Lab deployments need three numbers for each service.
 - If you selected the service you're setting up as part of deploying Azure Communications Gateway, you've allocated numbers for the service already.
 - Otherwise, choose the phone numbers now (in E.164 format and including the country code) and names to identify them. We recommend names of the form OC1 and OC2 (for Operator Connect) and TPM1 and TPM2 (for Teams Phone Mobile).
 

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

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: integration
-ms.date: 11/22/2023
+ms.date: 01/08/2024
 ms.custom:
     - template-how-to-pattern
 ---
@@ -52,8 +52,10 @@ Microsoft Teams only sends traffic to domains that you confirm that you own. You
 1. Select your Communications Gateway resource. Check that you're on the **Overview** of your Azure Communications Gateway resource.
 1. Select **Properties**.
 1. Find the field named **Domain**. This name is your deployment's _base domain name_.
-1. In each **Service Location** section, find the **Hostname** field. This field provides the _per-region domain name_. Your deployment has two service regions and therefore two per-region domain names.
-1. Note down the base domain name and the per-region domain names. You'll need these values in the next steps.
+1. In each **Service Location** section, find the **Hostname** field. This field provides the _per-region domain name_.
+    - A production deployment has two service regions and therefore two per-region domain names.
+    - A lab deployment has one service region and therefore one per-region domain name.
+1. Note down the base domain name and the per-region domain name(s). You'll need these values in the next steps.
 
 ## Register the base domain name for Azure Communications Gateway in your tenant
 
@@ -103,9 +105,12 @@ To activate the base domain in Microsoft 365, you must have at least one user or
 
 ## Connect your tenant to Azure Communications Gateway
 
-You most configure your Microsoft 365 tenant with two SIP trunks to Azure Communications Gateway. Each trunk connects to one of the per-region domain names that you found in [Find your Azure Communication Gateway's domain names](#find-your-azure-communication-gateways-domain-names).
+You must configure your Microsoft 365 tenant with SIP trunks to Azure Communications Gateway. Each trunk connects to one of the per-region domain names that you found in [Find your Azure Communication Gateway's domain names](#find-your-azure-communication-gateways-domain-names).
 
-Follow [Connect your Session Border Controller (SBC) to Direct Routing](/microsoftteams/direct-routing-connect-the-sbc), using the following configuration settings.
+Use [Connect your Session Border Controller (SBC) to Direct Routing](/microsoftteams/direct-routing-connect-the-sbc) and the following configuration settings to set up the trunks.
+
+- For a production deployment, set up two trunks.
+- For a lab deployment, set up one trunk.
 
 | Teams Admin Center setting | PowerShell parameter | Value to use (Admin Center / PowerShell) |
 | -------------------------- | -------------------- | ------------ |

articles/communications-gateway/connectivity.md

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: concept-article
-ms.date: 11/20/2023
+ms.date: 01/08/2024
 
 #CustomerIntent: As someone planning a deployment, I want to learn about my options for connectivity, so that I can start deploying
 ---
@@ -32,12 +32,17 @@ The following table lists all the available connection types and whether they're
 |---------|---------|---------|---------|---------|
 | MAPS Voice |✅ |✅|✅|- Best media quality because of prioritization with Microsoft network<br>- No extra costs<br>- See [Internet peering for Peering Service Voice walkthrough](../internet-peering/walkthrough-communications-services-partner.md)|
 |ExpressRoute Microsoft Peering |✅|✅|✅|- Easy to deploy<br>- Extra cost<br>- Consult with your onboarding team and ensure that it's available in your region<br>- See [Using ExpressRoute for Microsoft PSTN services](/azure/expressroute/using-expressroute-for-microsoft-pstn)|
-|Public internet |❌|✅|✅|- No extra setup<br>- Not recommended for production|
+|Public internet |⚠️ Lab deployments only|✅|✅|- No extra setup<br>- Where available, not recommended for production |
 
-Set up your network as in the following diagram and configure it in accordance with any network connectivity specifications for your chosen communications services. Your network must have two sites with cross-connect functionality. For more information on the reliability design for Azure Communications Gateway, see [Reliability in Azure Communications Gateway](reliability-communications-gateway.md).
+> [!NOTE]
+> The Operator Connect and Teams Phone Mobile programs do not allow production deployments to use the public internet.
+
+Set up your network as in the following diagram and configure it in accordance with any network connectivity specifications for your chosen communications services. For production deployments, your network must have two sites with cross-connect functionality. For more information on the reliability design for Azure Communications Gateway, see [Reliability in Azure Communications Gateway](reliability-communications-gateway.md).
 
 :::image type="content" source="media/azure-communications-gateway-network.svg" alt-text="Network diagram showing Azure Communications Gateway deployed into two Azure regions within one Azure Geography. The Azure Communications Gateway resource in each region connects to a communications service and both operator sites. Azure Communications Gateway uses MAPS or Express Route as its peering service between Azure and an operators network." lightbox="media/azure-communications-gateway-network.svg":::
 
+Lab deployments have one Azure service region and must connect to one site in your network.
+
 ## IP addresses and domain names
 
 Azure Communications Gateway (ACG) deployments require multiple IP addresses and fully qualified domain names (FQDNs). The following diagram and table describe the IP addresses and FQDNs that you might need to know about.

articles/communications-gateway/deploy.md

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to 
-ms.date: 10/09/2023
+ms.date: 01/08/2024
 ---
 
 # Deploy Azure Communications Gateway
@@ -29,7 +29,8 @@ You must have completed [Prepare to deploy Azure Communications Gateway](prepare
  |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 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`).|**Call Handling: Emergency dial strings**|
@@ -41,10 +42,13 @@ You must have completed [Prepare to deploy Azure Communications Gateway](prepare
 
 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 regions to use for call traffic. |**Service Region One/Two: Region**|
- |The IPv4 address used by Azure Communications Gateway to contact your network from this region. |**Service Region One/Two: Operator IP address**|
+ |The Azure region to use for call traffic. |**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**|
 

articles/communications-gateway/get-started.md

@@ -26,7 +26,8 @@ This article summarizes the steps and documentation that you need.
 Read the following articles to learn about Azure Communications Gateway.
 
 - [Your network and Azure Communications Gateway](role-in-network.md), to learn how Azure Communications Gateway fits into your network.
-- [Onboarding with Included Benefits for Azure Communications Gateway](onboarding.md), to learn about onboarding to Operator Connect or Teams Phone Mobile and the support we can provide.
+- [Onboarding with Included Benefits for Azure Communications Gateway](onboarding.md), to learn about onboarding to your chosen communications services and the support we can provide.
+- [Lab Azure Communications Gateway overview](lab.md), to learn about when and how you could use a lab deployment.
 - [Connectivity for Azure Communications Gateway](connectivity.md) and [Reliability in Azure Communications Gateway](reliability-communications-gateway.md), to create a network design that includes Azure Communications Gateway.
 - [Overview of security for Azure Communications Gateway](security.md), to learn about how Azure Communications Gateway keeps customer data and your network secure.
 - [Provisioning API (preview) for Azure Communications Gateway](provisioning-platform.md), to learn about when you might need or want to integrate with the Provisioning API.
@@ -61,7 +62,7 @@ Use the following procedures to deploy Azure Communications Gateway and connect
 1. [Deploy Azure Communications Gateway](deploy.md) describes how to create your Azure Communications Gateway resource in the Azure portal and connect it to your networks.
 1. [Integrate with Azure Communications Gateway's Provisioning API (preview)](integrate-with-provisioning-api.md) describes how to integrate with the Provisioning API. Integrating with the API is:
     - Required for Microsoft Teams Direct Routing and Zoom Phone Cloud Peering.
-    - Recommended for Operator Connect and Teams Phone Mobile because it enables flow-through API-based provisioning of your customers both on Azure Communications Gateway and in the Operator Connect environment. This enables additional functionality to be provided by Azure Communications Gateway, such as injecting custom SIP headers, while also fulfilling the requirement from the the Operator Connect and Teams Phone Mobile programs for you to use APIs for provisioning customers in the Operator Connect environment. For more information, see [Provisioning and Operator Connect APIs](interoperability-operator-connect.md#provisioning-and-operator-connect-apis).
+    - Recommended for Operator Connect and Teams Phone Mobile because it enables flow-through API-based provisioning of your customers both on Azure Communications Gateway and in the Operator Connect environment. This enables additional functionality to be provided by Azure Communications Gateway, such as injecting custom SIP headers, while also fulfilling the requirement from the Operator Connect and Teams Phone Mobile programs for you to use APIs for provisioning customers in the Operator Connect environment. For more information, see [Provisioning and Operator Connect APIs](interoperability-operator-connect.md#provisioning-and-operator-connect-apis).
 
 ## Integrate with your chosen communications services
 

articles/communications-gateway/includes/communications-gateway-deployment-prerequisites.md

@@ -3,7 +3,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: include
-ms.date: 10/09/2023
+ms.date: 08/01/2024
 ---
 
 > [!IMPORTANT]
@@ -19,10 +19,10 @@ The following table describes how many numbers you need to allocate.
 
 Service | Numbers for integration testing | Service verification numbers |
 |---------|---------|---------|
-|Operator Connect | 1 (minimum)| 6 |
-|Teams Phone Mobile | 1 (minimum) | 6 |
+|Operator Connect | 1 (minimum) | - Production deployments: 6<br/> - Lab deployments: 3 |
+|Teams Phone Mobile | 1 (minimum) | - Production deployments: 6<br/> - Lab deployments: 3 |
 |Microsoft Teams Direct Routing | 1 (minimum) |  None (not applicable) |
-|Zoom Phone Cloud Peering | 1 (minimum) | - 6 (US and Canada)<br>- 2 (rest of world)|
+|Zoom Phone Cloud Peering | 1 (minimum) | - US and Canada: 6<br/>- Rest of world: 2 |
 
 > [!IMPORTANT]
 > Service verification numbers must be usable throughout the lifetime of your deployment.