Azure Private Link for Enterprise: Secure Private Connectivity Patterns and Implementation
Prerequisites
- Azure subscription with Contributor or Network Contributor permissions
- Working knowledge of VNets, DNS, and Azure CLI
Steps
Azure Private Link provides private, RFC1918-based access to Azure PaaS and partner services without exposing traffic to the public internet. This guide explains enterprise architecture patterns, deployment steps, CLI examples, security controls, and operational troubleshooting.
Overview
Azure Private Link enables private connectivity from virtual networks to Azure platform services, customer-owned services, and selected partner offerings by mapping a service to a private endpoint NIC in your VNet. Enterprises use it to reduce public exposure, enforce data exfiltration controls, simplify regulatory alignment, and keep application-to-service traffic on Microsoft backbone networks.
Key enterprise benefits:
- Private access to PaaS such as Azure Storage, Key Vault, SQL Database, and App Service
- Reduced attack surface by disabling public network access on supported services
- Segmentation-friendly design because access is scoped to approved VNets and subnets
- Predictable DNS-based routing through
privatelinkzones and private resolution paths
Architecture
Core components:
- Private Endpoint: An ENI with a private IP in a consumer VNet
- Private Link Service: Provider-side service exposure, commonly for custom apps behind Standard Load Balancer
- Private DNS Zone: Resolves service FQDNs to private endpoint IPs
- Consumer VNet / Provider VNet: Separate trust domains with explicit approval workflow
Typical deployment models:
- Single VNet: Workload and private endpoint in same VNet
- Hub-and-spoke: Shared DNS and inspection in hub, private endpoints in spokes or centralized endpoint subnet
- Cross-subscription / cross-tenant: Common in shared services and M&A scenarios
View as text
[User App Subnet] ---- 1. DNS query ----> [Private DNS Zone] [Private DNS Zone] ---- 2. A record reply ----> [User App Subnet] [User App Subnet] ---- 3. TCP 443 to private IP ----> [Private Endpoint NIC] [Private Endpoint NIC] ---- 4. Microsoft backbone ----> [Azure PaaS Service] [Security Team] ---- 5. policy / approval ----> [Private Endpoint] [Hub VNet DNS Forwarder] | v [On-Prem DNS] ---- 6. conditional forward ----> [Azure Private DNS]
Data flow summary:
- Client resolves the service FQDN.
- DNS returns a
privatelinkprivate IP. - Client connects over private IP inside the VNet.
- Traffic stays on Azure backbone to the target service.
Implementation Guide
- Create resource group and network.
az group create -n rg-privatelink-prod -l westeurope
az network vnet create -g rg-privatelink-prod -n vnet-app-prod --address-prefix 10.20.0.0/16 --subnet-name snet-app --subnet-prefix 10.20.1.0/24
az network vnet subnet create -g rg-privatelink-prod --vnet-name vnet-app-prod -n snet-pe --address-prefixes 10.20.2.0/24 --disable-private-endpoint-network-policies true
- Create a Storage account and disable public access.
az storage account create -g rg-privatelink-prod -n stplprod001 -l westeurope --sku Standard_LRS --kind StorageV2 --public-network-access Disabled --min-tls-version TLS1_2
- Create the private endpoint.
STORAGE_ID=$(az storage account show -g rg-privatelink-prod -n stplprod001 --query id -o tsv)
az network private-endpoint create -g rg-privatelink-prod -n pe-stplprod001 --vnet-name vnet-app-prod --subnet snet-pe --private-connection-resource-id "$STORAGE_ID" --group-id blob --connection-name peconn-stblob
- Create and link private DNS.
az network private-dns zone create -g rg-privatelink-prod -n privatelink.blob.core.windows.net
az network private-dns link vnet create -g rg-privatelink-prod -n link-vnet-app --zone-name privatelink.blob.core.windows.net --virtual-network vnet-app-prod --registration-enabled false
az network private-endpoint dns-zone-group create -g rg-privatelink-prod -n dzg-blob --endpoint-name pe-stplprod001 --private-dns-zone privatelink.blob.core.windows.net --zone-name blobzone
- Validate resolution and connectivity.
nslookup stplprod001.blob.core.windows.net
az network private-endpoint show -g rg-privatelink-prod -n pe-stplprod001 --query 'customDnsConfigs[].ipAddresses'
curl -I https://stplprod001.blob.core.windows.net/
Code Examples
Example 1: Bash validation script
fqdn="stplprod001.blob.core.windows.net"
expected_subnet="10.20.2.0/24"
resolved_ip=$(getent ahostsv4 $fqdn | awk 'NR==1{print $1}')
echo "Resolved $fqdn to $resolved_ip"
ipcalc -c "$resolved_ip" "$expected_subnet" && echo "Private Link resolution OK"
Example 2: Azure Policy assignment parameters
{
"properties": {
"displayName": "Deny public network access for Storage",
"policyDefinitionId": "/providers/Microsoft.Authorization/policyDefinitions/34c877ad-507e-4c82-993e-3452a6e0ad3c",
"parameters": {}
}
}
Example 3: Terraform private endpoint
resource "azurerm_private_endpoint" "blob" {
name = "pe-stplprod001"
location = azurerm_resource_group.rg.location
resource_group_name = azurerm_resource_group.rg.name
subnet_id = azurerm_subnet.pe.id
private_service_connection {
name = "peconn-stblob"
private_connection_resource_id = azurerm_storage_account.sa.id
subresource_names = ["blob"]
is_manual_connection = false
}
}
Security Hardening
- Disable public network access on supported PaaS resources after private endpoint validation
- Use NSGs carefully: NSGs apply to source subnets, not to the managed service itself; control east-west access to endpoint consumers
- Enforce TLS 1.2+ and service-native encryption with customer-managed keys where required
- Restrict DNS changes using RBAC and change control for private zones
- Use Azure Policy to audit or deny public endpoints and require approved private endpoint patterns
- Monitor with NSG flow logs, Azure Monitor, and Defender for Cloud for anomalous access attempts
Comparison
| Feature | Azure Private Link | AWS PrivateLink | Google Cloud Private Service Connect |
|---|---|---|---|
| Pricing model | Per private endpoint/hour + inbound/outbound data processing | Per interface endpoint/hour + data processing | Forwarding rule and data processing charges |
| Deployment | Native across many Azure PaaS services and custom services via Private Link Service | Strong AWS service coverage and SaaS integrations | Strong GCP service publishing and consumer patterns |
| Scalability | Enterprise-ready with hub-spoke and cross-subscription support | Highly scalable within AWS regional constructs | Scalable for producer-consumer service publishing |
| Security | Tight integration with Azure Policy, Private DNS, public access disablement | Mature IAM and endpoint policies | Strong service attachment controls and VPC design |
Troubleshooting
Error 1: DNS resolves to public IP
Log sample:
$ nslookup stplprod001.blob.core.windows.net
Non-authoritative answer:
Name: stplprod001.blob.core.windows.net
Address: 20.60.41.132
Fix: Link the correct private DNS zone to the VNet and verify conditional forwarding from on-prem DNS to Azure DNS forwarders.
Error 2: Private endpoint connection pending approval
Log sample:
{
"privateLinkServiceConnectionState": {
"status": "Pending",
"description": "Awaiting approval from resource owner"
}
}
Fix: Approve the connection on the provider resource or use auto-approval within the same tenant when supported.
Error 3: Application timeout to service
Log sample:
2026-11-19T10:14:22Z ERROR storage_client request failed: dial tcp 10.20.2.4:443: i/o timeout
Fix: Confirm route symmetry, source subnet NSG egress on 443, and that the target subresource matches the endpoint group such as blob, sqlServer, or vault.
Best Practices
Do:
- Centralize DNS design in hub-and-spoke environments with tested forwarders
- Create separate endpoint subnets for lifecycle clarity and IP planning
- Document subresource mappings like Storage
blob,file,queue,table - Pair Private Link with public access disablement for strong exfiltration control
Don't:
- Assume one endpoint covers all subresources; Storage often needs multiple endpoints
- Break name resolution during migration; validate split-horizon DNS before cutover
- Over-centralize without governance; shared endpoint services need ownership, approval, and monitoring models
Have a project in mind?
Get an instant AI price estimate for it, or talk directly to our team.
One email a month on what we learn building with AI