Skip to content

Create a Private Endpoint

A Private Endpoint places a network interface with a private IP in a customer subnet and connects it to the deployment's Private Link Service.

Before you begin

You need:

  • the authoritative Private Link Service resource ID from deployment outputs;
  • permission to create a Private Endpoint in the selected resource group and subnet;
  • an approved VNet and subnet with available address space;
  • a route from the intended client networks.

Warning

Never reconstruct the Private Link Service resource ID from a resource-name pattern. Internal Azure names can change. Use the value from deployment details or obtain it from iVedha support.

Create the endpoint

  1. In the Azure portal, search for Private endpoints.
  2. Select Create.
  3. On Basics, choose the subscription and resource group that will own the endpoint. Enter an approved name and region.
  4. On Resource, choose the option to connect by resource ID or alias.
  5. Paste the complete Private Link Service resource ID from deployment details.
  6. On Virtual Network, select the approved VNet and subnet.
  7. Configure application security groups or tags only when required by your organization.
  8. Review the settings and select Create.

Confirm connection approval

  1. Open the created Private Endpoint.
  2. Check Connection status.
  3. If it is Pending, ask the owner shown in deployment details or iVedha support to review the request. Same-subscription requests are not guaranteed to be automatically approved.
  4. Continue only when the status is Approved.

Record the endpoint resource ID, network interface, private IP, subnet, and approval time. Do not publish these deployment-specific values.

The endpoint does not configure application DNS or TLS. Continue with configure private DNS.