Skip to content

Commit 4003c55

Browse files
Adding link previously commented out
1 parent 4adf8ee commit 4003c55

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/private-5g-core/region-move-private-mobile-network-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You might move your resources to another region for a number of reasons. For exa
1919
## Prerequisites
2020

2121
- 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.
22-
- 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/) -->
22+
- 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/).
2323
- Verify pricing and charges associated with the target region to which you want to move your resources.
2424
- Choose a name for your new resource group in the target region. This must be different to the source region's resource group name.
2525
- 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, see [Set up kubectl access](commission-cluster.md#set-up-kubectl-access) for instructions on how to obtain this file.

0 commit comments

Comments
 (0)