M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Virtual network service endpoints

Concept

An Azure Virtual Network feature that restricts access to Azure services so only traffic from a chosen virtual network subnet is allowed, while the service keeps its public endpoint.

✦ CONCEPTVirtual network serviceendpointsM365.FM
Title graphic: Virtual network service endpoints (Concept)

Also discussed

The episode about Virtual network service endpoints also covers Azure Blob Storage, Azure ExpressRoute, Azure Load Balancer, Azure Private Link, Network security group (NSG) and Azure Virtual Network.

Description

Virtual network service endpoints are an Azure Virtual Network feature that restricts access to certain Azure services so that only traffic from a chosen virtual network subnet is allowed. The service keeps its public endpoint, but a rule on the service limits who may use it. In practice, resources in the subnet reach the service over the Azure backbone network, and the service can be locked down so that the public internet no longer has access to it.

The feature is used when workloads in a virtual network need to talk to platform services such as storage or databases while the service itself should not be reachable from everywhere. According to the Microsoft Learn overview, the supported services include Storage, SQL Database, Cosmos DB, Key Vault, Service Bus, Event Hubs, App Service and Container Registry. Resources in the subnet can use these services without public IP addresses of their own.

The setup has two parts. First, the endpoint is enabled on a subnet for a given service. Endpoints are switched on per subnet and per service, and several services can be combined on one subnet. Second, a virtual network rule is configured on the target service so that access is limited to that network. Enabling the endpoint requires a special permission on the subnet, and no extra charge applies for the feature itself.

Several related building blocks interact with service endpoints. Service tags can be used in network security groups to allow or deny traffic to the relevant services. Service endpoint policies filter access to specific resources of a service rather than the whole service. Routing is also affected: routes with the next hop type VirtualNetworkServiceEndpoint take precedence over BGP routes and user-defined routes. One visible side effect is that the source address of traffic changes from a public IP address to the private IPv4 address of the virtual network, which matters for firewall rules that were written against the old public address.

There are limits to keep in mind when deciding on this approach. Service endpoints do not cover traffic coming from on-premises networks. DNS records for the service still resolve to public addresses, because the service keeps its public endpoint. For these reasons, Microsoft recommends Private Link and private endpoints as the preferred option, with service endpoints remaining a simpler alternative for subnet-level access control.

The topic appears in two M365.FM episodes. In "Azure Virtual Network - Simply Explained", the episode lists virtual network service endpoints among the features that support secure internal communication, describing them as extending the private address space of a virtual network to Azure services and securing them within the VNet. It places them alongside virtual network peering, which connects multiple VNets, and network security groups, which apply stateful rules to filter traffic. In "Microsoft Foundry AI Apps with Jannik Reinhard [MVP]", the episode names virtual network service endpoints together with Azure Firewall as network security features that help shield AI applications from external threats, as part of a broader layered security picture that also covers identity, encryption and threat detection.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
DocumentationVirtual network service endpoints – Microsoft Learn learn.microsoft.com

Episodes about Virtual network service endpoints

Episodes in which Virtual network service endpoints is discussed:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What do virtual network service endpoints do? (AI)

They let a chosen subnet reach selected Azure services over the Azure backbone, and a virtual network rule on the service restricts access to that network. The service keeps its public endpoint.

Do service endpoints cover traffic from on-premises networks? (AI)

No. According to the Microsoft Learn overview, endpoints do not cover traffic from on-premises, and DNS records for the service still resolve to public addresses.

Are service endpoints or private endpoints preferred? (AI)

Microsoft recommends Private Link and private endpoints as the preferred option. Service endpoints are enabled per subnet and per service and carry no extra charge.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: