Private Link for secure service access in Azure - Mini Project: Build & Apply

Private Link for secure service access

📖 Scenario: You work for a company that wants to securely connect its virtual network to an Azure Storage Account without exposing the storage endpoint to the public internet. You will create a Private Endpoint using Azure Private Link to achieve this secure connection.

🎯 Goal: Build an Azure Private Endpoint to securely connect a virtual network to an Azure Storage Account using Private Link, ensuring traffic stays within the Microsoft backbone network.

📋 What You'll Learn

Create a resource group named rg-private-link-demo

Create a virtual network named vnet-demo with a subnet named subnet-demo

Create an Azure Storage Account named storagedemoprivatelink

Create a Private Endpoint named pe-storage in subnet-demo linked to the Storage Account

Configure the Private Endpoint with the correct private link service connection

💡 Why This Matters

🌍 Real World

Companies use Azure Private Link to keep their service traffic private and secure, avoiding exposure to the public internet.

💼 Career

Cloud engineers and architects often configure Private Link to meet security and compliance requirements for enterprise cloud deployments.

1

Create the resource group and virtual network

Create a resource group called rg-private-link-demo in the eastus region. Then create a virtual network called vnet-demo with address prefix 10.0.0.0/16 and a subnet called subnet-demo with address prefix 10.0.1.0/24 inside the resource group.

Azure

# Create resource group and virtual network with subnet
# Your code here

Hint

Use az group create to create the resource group and az network vnet create to create the virtual network with subnet.

2

Create the Azure Storage Account

Create an Azure Storage Account named storagedemoprivatelink in the resource group rg-private-link-demo with the Standard_LRS SKU and StorageV2 kind in the eastus location.

Azure

az group create --name rg-private-link-demo --location eastus
az network vnet create --resource-group rg-private-link-demo --name vnet-demo --address-prefix 10.0.0.0/16 --subnet-name subnet-demo --subnet-prefix 10.0.1.0/24
az network vnet subnet update --resource-group rg-private-link-demo --vnet-name vnet-demo --name subnet-demo --disable-private-endpoint-network-policies true
# Create the storage account
# Your code here

Hint

Use az storage account create with the specified parameters.

3

Create the Private Endpoint

Create a Private Endpoint named pe-storage in the resource group rg-private-link-demo inside the subnet subnet-demo of virtual network vnet-demo. Link this Private Endpoint to the Storage Account storagedemoprivatelink using the private link service connection for the blob service.

Azure

az group create --name rg-private-link-demo --location eastus
az network vnet create --resource-group rg-private-link-demo --name vnet-demo --address-prefix 10.0.0.0/16 --subnet-name subnet-demo --subnet-prefix 10.0.1.0/24
az network vnet subnet update --resource-group rg-private-link-demo --vnet-name vnet-demo --name subnet-demo --disable-private-endpoint-network-policies true
az storage account create --name storagedemoprivatelink --resource-group rg-private-link-demo --location eastus --sku Standard_LRS --kind StorageV2
# Create the private endpoint
# Your code here

Hint

Use az network private-endpoint create with the storage account resource ID and specify blob as the group ID.

4

Approve the Private Endpoint connection

Approve the Private Endpoint connection for pe-storage on the Storage Account storagedemoprivatelink by setting the connection status to Approved in the resource group rg-private-link-demo.

Azure

az group create --name rg-private-link-demo --location eastus
az network vnet create --resource-group rg-private-link-demo --name vnet-demo --address-prefix 10.0.0.0/16 --subnet-name subnet-demo --subnet-prefix 10.0.1.0/24
az network vnet subnet update --resource-group rg-private-link-demo --vnet-name vnet-demo --name subnet-demo --disable-private-endpoint-network-policies true
az storage account create --name storagedemoprivatelink --resource-group rg-private-link-demo --location eastus --sku Standard_LRS --kind StorageV2
az network private-endpoint create --name pe-storage --resource-group rg-private-link-demo --vnet-name vnet-demo --subnet subnet-demo --private-connection-resource-id $(az storage account show --name storagedemoprivatelink --resource-group rg-private-link-demo --query id -o tsv) --group-ids blob --connection-name pe-connection
# Approve the private endpoint connection
# Your code here

Hint

Use az network private-endpoint-connection approve with the correct parameters to approve the connection.

Practice

1. What is the main benefit of using Azure Private Link for service access?

easy

A. It allows secure access to Azure services using private IP addresses within your virtual network.

B. It provides public internet access to Azure services with encryption.

C. It automatically scales Azure services based on traffic.

D. It creates a VPN connection between on-premises and Azure.

Solution

1. Step 1: Understand Private Link purpose

   Private Link connects Azure services privately using private IPs inside your virtual network.

2. Step 2: Compare options

   Only It allows secure access to Azure services using private IP addresses within your virtual network. describes private, secure access using private IPs. Others describe different features.

3. Final Answer:

   It allows secure access to Azure services using private IP addresses within your virtual network. -> Option A

4. Quick Check:

   Private Link = Private IP secure access [OK]

Hint: Private Link means private IP inside your network [OK]

Common Mistakes:

• Confusing Private Link with VPN or public internet access
• Thinking Private Link automatically scales services
• Assuming Private Link creates a VPN

