Fixing AKS broken links

Author: schaffererin

articles/aks/configure-azure-cni-dynamic-ip-allocation.md

@@ -30,8 +30,8 @@ This article shows you how to use Azure CNI networking for dynamic allocation of
 > [!NOTE]
 > When using dynamic allocation of IPs, exposing an application as a Private Link Service using a Kubernetes Load Balancer Service isn't supported.
 
-* Review the [prerequisites](./configure-azure-cni.md#prerequisites) for configuring basic Azure CNI networking in AKS, as the same prerequisites apply to this article.
-* Review the [deployment parameters](./configure-azure-cni.md#deployment-parameters) for configuring basic Azure CNI networking in AKS, as the same parameters apply.
+* Review the [prerequisites][azure-cni-prereq] for configuring basic Azure CNI networking in AKS, as the same prerequisites apply to this article.
+* Review the [deployment parameters][azure-cni-deployment-parameters] for configuring basic Azure CNI networking in AKS, as the same parameters apply.
 * AKS Engine and DIY clusters aren't supported.
 * Azure CLI version `2.37.0` or later.
 
@@ -56,7 +56,7 @@ All other guidance related to configuring the maximum pods per node remains the
 
 ## Deployment parameters
 
-The [deployment parameters](./configure-azure-cni.md#deployment-parameters) for configuring basic Azure CNI networking in AKS are all valid, with two exceptions:
+The [deployment parameters][azure-cni-deployment-parameters]for configuring basic Azure CNI networking in AKS are all valid, with two exceptions:
 
 * The **subnet** parameter now refers to the subnet related to the cluster's nodes.
 * An additional parameter **pod subnet** is used to specify the subnet whose IP addresses will be dynamically allocated to pods.
@@ -151,7 +151,7 @@ Set the variables for subscription, resource group and cluster. Consider the fol
 
 4.	To view the metrics on the cluster, go to Workbooks on the cluster page in the Azure portal, and find the workbook named "Subnet IP Usage". Your view will look similar to the following:
 
-    :::image type="content" source="media/configure-azure-cni-dynamic-ip-allocation/ip-subnet-usage.png" alt-text="A diagram of the Azure portal's workbook blade is shown, and metrics for an AKS cluster's subnet IP usage are displayed.":::    
+    :::image type="content" source="media/configure-azure-cni-dynamic-ip-allocation/ip-subnet-usage.png" alt-text="A diagram of the Azure portal's workbook blade is shown, and metrics for an AKS cluster's subnet IP usage are displayed.":::
 
 ## Dynamic allocation of IP addresses and enhanced subnet support FAQs
 
@@ -189,3 +189,5 @@ Learn more about networking in AKS in the following articles:
 [aks-ingress-static-tls]: ingress-static-ip.md
 [aks-http-app-routing]: http-application-routing.md
 [aks-ingress-internal]: ingress-internal-ip.md
+[azure-cni-prereq]: ./configure-azure-cni.md#prerequisites
+[azure-cni-deployment-parameters]: ./configure-azure-cni.md#deployment-parameters

articles/aks/kubernetes-service-principal.md

@@ -233,7 +233,7 @@ Check the expiration date of your service principal credentials using the [`az a
 az ad app credential list --id <app-id> --query "[].endDateTime" -o tsv
 ```
 
-The default expiration time for the service principal credentials is one year. If your credentials are older than one year, you can [reset the existing credentials](update-credentials.md#reset-the-existing-service-principal-credentials) or [create a new service principal](update-credentials.md#create-a-new-service-principal).
+The default expiration time for the service principal credentials is one year. If your credentials are older than one year, you can [reset the existing credentials][reset-credentials] or [create a new service principal][new-service-principal].
 
 **General Azure CLI troubleshooting**
 
@@ -284,7 +284,9 @@ For information on how to update the credentials, see [Update or rotate the cred
 [rbac-disk-contributor]: ../role-based-access-control/built-in-roles.md#virtual-machine-contributor
 [az-role-assignment-create]: /cli/azure/role/assignment#az-role-assignment-create
 [aks-to-acr]: cluster-container-registry-integration.md
-[update-credentials]: update-credentials.md
+[update-credentials]: ./update-credentials.md
+[reset-credentials]: ./update-credentials.md#reset-the-existing-service-principal-credentials
+[new-service-principal]: ./update-credentials.md#create-a-new-service-principal
 [azure-ad-permissions]: ../active-directory/fundamentals/users-default-permissions.md
 [aks-permissions]: concepts-identity.md#aks-service-permissions
 [install-the-azure-az-powershell-module]: /powershell/azure/install-az-ps

articles/aks/use-system-pools.md

@@ -355,5 +355,5 @@ In this article, you learned how to create and manage system node pools in an AK
 [use-multiple-node-pools]: use-multiple-node-pools.md
 [maximum-pods]: configure-azure-cni.md#maximum-pods-per-node
 [update-node-pool-mode]: use-system-pools.md#update-existing-cluster-system-and-user-node-pools
-[start-stop-nodepools]: start-stop-nodepools.md
+[start-stop-nodepools]: ./start-stop-nodepools.md
 [node-affinity]: operator-best-practices-advanced-scheduler.md#node-affinity