Azure DevOps Kubernetes Environment Validation Failures — Connectivity and API Request Errors

Problem description

I am experiencing issues with my Kubernetes Environment resources in Azure DevOps Services. All existing resources show the message: 'Unable to connect to the cluster and namespace chosen for this resource.' Additionally, attempting to create a new Kubernetes resource results in validation failure with the error: 'There were validation errors while processing the kubernetes resource. Failed to query service connection API: https://{aks-api-server}:443' and 'An error occurred while sending the request.' I am seeking assistance to understand the root cause and resolve these connectivity and validation problems.

Environment

Azure DevOps Services, Kubernetes Resources, in the West Europe region, using Azure Kubernetes Service (AKS) clusters with public API endpoints.

What I've already tried

From the case record, I verified that the AKS API endpoints are reachable from Azure, clusters are not private, and API server authorized IP ranges are not configured. I recreated the Kubernetes resource with current connection details, and client-side and cluster-side checks such as DNS resolution, TLS connectivity, and credential validation all succeed. Despite this, the validation still fails with the 'An error occurred while sending the request' message. I also confirmed that the server URL matches the AKS FQDN, and the network path appears functional from outside the network.

Current status

I am looking for guidance on why Azure DevOps validation fails despite the AKS API being reachable and the connection details being correct. I would appreciate assistance in escalating this to the Azure Pipelines product team for backend log analysis or recommendations to resolve the validation failure.