2. Which of the following is the correct way to create a Private Endpoint in Azure CLI?

easy

A. az storage account create --name MyPE --resource-group MyRG --location eastus

B. az network vnet create --name MyPE --resource-group MyRG --subnet MySubnet

C. az network private-endpoint create --name MyPE --resource-group MyRG --vnet-name MyVNet --subnet MySubnet --private-connection-resource-id /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Storage/storageAccounts/mystorage --group-ids blob

D. az network private-link create --name MyPE --resource-group MyRG

Solution

1. Step 1: Identify Private Endpoint creation command

   The correct Azure CLI command to create a Private Endpoint is az network private-endpoint create with required parameters.

2. Step 2: Verify parameters

   az network private-endpoint create --name MyPE --resource-group MyRG --vnet-name MyVNet --subnet MySubnet --private-connection-resource-id /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Storage/storageAccounts/mystorage --group-ids blob uses correct command and parameters including resource ID and group IDs for the service.

3. Final Answer:

   az network private-endpoint create with proper parameters -> Option C

4. Quick Check:

   Private Endpoint creation uses az network private-endpoint create [OK]

Hint: Private Endpoint uses 'az network private-endpoint create' command [OK]

Common Mistakes:

• Using vnet create instead of private-endpoint create
• Confusing storage account creation with Private Endpoint
• Using non-existent 'private-link create' command

3. Given this Azure CLI command output snippet for a Private Endpoint:

{
  "privateLinkServiceConnections": [
    {
      "name": "connection1",
      "privateLinkServiceId": "/subscriptions/abc/resourceGroups/rg1/providers/Microsoft.Network/privateLinkServices/pls1",
      "status": "Approved"
    }
  ]
}

What does the status "Approved" indicate?

medium

A. The Private Endpoint connection request is pending approval.

B. The Private Endpoint is deleted.

C. The Private Endpoint connection request was rejected.

D. The Private Endpoint connection request has been accepted and is active.

Solution

1. Step 1: Understand status field meaning

   The status "Approved" means the connection request was accepted and is active.

2. Step 2: Eliminate other options

   "Pending" means waiting, "Rejected" means denied, "Deleted" means removed. Only "Approved" means active connection.

3. Final Answer:

   The Private Endpoint connection request has been accepted and is active. -> Option D

4. Quick Check:

   Status Approved = Active connection [OK]

Hint: Approved status means connection is active [OK]

Common Mistakes:

• Confusing Approved with Pending or Rejected
• Assuming Approved means deleted or inactive
• Ignoring the status field meaning

4. You created a Private Endpoint but cannot access the Azure Storage account privately. Which of the following is a likely misconfiguration?

medium

A. The Private Endpoint subnet does not have network policies disabled for Private Link.

B. The Storage account is in the same region as the Private Endpoint.

C. The Private Endpoint has a valid approved connection status.

D. The virtual network has enough IP addresses.

Solution

1. Step 1: Check Private Endpoint subnet network policies

   For Private Link to work, the subnet must have network policies disabled to allow private IP traffic.

2. Step 2: Analyze other options

   Same region is normal, approved status is good, and enough IPs is required but less likely cause of access failure.

3. Final Answer:

   The Private Endpoint subnet does not have network policies disabled for Private Link. -> Option A

4. Quick Check:

   Subnet network policies must be disabled for Private Link [OK]

Hint: Disable subnet network policies for Private Link [OK]

Common Mistakes:

• Ignoring subnet network policies setting
• Assuming region mismatch causes access failure
• Overlooking connection status correctness

5. You want to securely connect your on-premises network to an Azure SQL Database using Private Link. Which combination of Azure components should you configure to achieve this?

hard

A. Create a Public Endpoint for Azure SQL Database and use firewall rules to restrict IPs.

B. Create a Private Endpoint for the Azure SQL Database in a virtual network, then connect your on-premises network to that virtual network via VPN or ExpressRoute.

C. Use Azure Bastion to connect to the Azure SQL Database securely.

D. Create a Virtual Network Gateway and connect directly to the Azure SQL Database without Private Endpoint.

Solution

1. Step 1: Understand Private Link for on-premises access

   Private Link requires a Private Endpoint in a virtual network to provide private IP access to Azure SQL Database.

2. Step 2: Connect on-premises to Azure VNet

   To access the Private Endpoint from on-premises, you must connect your on-premises network to the Azure virtual network using VPN or ExpressRoute.

3. Step 3: Evaluate other options

   Public Endpoint with firewall is less secure, Azure Bastion is for VM access, and Virtual Network Gateway alone doesn't provide Private Link.

4. Final Answer:

   Create a Private Endpoint for the Azure SQL Database in a virtual network, then connect your on-premises network to that virtual network via VPN or ExpressRoute. -> Option B

5. Quick Check:

   Private Endpoint + VPN/ExpressRoute = Secure on-premises access [OK]

Hint: Private Endpoint plus VPN/ExpressRoute connects on-premises securely [OK]

Common Mistakes:

• Using public endpoints instead of Private Link for security
• Confusing Azure Bastion with Private Link usage
• Assuming Virtual Network Gateway alone provides Private Link