Tutorial: Connect to a storage account using an Azure Private Endpoint
Azure Private endpoint is the fundamental building block for Private Link in Azure. It enables Azure resources, like virtual machines (VMs), to privately and securely communicate with Private Link resources such as Azure Storage.
In this tutorial, you learn how to:
- Create a virtual network and bastion host.
- Create a virtual machine.
- Create a storage account with a private endpoint.
- Test connectivity to the storage account private endpoint.
If you don't have an Azure subscription, create a free account before you begin.
- An Azure subscription
Sign in to Azure
Sign in to the Azure portal.
Create a virtual network and bastion host
In this section, you'll create a virtual network, subnet, and bastion host.
The bastion host will be used to connect securely to the virtual machine for testing the private endpoint.
On the upper-left side of the screen, select Create a resource > Networking > Virtual network or search for Virtual network in the search box.
In Create virtual network, enter or select this information in the Basics tab:
Setting Value Project Details Subscription Select your Azure subscription. Resource Group Select Create new. Enter myResourceGroup in Name. Select OK. Instance details Name Enter myVNet. Region Select East US.
Select the IP Addresses tab or select the Next: IP Addresses button at the bottom of the page.
In the IP Addresses tab, enter this information:
Setting Value IPv4 address space Enter 10.1.0.0/16.
Under Subnet name, select the word default.
In Edit subnet, enter this information:
Setting Value Subnet name Enter mySubnet. Subnet address range Enter 10.1.0.0/24.
Select the Security tab.
Under BastionHost, select Enable. Enter this information:
Setting Value Bastion name Enter myBastionHost. AzureBastionSubnet address space Enter 10.1.1.0/24. Public IP Address Select Create new. For Name, enter myBastionIP. Select OK.
Select the Review + create tab or select the Review + create button.
Create a virtual machine
In this section, you'll create a virtual machine that will be used to test the private endpoint.
On the upper-left side of the portal, select Create a resource > Compute > Virtual machine or search for Virtual machine in the search box.
In Create a virtual machine, type or select the values in the Basics tab:
Setting Value Project Details Subscription Select your Azure subscription. Resource Group Select myResourceGroup. Instance details Virtual machine name Enter myVM. Region Select (US) East US. Availability Options Select No infrastructure redundancy required. Security type Select Standard. Image Select Windows Server 2019 Datacenter - Gen2. Azure Spot instance Select No. Size Choose VM size or take default setting. Administrator account Username Enter a username. Password Enter a password. Confirm password Reenter password.
Select the Networking tab, or select Next: Disks, then Next: Networking.
In the Networking tab, select or enter:
Setting Value Network interface. Virtual network myVNet. Subnet mySubnet. Public IP Select None. NIC network security group Basic. Public inbound ports Select None.
Select Review + create.
Review the settings, and then select Create.
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.
For more information, see Default outbound access in Azure.
The default outbound access IP is disabled when either a public IP address is assigned to the VM or the VM is placed in the back-end pool of a standard load balancer, with or without outbound rules. If an Azure Virtual Network network address translation (NAT) gateway resource is assigned to the subnet of the virtual machine, the default outbound access IP is disabled.
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 Use source network address translation (SNAT) for outbound connections.
Create storage account with a private endpoint
In this section, you'll create a storage account and configure the private endpoint.
In the left-hand menu, select Create a resource > Storage > Storage account, or search for Storage account in the search box.
In the Basics tab of Create storage account enter or select the following information:
Setting Value Project Details Subscription Select your Azure subscription. Resource Group Select myResourceGroup. Instance details Storage account name Enter mystorageaccount. If the name is unavailable, enter a unique name. Location Select (US) East US. Performance Leave the default Standard. Redundancy Select Locally-redundant storage (LRS).
Select the Networking tab or select the Next: Networking button.
In the Networking tab, under Network connectivity select Disable public access and use private access.
In Private endpoint, select + Add private endpoint.
In Create private endpoint enter or select the following information:
Setting Value Subscription Select your Azure subscription. Resource Group Select myResourceGroup. Location Select East US. Name Enter myPrivateEndpoint. Storage sub-resource Leave the default blob. Networking Virtual network Select myVNet. Subnet Select mySubnet. Private DNS integration. Integrate with private DNS zone Leave the default Yes. Private DNS Zone Leave the default (New) privatelink.blob.core.windows.net.
Select Review + create.
Select Resource groups in the left-hand navigation pane.
Select the storage account you created in the previous steps.
In the Security + networking section of the storage account, select Access keys.
Select Show keys, then select copy on the Connection string for key1.
Add a container
Select Go to resource, or in the left-hand menu of the Azure portal, select All Resources > mystorageaccount.
Under the Data storage section, select Containers.
Select + Container to create a new container.
Enter mycontainer in Name and select Private (no anonymous access) under Public access level.
Test connectivity to private endpoint
In this section, you'll use the virtual machine you created in the previous steps to connect to the storage account across the private endpoint using Microsoft Azure Storage Explorer.
Select Resource groups in the left-hand navigation pane.
On the overview page for myVM, select Connect then Bastion.
Enter the username and password that you entered during the virtual machine creation.
Select Connect button.
Open Windows PowerShell on the server after you connect.
nslookup <storage-account-name>.blob.core.windows.net. Replace <storage-account-name> with the name of the storage account you created in the previous steps. You'll receive a message similar to what is displayed below:
Server: UnKnown Address: 22.214.171.124 Non-authoritative answer: Name: mystorageaccount.privatelink.blob.core.windows.net Address: 10.1.0.5 Aliases: mystorageaccount.blob.core.windows.net
A private IP address of 10.1.0.5 is returned for the storage account name. This address is in mySubnet subnet of myVNet virtual network you created previously.
Install Microsoft Azure Storage Explorer on the virtual machine.
Select Finish after the Microsoft Azure Storage Explorer is installed. Leave the box checked to open the application.
In the Select Resource screen, select Storage account or service to add a connection in Microsoft Azure Storage Explorer to your storage account that you created in the previous steps.
In the Select Connection Method screen, select Connection string, and then Next.
In the box under Connection String, paste the connection string from the storage account you copied in the previous steps. The storage account name will automatically populate in the box under Display name.
Verify the settings are correct in Summary.
Select Connect, then select mystorageaccount from the Storage Accounts left-hand menu.
Under Blob Containers, you see mycontainer that you created in the previous steps.
Close the connection to myVM.
Clean up resources
If you're not going to continue to use this application, delete the virtual network, virtual machine, and storage account with the following steps:
From the left-hand menu, select Resource groups.
Select Delete resource group.
Enter myResourceGroup in TYPE THE RESOURCE GROUP NAME.
In this tutorial, you learned how to create:
- Virtual network and bastion host.
- Virtual machine.
- Storage account and a container.
Learn how to connect to an Azure Cosmos DB account using an Azure Private Endpoint:
Submit and view feedback for