A managed cluster configuration can describe node count, machine size, identity and control-plane access. Those settings are inputs to a workload platform. They do not prove that a Pod can start, pull an image, reach a dependency, or satisfy a business availability target.
At Ashfield Engineering, operations needs a private control-plane configuration and enough declared node capacity for its training plan. You will configure cluster records and distinguish that intent from the behavior a real cluster would still need to demonstrate. The browser stores supported AKS fields only. It does not create node pools, run a scheduler, execute kubectl, provision a network path, or test a Kubernetes version. A private control plane also leaves application ingress choices to the workload design. Keep each of those boundaries visible in the final recommendation.
Separate declared cluster settings from running workload evidence.