[BUG] AKS Hybrid fail to deploy if using public DNS

**Describe the bug**
I was trying to deploy AKS hybrid with the DNS pointing to 1.1.1.1 instead of our Domain DNS. However the deployment stuck at scaling control plane. Further check on control plane found that AKS Hybrid try to access AKS cloudagent server which is not there if we public DNS.

**To Reproduce**
Steps to reproduce the behavior:
1. Create 1 aks cluster network pointing to 1.1.1.1,1.0.0.1
2. Create new cluster with the aks cluster network pointing to 1.1.1.1

**Expected behavior**
AKS Cluster will stuck at deploying/scaling control plane

**Screenshots**
Remotingone of the Control plane found out the AKS Cluster still require access to AKS Cloudagent
stuck at scaling control plane

**Environment (please complete the following information):**
- AKS-HCI Version 1.0.21.11030
- Kubernetes Version 1.26.6

No repository file, test, or entry point is identified. Start by reproducing the AKS Hybrid deployment with the listed public DNS servers and inspect the control-plane scaling failure and its AKS Cloudagent access requirement. Done should mean the deployment behavior and required DNS or endpoint access are clearly established and documented.

Written by the indexing model from the issue text.