Resolved broken links

Author: schaffererin

.openpublishing.redirection.json

@@ -3924,6 +3924,11 @@
             "redirect_url": "/azure/kubernetes-fleet/concepts-resource-propagation",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/kubernetes-fleet/access-fleet-kubernetes-api.md",
+            "redirect_url": "/azure/kubernetes-fleet/quickstart-access-fleet-kubernetes-api",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/defender-for-iot/organizations/update-legacy-ot-software.md",
             "redirect_url": "/azure/defender-for-iot/organizations/update-ot-software?tabs=portal",

articles/kubernetes-fleet/concepts-resource-propagation.md

@@ -332,7 +332,7 @@ Resource-only changes (updating the resources or updating the `ResourceSelector`
 
 ## Access the Kubernetes API of the Fleet resource cluster
 
-If you created a Azure Kubernetes Fleet Manager resource with the hub cluster enabled, you can use it to centrally control scenarios like Kubernetes object propagation. To access the Kubernetes API of the Fleet resource cluster, follow the steps in [Access the Kubernetes API of the Fleet resource cluster with Azure Kubernetes Fleet Manager](access-fleet-kubernetes-api.md).
+If you created a Azure Kubernetes Fleet Manager resource with the hub cluster enabled, you can use it to centrally control scenarios like Kubernetes object propagation. To access the Kubernetes API of the Fleet resource cluster, follow the steps in [Access the Kubernetes API of the Fleet resource cluster with Azure Kubernetes Fleet Manager](./quickstart-access-fleet-kubernetes-api.md).
 
 ## Next steps
 

articles/kubernetes-fleet/l4-load-balancing.md

@@ -31,7 +31,7 @@ You can follow this document to set up layer 4 load balancing for such multi-clu
   * These target clusters have to be [added as member clusters to the Fleet resource](./quickstart-create-fleet-and-members.md#join-member-clusters).
   * These target clusters should be using [Azure CNI (Container Networking Interface) networking](../aks/configure-azure-cni.md).
 
-* You must gain access to the Kubernetes API of the hub cluster by following the steps in [Access the Kubernetes API of the Fleet resource](./access-fleet-kubernetes-api.md).
+* You must gain access to the Kubernetes API of the hub cluster by following the steps in [Access the Kubernetes API of the Fleet resource](./quickstart-access-fleet-kubernetes-api.md).
 
 * Set the following environment variables and obtain the kubeconfigs for the fleet and all member clusters:
 

articles/kubernetes-fleet/quickstart-resource-propagation.md

@@ -20,7 +20,7 @@ In this quickstart, you learn how to propagate resources from an Azure Kubernete
 * An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 * You need a Fleet resource with a hub cluster and member clusters. If you don't have one, see [Create an Azure Kubernetes Fleet Manager resource and join member clusters using Azure CLI](quickstart-create-fleet-and-members.md).
 * Member clusters must be labeled appropriately in the hub cluster to match the desired selection criteria. Example labels include region, environment, team, availability zones, node availability, or anything else desired.
-* You need access to the Kubernetes API of the hub cluster. If you don't have access, see [Access the Kubernetes API of the Fleet resource with Azure Kubernetes Fleet Manager](./quickstart-access-kubernetes-api.md).
+* You need access to the Kubernetes API of the hub cluster. If you don't have access, see [Access the Kubernetes API of the Fleet resource with Azure Kubernetes Fleet Manager](./quickstart-access-fleet-kubernetes-api.md).
 
 ## Use the `ClusterResourcePlacement` API to propagate resources to member clusters