Found a way to disconnect a AKS cluster from Rancher that was created in Cluster Management with out deleting the AKS cluster so it can be imported into another rancher. These are the steps as far as I can get. 1. Get the Creds from the AKS cluster do not use the rancher Creds or it blocks the user-cluster.yml because of permissions. 2. I can remove the components from the nodes using the user-cluster.yml that the user-cluster.sh would have called you just need to update the image: rancher/rancher-agent:v2.7.9 with the image your cluster is using for rancher-agent 3. Delete the webhook config's or you will have an error when you import (Failed to communicate with cluster: error generating service account token: Internal error occurred: failed calling webhook "rancher.cattle.io.namespaces.create-non-kubesystem": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation/namespaces?timeout=10s": service "rancher-webhook" not found) a. kubectl delete validatingwebhookconfiguration rancher.cattle.io b. kubectl delete mutatingwebhookconfiguration rancher.cattle.io 4. I Lock the resource group in Azure from delete 5. I then delete the Cluster from Cluster Management 6. Check Azure and cluster is still up 7. I can manually delete the Fleet scripts with in the Local cluster that were created for the cluster a. Contents,Bundles,ClusterRegistrations 8. I can manually remove the finalizers from Cluster Provisioning so the Config deletes. a. AKSClusterConfigs 9. Check Azure and cluster is still up 10. Remove the Lock from step 4 11. Try Import in Cluster Management for the Cluster you just deleted. 12. There maybe the old Job "cattle-cleanup-job" still on the cluster that is in a failed state that needs to be deleted.