Quickstart: Create a private endpoint by using the Azure CLI
Get started with Azure Private Link by using a private endpoint to connect securely to an Azure web app.
In this quickstart, you'll create a private endpoint for an Azure web app and then create and deploy a virtual machine (VM) to test the private connection.
You can create private endpoints for various Azure services, such as Azure SQL and Azure Storage.
An Azure account with an active subscription. If you don't already have an Azure account, create an account for free.
To ensure that your subscription is active, sign in to the Azure portal, and then check your version by running
An Azure web app with a PremiumV2-tier or higher app service plan, deployed in your Azure subscription.
For more information and an example, see Quickstart: Create an ASP.NET Core web app in Azure.
The example webapp in this article is named myWebApp1979. Replace the example with your webapp name.
The latest version of the Azure CLI, installed.
Check your version of the Azure CLI in a terminal or command window by running
az --version. For the latest version, see the most recent release notes.
If you don't have the latest version of the Azure CLI, update it by following the installation guide for your operating system or platform.
Create a resource group
An Azure resource group is a logical container where Azure resources are deployed and managed.
First, create a resource group by using az group create:
az group create \ --name CreatePrivateEndpointQS-rg \ --location eastus
Create a virtual network and bastion host
A virtual network and subnet is required for to host the private IP address for the private endpoint. You'll create a bastion host to connect securely to the virtual machine to test the private endpoint. You'll create the virtual machine in a later section.
Create a virtual network with az network vnet create.
az network vnet create \ --resource-group CreatePrivateEndpointQS-rg \ --location eastus \ --name myVNet \ --address-prefixes 10.0.0.0/16 \ --subnet-name myBackendSubnet \ --subnet-prefixes 10.0.0.0/24
Create a bastion subnet with az network vnet subnet create.
az network vnet subnet create \ --resource-group CreatePrivateEndpointQS-rg \ --name AzureBastionSubnet \ --vnet-name myVNet \ --address-prefixes 10.0.1.0/27
Create a public IP address for the bastion host with az network public-ip create.
az network public-ip create \ --resource-group CreatePrivateEndpointQS-rg \ --name myBastionIP \ --sku Standard \ --zone 1 2 3
Create the bastion host with az network bastion create.
az network bastion create \ --resource-group CreatePrivateEndpointQS-rg \ --name myBastionHost \ --public-ip-address myBastionIP \ --vnet-name myVNet \ --location eastus
It can take a few minutes for the Azure Bastion host to deploy.
Create a private endpoint
An Azure service that supports private endpoints is required to set up the private endpoint and connection to the virtual network. For the examples in this article, you'll use the Azure WebApp from the prerequisites. For more information on the Azure services that support a private endpoint, see Azure Private Link availability.
A private endpoint can have a static or dynamically assigned IP address.
You must have a previously deployed Azure WebApp to proceed with the steps in this article. For more information, see Prerequisites .
Place the resource ID of the web app that you created earlier into a shell variable with az webapp list. Create the private endpoint with az network private-endpoint create.
id=$(az webapp list \ --resource-group CreatePrivateEndpointQS-rg \ --query '.[id]' \ --output tsv) az network private-endpoint create \ --connection-name myConnection --name myPrivateEndpoint \ --private-connection-resource-id $id \ --resource-group CreatePrivateEndpointQS-rg \ --subnet myBackendSubnet \ --group-id sites \ --vnet-name myVNet
Configure the private DNS zone
A private DNS zone is used to resolve the DNS name of the private endpoint in the virtual network. For this example, we're using the DNS information for an Azure WebApp, for more information on the DNS configuration of private endpoints, see Azure Private Endpoint DNS configuration].
Create a new private Azure DNS zone with az network private-dns zone create.
az network private-dns zone create \ --resource-group CreatePrivateEndpointQS-rg \ --name "privatelink.azurewebsites.net"
Link the DNS zone to the virtual network you created previously with az network private-dns link vnet create.
az network private-dns link vnet create \ --resource-group CreatePrivateEndpointQS-rg \ --zone-name "privatelink.azurewebsites.net" \ --name MyDNSLink \ --virtual-network myVNet \ --registration-enabled false
Create a DNS zone group with az network private-endpoint dns-zone-group create.
az network private-endpoint dns-zone-group create \ --resource-group CreatePrivateEndpointQS-rg \ --endpoint-name myPrivateEndpoint \ --name MyZoneGroup \ --private-dns-zone "privatelink.azurewebsites.net" \ --zone-name webapp
Create a test virtual machine
To verify the static IP address and the functionality of the private endpoint, a test virtual machine connected to your virtual network is required.
Create the virtual machine with az vm create.
az vm create \ --resource-group CreatePrivateEndpointQS-rg \ --name myVM \ --image Win2019Datacenter \ --public-ip-address "" \ --vnet-name myVNet \ --subnet myBackendSubnet \ --admin-username azureuser
Azure provides a default outbound access IP for VMs that either aren't assigned a public IP address or are in the back-end pool of an internal basic Azure load balancer. The default outbound access IP mechanism provides an outbound IP address that isn't configurable.
The default outbound access IP is disabled when a public IP address is assigned to the VM, the VM is placed in the back-end pool of a standard load balancer, with or without outbound rules, or if an Azure Virtual Network NAT gateway resource is assigned to the subnet of the VM.
VMs that are created by virtual machine scale sets in flexible orchestration mode don't have default outbound access.
For more information about outbound connections in Azure, see Default outbound access in Azure and Use source network address translation (SNAT) for outbound connections.
Test connectivity with the private endpoint
Use the VM you created in the previous step to connect to the webapp across the private endpoint.
Sign in to the Azure portal.
In the search box at the top of the portal, enter Virtual machine. Select Virtual machines.
On the overview page for myVM, select Connect, and then select Bastion.
Enter the username and password that you used when you created the VM. Select Connect.
After you've connected, open PowerShell on the server.
nslookup mywebapp1979.azurewebsites.net. Replace mywebapp1979 with the name of the web app that you created earlier. You'll receive a message that's similar to the following example:
Server: UnKnown Address: 184.108.40.206 Non-authoritative answer: Name: mywebapp1979.privatelink.azurewebsites.net Address: 10.0.0.10 Aliases: mywebapp1979.azurewebsites.net
In the bastion connection to myVM, open the web browser.
Enter the URL of your web app,
If your web app hasn't been deployed, you'll get the following default web app page:
Close the connection to myVM.
Clean up resources
When no longer needed, use the az group delete command to remove the resource group, private link service, load balancer, and all related resources.
az group delete \ --name CreatePrivateEndpointQS-rg
For more information about the services that support private endpoints, see:
Submit and view feedback for