Merge pull request #292979 from LouisBerner/v-loberner-ado-359496-rebranding-1

Updated for Azure Local rebranding.

Author: prmerger-automator[bot]

articles/private-5g-core/collect-required-information-for-a-site.md

@@ -6,7 +6,7 @@ author: anzaman
 ms.author: alzam
 ms.service: azure-private-5g-core
 ms.topic: how-to 
-ms.date: 02/07/2022
+ms.date: 01/15/2025
 ms.custom: template-how-to
 zone_pivot_groups: ase-pro-version
 ---
@@ -51,15 +51,15 @@ Collect all the values in the following table for the packet core instance that
    |---------|---------|
    |The core technology type the packet core instance should support: 5G, 4G, or combined 4G and 5G. |**Technology type**|
    | The Azure Stack Edge resource representing the Azure Stack Edge Pro device in the site. You created this resource as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> If you're going to create your site using the Azure portal, collect the name of the Azure Stack Edge resource.</br></br> If you're going to create your site using an ARM template, collect the full resource ID of the Azure Stack Edge resource. You can do this by navigating to the Azure Stack Edge resource, selecting **JSON View**, and copying the contents of the **Resource ID** field. | **Azure Stack Edge device** |
-   |The custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site. You commissioned the AKS-HCI cluster as part of the steps in [Commission the AKS cluster](commission-cluster.md).</br></br> If you're going to create your site using the Azure portal, collect the name of the custom location.</br></br> If you're going to create your site using an ARM template, collect the full resource ID of the custom location. You can do this by navigating to the Custom location resource, selecting **JSON View**, and copying the contents of the **Resource ID** field.|**Custom location**|
+   |The custom location that targets the Azure Kubernetes Service on Azure Local (AKS on Azure Local) cluster on the Azure Stack Edge Pro device in the site. You commissioned AKS on Azure Local as part of the steps in [Commission the AKS cluster](commission-cluster.md).</br></br> If you're going to create your site using the Azure portal, collect the name of the custom location.</br></br> If you're going to create your site using an ARM template, collect the full resource ID of the custom location. You can do this by navigating to the Custom location resource, selecting **JSON View**, and copying the contents of the **Resource ID** field.|**Custom location**|
    | The virtual network name on port 6 on your Azure Stack Edge Pro GPU device corresponding to the user plane interface on the data network. For 5G, this interface is the N6 interface; for 4G, it's the SGi interface; for combined 4G and 5G, it's the N6/SGi interface. | **ASE N6 virtual subnet** (for 5G) or **ASE SGi virtual subnet** (for 4G), or **ASE N6/SGi virtual subnet** (for combined 4G and 5G). |
 :::zone-end
 :::zone pivot="ase-pro-2"
    |Value  |Field name in Azure portal  |
    |---------|---------|
    |The core technology type the packet core instance should support: 5G, 4G, or combined 4G and 5G. |**Technology type**|
    | The Azure Stack Edge resource representing the Azure Stack Edge Pro device in the site. You created this resource as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> If you're going to create your site using the Azure portal, collect the name of the Azure Stack Edge resource.</br></br> If you're going to create your site using an ARM template, collect the full resource ID of the Azure Stack Edge resource. You can do this by navigating to the Azure Stack Edge resource, selecting **JSON View**, and copying the contents of the **Resource ID** field. | **Azure Stack Edge device** |
-   |The custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site. You commissioned the AKS-HCI cluster as part of the steps in [Commission the AKS cluster](commission-cluster.md).</br></br> If you're going to create your site using the Azure portal, collect the name of the custom location.</br></br> If you're going to create your site using an ARM template, collect the full resource ID of the custom location. You can do this by navigating to the Custom location resource, selecting **JSON View**, and copying the contents of the **Resource ID** field.|**Custom location**|
+   |The custom location that targets the AKS on Azure Local cluster on the Azure Stack Edge Pro device in the site. You commissioned AKS on Azure Local as part of the steps in [Commission the AKS cluster](commission-cluster.md).</br></br> If you're going to create your site using the Azure portal, collect the name of the custom location.</br></br> If you're going to create your site using an ARM template, collect the full resource ID of the custom location. You can do this by navigating to the Custom location resource, selecting **JSON View**, and copying the contents of the **Resource ID** field.|**Custom location**|
    | The virtual network name on port 4 on your Azure Stack Edge Pro 2 device corresponding to the user plane interface on the data network. For 5G, this interface is the N6 interface; for 4G, it's the SGi interface; for combined 4G and 5G, it's the N6/SGi interface. |  **ASE N6 virtual subnet** (for 5G) or **ASE SGi virtual subnet** (for 4G), or **ASE N6/SGi virtual subnet** (for combined 4G and 5G). |
    | The gateway for the IP address configured for the N6 interface | SGi/N6 gateway | 
 :::zone-end
