L8. Private Endpoints & Service Endpoints
Course outlineLesson 8 of 18
Choose private or service endpoints by network requirements, verify DNS from each client and configure public access separately from private connectivity.
Course context: AZ-500 retired on August 31, 2026. Use these Azure security concepts for operational practice and continue with the current SC-500 course for certification preparation.
Service Endpoints vs Private Endpoints
| Property | Service endpoint | Private endpoint |
|---|---|---|
| Service destination | Public service endpoint over Azure backbone | Private IP on a NIC in your VNet |
| Source identity | Subnet identity and private source IP | Private connectivity to the selected resource |
| DNS | Public service resolution | Resolution to the endpoint's private IP |
| On-premises private connectivity | Does not extend service endpoints to on-premises | VPN or ExpressRoute with working DNS and routing |
Configure Private DNS
For Azure Blob Storage, use privatelink.blob.core.windows.net. Link the private DNS zone to the client VNet and associate the endpoint with a DNS zone group, or maintain the required A record yourself. Custom DNS and on-premises clients need an appropriate forwarding or resolver design.
A private DNS zone is a common solution, not the only supported DNS design. Verify that the normal storage hostname resolves to the private endpoint IP from each client network. If it still resolves publicly, access follows public network rules and can fail when public access is disabled.
Choose the Access Pattern
Use a service endpoint when subnet rules on a public service endpoint meet the requirement. Regional scope depends on the service: Storage supports cross-region connectivity through Microsoft.Storage.Global. Do not apply a universal same-region rule.
Use private endpoints for resource-specific private connectivity, including hybrid clients. Creating a private endpoint does not automatically disable public access. Configure that separately.
Disable Public Access Deliberately
For Storage, disabling public network access blocks normal public endpoint access, including service endpoint traffic. Private endpoints continue to work. Review trusted-service and resource-instance exceptions too: previously configured exceptions can remain effective. DNS, network access and data authorization are separate checks.
References
- Service endpoints
- Private endpoint DNS
- Storage firewall limitations and exceptions
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓Service endpoints use the public service destination over the backbone, with private source IPs and subnet identity
- ✓Private endpoints provide a private IP; configure and verify DNS resolution from every client network
- ✓On-premises clients can use private endpoints through VPN or ExpressRoute with working routing and DNS
- ✓Creating a private endpoint does not disable public access; review public access settings and existing exceptions separately
- ✓Blob Storage uses privatelink.blob.core.windows.net; service endpoint regional behavior varies by service
1. A Blob Storage private endpoint has an A record in its private DNS zone, linked to the VM VNet and used by the VM resolver. What does 'mystorageaccount.blob.core.windows.net' resolve to?
2. What is the key difference between a Service Endpoint and a Private Endpoint?
3. Which private DNS zone name does Microsoft document for Azure Blob Storage private endpoints?