Additional private endpoints to an existing private AKS cluster

Alex 285 Reputation points


I would like some help/insights on below situation.

  • I got a private AKS cluster deployed in Vnet1.
  • Now I am trying to create another private endpoint for this AKS cluster from another Vnet2.
  • I am able to successfully create one and it gets auto-approved as well, only when I choose the AKS resource from the drop-down (Connect to an Azure resource in my directory).
  • But, it doesn't get auto-approved when I create it using the resource ID/alias.


  • Can this be done? If yes, where does this private endpoint connection request go? and how can I get it approved? If no, why?
Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
459 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,845 questions
0 comments No comments
{count} votes

Accepted answer
  1. Deepanshu katara 4,350 Reputation points

    Hi, Thanks to reaching to us.

    The consumers can request a connection to a private-link service by using either the resource URI or the alias. To connect by using the alias, create a private endpoint by using the manual connection approval method. To use the manual connection approval method, set the manual request parameter to True during the private-endpoint create flow.

    This manual request can be auto approved if the consumer's subscription is allow-listed on the provider side.

    To learn more go to controlling service access.

    Please check below docs for more ref

    Kindly accept answer if it helps, Thanks!

    0 comments No comments

0 additional answers

Sort by: Most helpful