Merge pull request #236778 from robswain/regions

v-ccolin · web-flow · commit 92bd3c2a88cf · 2023-05-05T11:27:08.000+01:00
update specific region references to generic links
diff --git a/articles/private-5g-core/collect-required-information-for-a-site.md b/articles/private-5g-core/collect-required-information-for-a-site.md
@@ -37,7 +37,7 @@ Collect all the values in the following table for the mobile network site resour
    |The name for the site.           |**Instance details: Name**|
    |The region in which you deployed the private mobile network.                         |**Instance details: Region**|
    |The packet core in which to create the mobile network site resource.                         |**Instance details: Packet core name**|
-   |The [region code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*. </br></br>You only need to collect this value if you're going to create your site using an ARM template.                         |Not applicable.|
+   |The [region code name](region-code-names.md) of the region in which you deployed the private mobile network.</br></br>You only need to collect this value if you're going to create your site using an ARM template.                         |Not applicable.|
    |The mobile network resource representing the private mobile network to which you’re adding the site. </br></br>You only need to collect this value if you're going to create your site using an ARM template.                         |Not applicable.|
    |The service plan for the site that you are creating. See [Azure Private 5G Core pricing](https://azure.microsoft.com/pricing/details/private-5g-core/). |**Instance details: Service plan**|
 
diff --git a/articles/private-5g-core/collect-required-information-for-private-mobile-network.md b/articles/private-5g-core/collect-required-information-for-private-mobile-network.md
@@ -30,7 +30,7 @@ Collect all of the following values for the mobile network resource that will re
    |The Azure subscription to use to deploy the mobile network resource. You must use the same subscription for all resources in your private mobile network deployment. You identified this subscription in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).                 |**Project details: Subscription**
    |The Azure resource group to use to deploy the mobile network resource. You should use a new resource group for this resource. It's useful to include the purpose of this resource group in its name for future identification (for example, *contoso-pmn-rg*). </br></br> Note: We recommend that this resource group is also used when [Collecting the required information for a site](collect-required-information-for-a-site.md).              |**Project details: Resource group**|
    |The name for the private mobile network.           |**Instance details: Mobile network name**|
-   |The region in which you're deploying the private mobile network. This can be the East US or the West Europe region.                           |**Instance details: Region**|
+   |The region in which you're deploying the private mobile network.                           |**Instance details: Region**|
    |The mobile country code for the private mobile network. If you do not already have this, contact your national telecom regulator. <br><br> **Note:** For internal private networks you can configure the MCC to 001 (a test value) or 999.   |**Network configuration: Mobile country code (MCC)**|
    |The mobile network code for the private mobile network. If you do not already have this, contact your national telecom regulator. <br><br> **Note:** For internal private networks you can configure the MNC to 01 (a test value), 99 or 999.    |**Network configuration: Mobile network code (MNC)**|
 
diff --git a/articles/private-5g-core/commission-cluster.md b/articles/private-5g-core/commission-cluster.md
@@ -268,7 +268,7 @@ Collect each of the values in the table below.
 |The ID of the Azure subscription in which the Azure resources are deployed. |**SUBSCRIPTION_ID**|
 |The name of the resource group in which the AKS cluster is deployed. This can be found by using the **Manage** button in the **Azure Kubernetes Service** pane of the Azure portal. |**RESOURCE_GROUP_NAME**|
 |The name of the AKS cluster resource. This can be found by using the **Manage** button in the **Azure Kubernetes Service** pane of the Azure portal. |**RESOURCE_NAME**|
-|The region in which the Azure resources are deployed. This must match the region into which the mobile network will be deployed, which must be one of the regions supported by AP5GC: **EastUS** or **WestEurope**.</br></br>This value must be the [region's code name](region-code-names.md); see [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/) for a list of supported regions. |**LOCATION**|
+|The region in which the Azure resources are deployed. This must match the region into which the mobile network will be deployed, which must be one of the regions supported by AP5GC.</br></br>This value must be the [region's code name](region-code-names.md). |**LOCATION**|
 |The name of the **Custom location** resource to be created for the AKS cluster. </br></br>This value must start and end with alphanumeric characters, and must contain only alphanumeric characters, `-` or `.`. |**CUSTOM_LOCATION**|
 
 ## Install Kubernetes extensions
@@ -357,7 +357,7 @@ You should see the new **Custom location** visible as a resource in the Azure po
 
 If you have made an error in the Azure Stack Edge configuration, you can use the portal to remove the AKS cluster (see [Deploy Azure Kubernetes service on Azure Stack Edge](/azure/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge)). You can then modify the settings via the local UI.  
 
-Alternatively, you can perform a full reset using the **Device Reset** blade in the local UI (see [Azure Stack Edge device reset and reactivation](/azure/databox-online/azure-stack-edge-reset-reactivate-device)) and then restart this procedure.  In this case, you should also [delete any associated resources](/azure/databox-online/azure-stack-edge-return-device?tabs=azure-portal) left in the Azure Portal after completing the Azure Stack Edge reset. This will include some or all of the following, depending on how far through the process you are:
+Alternatively, you can perform a full reset using the **Device Reset** blade in the local UI (see [Azure Stack Edge device reset and reactivation](/azure/databox-online/azure-stack-edge-reset-reactivate-device)) and then restart this procedure.  In this case, you should also [delete any associated resources](/azure/databox-online/azure-stack-edge-return-device?tabs=azure-portal) left in the Azure portal after completing the Azure Stack Edge reset. This will include some or all of the following, depending on how far through the process you are:
 
 - **Azure Stack Edge** resource
 - Autogenerated **KeyVault** associated with the **Azure Stack Edge** resource
@@ -385,4 +385,4 @@ Your packet core should now be in service with the updated ASE configuration. To
 
 Your Azure Stack Edge device is now ready for Azure Private 5G Core. The next step is to collect the information you'll need to deploy your private network.
 
-- [Collect the required information to deploy a private mobile network](./collect-required-information-for-private-mobile-network.md)
+- [Collect the required information to deploy a private mobile network](./collect-required-information-for-private-mobile-network.md)
diff --git a/articles/private-5g-core/configure-service-sim-policy-arm-template.md b/articles/private-5g-core/configure-service-sim-policy-arm-template.md
@@ -53,7 +53,7 @@ Two Azure resources are defined in the template.
     - **Subscription:** select the Azure subscription you used to create your private mobile network.
     - **Resource group:** select the resource group containing the Mobile Network resource representing your private mobile network.
     - **Region:** select the region in which you deployed the private mobile network.
-    - **Location:** enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*.
+    - **Location:** enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network.
     - **Existing Mobile Network Name:** enter the name of the Mobile Network resource representing your private mobile network.
     - **Existing Slice Name:** enter the name of the Slice resource representing your network slice.
     - **Existing Data Network Name:** enter the name of the data network. This value must match the name you used when creating the data network.
diff --git a/articles/private-5g-core/create-site-arm-template.md b/articles/private-5g-core/create-site-arm-template.md
@@ -54,7 +54,7 @@ Four Azure resources are defined in the template.
     | **Subscription** | Select the Azure subscription you used to create your private mobile network. |
     | **Resource group** | Select the resource group containing the mobile network resource representing your private mobile network. |
     | **Region** | Select the region in which you deployed the private mobile network. |
-    | **Location** | Enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*. |
+    | **Location** | Enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. |
     | **Existing Mobile Network Name** | Enter the name of the mobile network resource representing your private mobile network. |
     | **Existing Data Network Name** | Enter the name of the data network. This value must match the name you used when creating the data network. |
     | **Site Name** | Enter a name for your site.|
diff --git a/articles/private-5g-core/create-slice-arm-template.md b/articles/private-5g-core/create-slice-arm-template.md
@@ -2,8 +2,8 @@
 title: Create a slice - ARM template
 titleSuffix: Azure Private 5G Core
 description: This how-to guide shows how to create a slice in your private mobile network using an Azure Resource Manager (ARM) template. 
-author: b-branco
-ms.author: biancabranco
+author: robswain
+ms.author: robswain
 ms.service: private-5g-core
 ms.topic: how-to
 ms.date: 09/30/2022
@@ -52,8 +52,8 @@ The following Azure resource is defined in the template.
     |--|--|
     | **Subscription** | Select the Azure subscription you used to create your private mobile network. |
     | **Resource group** | Select the resource group containing the mobile network resource representing your private mobile network. |
-    | **Region** | Select **East US**. |
-    | **Location** | Enter *eastus*. |
+    | **Region** | Select the region in which you deployed the private mobile network. |
+    | **Location** | Enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. |
     | **Existing Mobile Network Name** | Enter the name of the Mobile Network resource representing your private mobile network. |
     | **Slice Name** | Enter the name of the network slice. |
     | **Sst** | Enter the slice/service type (SST) value. If the slice will be used by 4G UEs, enter a value of 1. |
diff --git a/articles/private-5g-core/deploy-private-mobile-network-with-site-command-line.md b/articles/private-5g-core/deploy-private-mobile-network-with-site-command-line.md
@@ -12,7 +12,7 @@ ms.date: 03/15/2023
 
 # Quickstart: Deploy a private mobile network and site - Azure CLI
 
-Azure Private 5G Core is an Azure cloud service for deploying and managing 5G core network functions on an Azure Stack Edge device, as part of an on-premises private mobile network for enterprises. This quickstart describes how to use an Azure CLI to deploy the following.
+Azure Private 5G Core is an Azure cloud service for deploying and managing 5G core network functions on an Azure Stack Edge device, as part of an on-premises private mobile network for enterprises. This quickstart describes how to use an Azure CLI to deploy the following resources in the East US Azure region. See [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=private-5g-core) for the Azure regions where Azure Private 5G Core is available.
 
 - A private mobile network.
 - A site.
diff --git a/articles/private-5g-core/deploy-private-mobile-network-with-site-powershell.md b/articles/private-5g-core/deploy-private-mobile-network-with-site-powershell.md
@@ -12,7 +12,7 @@ ms.date: 03/15/2023
 
 # Quickstart: Deploy a private mobile network and site - Azure PowerShell
 
-Azure Private 5G Core is an Azure cloud service for deploying and managing 5G core network functions on an Azure Stack Edge device, as part of an on-premises private mobile network for enterprises. This quickstart describes how to use an Azure PowerShell to deploy the following.
+Azure Private 5G Core is an Azure cloud service for deploying and managing 5G core network functions on an Azure Stack Edge device, as part of an on-premises private mobile network for enterprises. This quickstart describes how to use an Azure PowerShell to deploy the following resources in the East US Azure region. See [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=private-5g-core) for the Azure regions where Azure Private 5G Core is available.
 
 - A private mobile network.
 - A site.
diff --git a/articles/private-5g-core/provision-sims-arm-template.md b/articles/private-5g-core/provision-sims-arm-template.md
@@ -134,7 +134,7 @@ The following Azure resources are defined in the template.
     - **Subscription:** select the Azure subscription you used to create your private mobile network.
     - **Resource group:** select the resource group containing the Mobile Network resource representing your private mobile network.
     - **Region:** select the region in which you deployed the private mobile network.
-    - **Location:** enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network. For the East US region, this is *eastus*; for West Europe, this is *westeurope*.
+    - **Location:** enter the [code name](region-code-names.md) of the region in which you deployed the private mobile network.
     - **Existing Mobile Network Name:** enter the name of the Mobile Network resource representing your private mobile network.
     - **Existing Sim Policy Name:** enter the name of the SIM policy you want to assign to the SIMs.
     - **Sim Group Name:** enter the name for the new SIM group.
diff --git a/articles/private-5g-core/region-code-names.md b/articles/private-5g-core/region-code-names.md
@@ -1,8 +1,8 @@
 ---
 title: Region code names for Azure Private 5G Core 
 description: Learn about the region code names used for the location parameter in Azure Private 5G Core ARM templates
-author: b-branco
-ms.author: biancabranco
+author: robswain
+ms.author: robswain
 ms.service: private-5g-core
 ms.topic: reference
 ms.custom: references_regions
@@ -27,3 +27,5 @@ DisplayName               Name                 RegionalDisplayName
 East US                   eastus               (US) East US
 West Europe               westeurope           (Europe) West Europe
 ```
+
+See [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=private-5g-core) for the Azure regions where Azure Private 5G Core is available.
diff --git a/articles/private-5g-core/region-move-private-mobile-network-resources.md b/articles/private-5g-core/region-move-private-mobile-network-resources.md
@@ -2,8 +2,8 @@
 title: Move Azure Private 5G Core private mobile network resources between regions
 titleSuffix: Azure Private 5G Core
 description: In this how-to guide, you'll learn how to move your private mobile network resources to a different region.
-author: b-branco
-ms.author: biancabranco
+author: robswain
+ms.author: robswain
 ms.service: private-5g-core
 ms.topic: how-to 
 ms.date: 01/04/2023
@@ -19,7 +19,7 @@ You might move your resources to another region for a number of reasons. For exa
 ## Prerequisites
 
 - Ensure you can sign in to the Azure portal using an account with access to the active subscription you used to create your private mobile network. This account must have the built-in Contributor or Owner role at the subscription scope.
-- Ensure Azure Private 5G Core supports the region to which you want to move your resources. Refer to [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
+- Ensure Azure Private 5G Core supports the region to which you want to move your resources. Refer to [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=private-5g-core).
 - Verify pricing and charges associated with the target region to which you want to move your resources.
 - Choose a name for your new resource group in the target region. This must be different to the source region's resource group name.
 - If you use Azure Active Directory (Azure AD) to authenticate access to your local monitoring tools, ensure your local machine has core kubectl access to the Azure Arc-enabled Kubernetes cluster. This requires a core kubeconfig file, which you can obtain by following [Set up kubectl access](commission-cluster.md#set-up-kubectl-access).
diff --git a/articles/private-5g-core/reliability-private-5g-core.md b/articles/private-5g-core/reliability-private-5g-core.md
@@ -13,14 +13,14 @@ ms.date: 01/31/2022
 
 This article describes reliability support in Azure Private 5G Core. It covers both regional resiliency with availability zones and cross-region resiliency with disaster recovery. For an overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
 
+See [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=private-5g-core) for the Azure regions where Azure Private 5G Core is available.
+
 ## Availability zone support
 
 The Azure Private 5G Core service is automatically deployed as zone-redundant in Azure regions that support availability zones, as listed in [Availability zone service and regional support](../reliability/availability-zones-service-support.md). If a region supports availability zones then all Azure Private 5G Core resources created in a region can be managed from any of the availability zones.
 
 No further work is required to configure or manage availability zones. Failover between availability zones is automatic.
 
-Azure Private 5G Core is currently available in the EastUS and WestEurope regions.
-
 ### Zone down experience
 
 In a zone-wide outage scenario, users should experience no impact because the service will move to take advantage of the healthy zone automatically. At the start of a zone-wide outage, you may see in-progress ARM requests time-out or fail. New requests will be directed to healthy nodes with zero impact on users and any failed operations should be retried. You'll still be able to create new resources and update, monitor and manage existing resources during the outage.
@@ -33,8 +33,6 @@ The application ensures that all cloud state is replicated between availability
 
 Azure Private 5G Core is only available in multi-region (3+N) geographies. The service automatically replicates SIM credentials to a backup region in the same geography. This means that there's no loss of data in the event of region failure. Within four hours of the failure, all resources in the failed region are available to view through the Azure portal and ARM tools but will be read-only until the failed region is recovered. the packet running at the Edge continues to operate without interruption and network connectivity will be maintained.
 
-To view all regions that support Azure Private 5G Core, see [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
-
 ### Cross-region disaster recovery in multi-region geography
 
 Microsoft is responsible for outage detection, notification and support for the Azure cloud aspects of the Azure Private 5G Core service.
