Azure Private Link for Enterprise: Secure Private Access to PaaS and Partner Services
Prerequisites
- Azure subscription with Contributor or Network Contributor access
- Working knowledge of Azure VNets, DNS, and target PaaS services
Steps
Azure Private Link enables private connectivity from Azure virtual networks to Azure PaaS, customer-owned, and partner services without exposing traffic to the public internet. This guide explains enterprise architecture patterns, implementation steps, hardening controls, and troubleshooting practices for production deployments.
Overview
Azure Private Link provides private IP-based access to supported Azure services, Private Link Service endpoints, and selected SaaS offerings through a Private Endpoint placed inside your virtual network. Enterprises adopt it to reduce public exposure, enforce data exfiltration controls, simplify segmentation, and meet compliance requirements while preserving service-native management planes.
Typical use cases include accessing Azure Storage, Key Vault, SQL Database, App Service, AKS API server, and partner platforms over private addressing. Unlike service endpoints, Private Link maps a specific service resource to a NIC in your VNet and supports cross-subscription and cross-tenant approval workflows.
Architecture
Core components:
- Consumer VNet/Subnet: hosts workloads and private endpoints.
- Private Endpoint: network interface with a private IP in the consumer subnet.
- Private Link resource: Azure PaaS resource or provider-published
Private Link Service. - Private DNS Zone: resolves service FQDNs to private IPs.
- Hub-and-spoke or shared services DNS: centralizes name resolution across estates.
Common deployment models:
- Single VNet: simplest pattern for isolated applications.
- Hub-and-spoke: private endpoints in spoke VNets, DNS forwarded through hub resolvers.
- Centralized endpoint VNet: used cautiously when multiple apps share access paths and DNS is tightly governed.
View as text
[User Workload VM] ---- 1. DNS query ----> [Private DNS Zone] [Private DNS Zone] ---- 2. A record ----> [10.10.2.4] [User Workload VM] ---- 3. TCP 443 ----> [Private Endpoint NIC] [Private Endpoint NIC] ---- 4. Microsoft backbone ----> [Azure Storage Account] [Platform Admin] ---- 5. ARM control plane ----> [Azure Resource Manager]
Data flow:
- Client resolves the public service FQDN.
- DNS returns the private endpoint IP through a linked private zone.
- Traffic stays on the Microsoft backbone to the target service.
- Public network access can then be disabled on the service resource.
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-prefixes 10.10.0.0/16 --subnet-name snet-app --subnet-prefixes 10.10.1.0/24
az network vnet subnet create -g rg-privatelink-prod --vnet-name vnet-app-prod -n snet-private-endpoints --address-prefixes 10.10.2.0/24 --disable-private-endpoint-network-policies true
- Create a Storage account and disable public access after validation.
az storage account create -g rg-privatelink-prod -n stpldemo001 --sku Standard_LRS --kind StorageV2 --public-network-access Enabled
- Create Private DNS zone and link it to the VNet.
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-blob-prod -z privatelink.blob.core.windows.net -v /subscriptions/<subId>/resourceGroups/rg-privatelink-prod/providers/Microsoft.Network/virtualNetworks/vnet-app-prod -e false
- Create the private endpoint.
ST_ID=$(az storage account show -g rg-privatelink-prod -n stpldemo001 --query id -o tsv)
az network private-endpoint create -g rg-privatelink-prod -n pe-stpldemo001-blob -vnet-name vnet-app-prod -snet snet-private-endpoints --private-connection-resource-id $ST_ID --group-id blob --connection-name conn-stpldemo001-blob
- Create DNS zone group so records are managed automatically.
az network private-endpoint dns-zone-group create -g rg-privatelink-prod --endpoint-name pe-stpldemo001-blob -n zg-blob --private-dns-zone privatelink.blob.core.windows.net --zone-name blob-zone
- Validate resolution and connectivity, then disable public access.
nslookup stpldemo001.blob.core.windows.net
az storage account update -g rg-privatelink-prod -n stpldemo001 --public-network-access Disabled
Code Examples
az network private-endpoint show -g rg-privatelink-prod -n pe-stpldemo001-blob --query '{ip:customDnsConfigs[0].ipAddresses[0],fqdn:customDnsConfigs[0].fqdn,provisioningState:provisioningState}' -o json
apiVersion: v1
kind: ConfigMap
metadata:
name: app-config
data:
STORAGE_ACCOUNT_FQDN: "stpldemo001.blob.core.windows.net"
HTTPS_ONLY: "true"
DNS_EXPECTED_ZONE: "privatelink.blob.core.windows.net"
import socket, ssl
host = "stpldemo001.blob.core.windows.net"
ip = socket.gethostbyname(host)
print(f"resolved_ip={ip}")
ctx = ssl.create_default_context()
with socket.create_connection((host, 443), timeout=5) as sock:
with ctx.wrap_socket(sock, server_hostname=host) as tls:
print(f"tls_version={tls.version()} cipher={tls.cipher()[0]}")
Security Hardening
- Disable public network access on supported services after private validation.
- Use NSGs carefully: private endpoints ignore NSG rules for the endpoint itself, but source subnets still need egress governance.
- Restrict DNS changes with RBAC and Azure Policy; incorrect DNS is the most common operational failure.
- Encrypt data at rest and in transit: use service-managed or customer-managed keys, and enforce TLS 1.2+.
- Apply least privilege: separate network, DNS, and application roles; require approval workflows for cross-tenant private endpoint connections.
- Monitor with Azure Monitor, NSG flow logs where applicable, and Defender for Cloud recommendations.
Comparison
| Feature | Azure Private Link | AWS PrivateLink | Google Cloud Private Service Connect |
|---|---|---|---|
| Pricing model | Private endpoint hourly + inbound/outbound data processing | Interface endpoint hourly + data processing | Forwarding rule/NAT related charges + data processing |
| Deployment | Native across many Azure PaaS services and partner services | Strong for AWS services and SaaS integrations | Strong for Google APIs and service publishing |
| Scalability | Enterprise-ready, zone-aware patterns, cross-subscription support | Mature regional scale, broad service ecosystem | Good scalability, especially for Google service publishing |
| Security | Private IP mapping, approval workflow, public access disablement | Private ENI-based access, policy controls | Private consumer-producer connectivity with granular publishing |
Troubleshooting
- DNS resolves to public IP
$ nslookup stpldemo001.blob.core.windows.net
Name: stpldemo001.blob.core.windows.net
Address: 20.60.44.132
Fix: ensure the VNet is linked to privatelink.blob.core.windows.net and the private endpoint has a DNS zone group.
- Connection approved state missing
{"status":"Pending","description":"Awaiting approval from resource owner","privateEndpointConnection":{"id":"/subscriptions/.../privateEndpointConnections/conn-stpldemo001-blob"}}
Fix: approve the connection on the provider resource or verify auto-approval conditions within the same tenant and subscription scope.
- Application timeout after public access disabled
2026-11-18T09:14:22Z ERROR storage_client request_id=7f3c9d2b connect_timeout host=stpldemo001.blob.core.windows.net:443 errno=110 message="Connection timed out"
Fix: verify route symmetry, custom DNS forwarders, and that the workload subnet can reach Azure DNS or your conditional forwarder path.
Best Practices
Do:
- Place private endpoints in dedicated subnets such as
snet-private-endpoints. - Standardize private DNS through hub resolvers and conditional forwarding.
- Use Azure Policy to deny creation of public network access for sensitive services.
- Document service-specific subresources like
blob,sqlServer, orvault.
Don't:
- Reuse one endpoint subnet for unrelated trust zones.
- Disable public access before validating DNS and application connectivity.
- Assume on-premises clients will resolve private zones without DNS forwarding.
- Treat Private Link as a replacement for identity controls; still enforce Entra ID, RBAC, and service firewalls where supported.
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