@@ -89,9 +89,9 @@ Collect all the values in the following table to define the packet core instance
    |Value  |Field name in Azure portal  |
    |---------|---------|
    | The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface. |**ASE N2 interface** (for 5G), **ASE S1-MME interface** (for 4G), or **ASE S1-MME/N2 interface** (for combined 4G and 5G). |
-   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).  </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual IP address** (for 5G), **ASE S1-MME virtual IP address** (for 4G), or **ASE S1-MME/N2 virtual IP address** (for combined 4G and 5G). |
+   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying AKS on Azure Local on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).  </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual IP address** (for 5G), **ASE S1-MME virtual IP address** (for 4G), or **ASE S1-MME/N2 virtual IP address** (for combined 4G and 5G). |
    | The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface; for combined 4G and 5G, it's the N3/S1-U interface. |**ASE N3 interface** (for 5G), **ASE S1-U interface** (for 4G), or **ASE S1-U/N3 interface** (for combined 4G and 5G). |
-   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers.  | **ASE N3 virtual IP address** (for 5G), **ASE S1-U virtual IP address** (for 4G), or **ASE S1-U/N3 virtual IP address** (for combined 4G and 5G). |
+   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying AKS on Azure Local on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers.  | **ASE N3 virtual IP address** (for 5G), **ASE S1-U virtual IP address** (for 4G), or **ASE S1-U/N3 virtual IP address** (for combined 4G and 5G). |
    | The ID number of the VLAN for the N2 network | S1-MME/N2 VLAN ID |
    | The subnet for the IP address configured for the N2 interface e.g. 10.232.44.0/24 | S1-MME/N2 subnet |
    | The gateway for the IP address configured for the N2 interface e.g. 10.232.44.1. If the subnet does not have a default gateway, use another IP address in the subnet which will respond to ARP requests (such as one of the RAN IP addresses). If there's more than one gNB connected via a switch, choose one of the IP addresses for the gateway. | S1-MME/N2 gateway |
@@ -109,9 +109,9 @@ Collect all the values in the following table to define the packet core instance
    |Value  |Field name in Azure portal  |
    |---------|---------|
    | The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface. |**ASE N2 interface** (for 5G), **ASE S1-MME interface** (for 4G), or **ASE S1-MME/N2 interface** (for combined 4G and 5G). |
-   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).  </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual IP address** (for 5G), **ASE S1-MME virtual IP address** (for 4G), or **ASE S1-MME/N2 virtual IP address** (for combined 4G and 5G). |
+   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying AKS on Azure Local on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).  </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual IP address** (for 5G), **ASE S1-MME virtual IP address** (for 4G), or **ASE S1-MME/N2 virtual IP address** (for combined 4G and 5G). |
    | The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface; for combined 4G and 5G, it's the N3/S1-U interface. |**ASE N3 interface** (for 5G), **ASE S1-U interface** (for 4G), or **ASE S1-U/N3 interface** (for combined 4G and 5G). |
-   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers.  | **ASE N3 virtual IP address** (for 5G), **ASE S1-U virtual IP address** (for 4G), or **ASE S1-U/N3 virtual IP address** (for combined 4G and 5G). |
+   | The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying AKS on Azure Local on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers.  | **ASE N3 virtual IP address** (for 5G), **ASE S1-U virtual IP address** (for 4G), or **ASE S1-U/N3 virtual IP address** (for combined 4G and 5G). |
    | The ID number of the VLAN for the N2 network | S1-MME/N2 VLAN ID |
    | The subnet for the IP address configured for the N2 interface e.g. 10.232.44.0/24 | S1-MME/N2 subnet |
    | The gateway for the IP address configured for the N2 interface e.g. 10.232.44.1. If the subnet does not have a default gateway, use another IP address in the subnet which will respond to ARP requests (such as one of the RAN IP addresses). If there's more than one gNB connected via a switch, choose one of the IP addresses for the gateway. | S1-MME/N2 gateway |

