Skip to content

Commit cc7d121

Browse files
Update articles/private-5g-core/collect-required-information-for-service.md
Co-authored-by: robswain <[email protected]>
1 parent 22c5621 commit cc7d121

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ During cluster commissioning, the Azure Private 5G Core private mobile network r
5858
|The ID of the Azure subscription in which the Azure resources are deployed. |**SUBSCRIPTION_ID**|
5959
|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**|
6060
|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**|
61-
|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, see [Region code names](region-code-names.md) for list of the supported regions and their codes. |**LOCATION**|
61+
|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; see [Region code names](region-code-names.md) for a list of supported regions and their code names. |**LOCATION**|
6262
|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**|
6363

6464
## Data flow policy rule(s)

0 commit comments

Comments
 (0)