articles/private-5g-core/complete-private-mobile-network-prerequisites.md

@@ -6,7 +6,7 @@ author: anzaman
 ms.author: alzam
 ms.service: azure-private-5g-core
 ms.topic: how-to 
-ms.date: 03/30/2023
+ms.date: 01/15/2025
 ms.custom: template-how-to, devx-track-azurecli
 zone_pivot_groups: ase-pro-version
 ---
@@ -90,7 +90,7 @@ Depending on your networking requirements (for example, if a limited set of subn
 - Default gateway.
 - One IP address for the management port (port 2) on the Azure Stack Edge Pro 2 device.
   - HA: four IP addresses (two for each Azure Stack Edge device).
-- Six sequential IP addresses for the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster nodes.
+- Six sequential IP addresses for the Azure Kubernetes Service on Azure Local (AKS on Azure Local) cluster nodes.
   - HA: seven sequential IP addresses.
 - One service IP address for accessing local monitoring tools for the packet core instance.
 
@@ -107,7 +107,7 @@ Additional IP addresses for the two node Azure Stack Edge cluster in an HA deplo
 - One IP address for the management port
   - Choose a port between 2 and 4 to use as the Azure Stack Edge Pro GPU device's management port as part of [setting up your Azure Stack Edge Pro device](#order-and-set-up-your-azure-stack-edge-pro-devices).*
   - HA: two IP addresses (one for each Azure Stack Edge device)
-- Six sequential IP addresses for the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster nodes.
+- Six sequential IP addresses for the AKS on Azure Local cluster nodes.
   - HA: seven sequential IP addresses.
 - One service IP address for accessing local monitoring tools for the packet core instance.
 

articles/private-5g-core/create-site-arm-template.md

@@ -6,7 +6,7 @@ author: anzaman
 ms.author: alzam
 ms.service: azure-private-5g-core
 ms.topic: how-to
-ms.date: 03/16/2022
+ms.date: 01/15/2025
 ms.custom: template-how-to, devx-track-arm-template
 zone_pivot_groups: ase-pro-version
 ---
@@ -75,7 +75,7 @@ Four Azure resources are defined in the template.
     | **Core Network Technology** | Enter *5GC* for 5G, *EPC* for 4G, or *EPC + 5GC* for combined 4G and 5G. |
     | **Napt Enabled** | Set this field depending on whether Network Address and Port Translation (NAPT) should be enabled for the data network. |
     | **Dns Addresses** | Enter the DNS server addresses. You should only omit this if you don't need the UEs to perform DNS resolution, or if all UEs in the network will use their own locally configured DNS servers. |
-    | **Custom Location** | Enter the resource ID of the custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site. |
+    | **Custom Location** | Enter the resource ID of the custom location that targets the Azure Kubernetes Service on Azure Local (AKS on Azure Local) cluster on the Azure Stack Edge Pro device in the site. |
 
 :::zone-end
 :::zone pivot="ase-pro-2"
@@ -100,7 +100,7 @@ Four Azure resources are defined in the template.
     | **Core Network Technology** | Enter *5GC* for 5G, *EPC* for 4G, or *EPC + 5GC* for combined 4G and 5G. |
     | **Napt Enabled** | Set this field depending on whether Network Address and Port Translation (NAPT) should be enabled for the data network. |
     | **Dns Addresses** | Enter the DNS server addresses. You should only omit this if you don't need the UEs to perform DNS resolution, or if all UEs in the network will use their own locally configured DNS servers. |
-    | **Custom Location** | Enter the resource ID of the custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site. |
+    | **Custom Location** | Enter the resource ID of the custom location that targets the AKS on Azure Local cluster on the Azure Stack Edge Pro device in the site. |
 
 :::zone-end