Azure Networking Services
AZ-900 AZ-900 · Describe Azure architecture and services
Virtual networks: your private network in Azure
An Azure virtual network (VNet) is the fundamental networking building block in Azure: an isolated, private network in the cloud where your resources — virtual machines, web apps, databases — communicate with each other, with the internet, and with your on-premises network. Think of a VNet as your own datacenter network, recreated in Azure: you define its address space (a private IP range such as 10.0.0.0/16), and every resource you place in it gets an address from that space. Resources in the same VNet communicate privately by default; traffic to the outside world goes through controlled exits.
VNets are divided into subnets — smaller address ranges within the VNet — so you can organise and secure resources by tier: web servers in one subnet, application servers in another, databases in a third. Subnets let you apply different security rules per tier (for example, only the application subnet may reach the database subnet) using network security groups. The exam expects you to know that a VNet is scoped to one region, and that subnets are how you segment it.
Connecting networks together
Three services connect networks, and the exam tests which one fits each situation:
- VNet peering connects two virtual networks in Azure so resources in each can communicate directly, as if they were one network. Traffic between peered VNets stays on Microsoft's private backbone network — it never crosses the public internet — and the connection is low-latency and high-bandwidth. Peering can join VNets in the same region or in different regions (global peering), and in the same or different subscriptions. Use it when two Azure networks need to talk to each other.
- Azure VPN Gateway connects an on-premises network to Azure over the public internet through an encrypted tunnel. It supports site-to-site VPN (an entire office network) and point-to-site VPN (individual devices). VPN Gateway is quick to set up and inexpensive, but bandwidth is limited and latency depends on the internet. Use it for smaller or temporary hybrid connections, or when a private connection is not justified.
- Azure ExpressRoute connects an on-premises network to Azure over a private, dedicated connection provided by a connectivity partner — traffic never touches the public internet. ExpressRoute offers higher bandwidth, lower and more predictable latency, and stronger reliability than a VPN, at a higher price and with a longer setup time. Use it when a company needs a private, high-bandwidth, predictable connection — for example, moving large volumes of data regularly, or meeting compliance rules that forbid sending traffic over the internet.
The exam's classic networking question gives you a requirement — "private connection, not over the internet" — and expects ExpressRoute, or "quick, encrypted connection over the internet" and expects VPN Gateway. The distinguishing words are private/dedicated versus encrypted over the internet.
Azure DNS
Azure DNS hosts DNS domains in Azure: it resolves domain names (such as www.example.com) to IP addresses, using Microsoft's global network of name servers for fast, reliable lookups. Organisations use it to manage their public DNS records alongside their Azure resources, and to host private DNS zones that resolve names inside a virtual network. If a question asks which service hosts a domain's DNS records in Azure, the answer is Azure DNS — not a virtual network, not a VPN, and not ExpressRoute.
Public and private endpoints
Every Azure service can be reached somehow, and the endpoint type decides how. A public endpoint is an address reachable over the public internet — a public IP address on a VM, or the public URL of a storage account. Public endpoints are convenient and are the default for many services, but they are exposed to the internet and must be protected with authentication, firewalls, and access controls. A private endpoint gives an Azure service a private IP address inside your virtual network, so traffic to that service travels over the private network and never crosses the internet — for example, a VM in a VNet reaching a storage account through a private IP. Private endpoints are the answer whenever a scenario requires that traffic to a service stay off the public internet.
Worked example: connecting a hybrid company
A company runs its main systems on-premises and is moving its web tier to Azure. The web servers in Azure must reach the on-premises database securely, and the company moves large amounts of data between the two every night. Two decisions follow. First, the connection: the volume and the need for predictable performance point to ExpressRoute rather than a VPN — a VPN would work, but the nightly bulk transfer and the latency requirement make the private connection the right fit. Second, the database access: the web servers reach the on-premises database through the ExpressRoute connection, and the Azure-side storage uses private endpoints so that no data crosses the public internet at any point. If the budget were smaller and the data volumes lower, the same design with a VPN Gateway would be the right answer instead — the exam rewards matching the service to the requirement, not memorising that one is "better".
Securing the network: two supporting concepts
Two further networking concepts support the exam's scenarios, even though the objectives do not name them as headline topics. Network security groups (NSGs) are the firewalls of the virtual network: rule lists attached to subnets or network interfaces that allow or deny traffic by source, destination, port, and protocol. A typical design allows web traffic (port 443) to the web subnet, allows only the web subnet to reach the application subnet, and allows only the application subnet to reach the database subnet — the network layer of defense in depth, applied with NSG rules. Azure DDoS Protection defends against distributed denial-of-service attacks that try to overwhelm a service with traffic; every Azure property gets basic, always-on network-level protection, and the paid Network Protection tier adds attack analytics, mitigation policies tuned to your resources, and cost protection. When a scenario mentions filtering traffic between subnets, think NSGs; when it mentions defending against volumetric attacks, think DDoS Protection.
Quick comparison
| Service | Connects | Over | Best when |
|---|---|---|---|
| VNet peering | Two Azure VNets | Microsoft private backbone | Azure networks need to talk to each other |
| VPN Gateway | On-premises ↔ Azure | Public internet, encrypted | Quick, low-cost hybrid connection |
| ExpressRoute | On-premises ↔ Azure | Private dedicated connection | High bandwidth, low latency, no public internet |
| Azure DNS | Domain names ↔ IP addresses | Microsoft's name servers | Hosting DNS zones in Azure |
| Private endpoint | VNet ↔ Azure service | Private network | Traffic must stay off the internet |
Exam traps to watch for
- Choosing VPN Gateway when the scenario says 'private connection, not over the internet'. That phrase means ExpressRoute; VPN traffic crosses the public internet (encrypted).
- Using VNet peering to connect on-premises to Azure. Peering connects two Azure virtual networks; on-premises connections use VPN Gateway or ExpressRoute.
- Confusing public and private endpoints. A public endpoint is reachable over the internet; a private endpoint gives a service a private IP inside your VNet.
- Forgetting that a VNet is scoped to one region. Resources in different regions need separate VNets (connected by global peering if they must communicate).
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company needs to connect its on-premises datacenter to Azure with a private, dedicated connection that never crosses the public internet, with predictable low latency for large nightly data transfers. Which service should it use?
Explanation: ExpressRoute is a private dedicated connection between on-premises and Azure that never uses the public internet, with high bandwidth and predictable latency. VPN Gateway traffic crosses the public internet (encrypted). VNet peering connects two Azure VNets, not on-premises to Azure. Azure DNS hosts domain name records; it does not connect networks.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
Q2.A company has two virtual networks in Azure in different regions. Resources in each network must communicate directly with low latency, without traffic crossing the public internet. What should the company configure?
Explanation: VNet peering (global peering across regions) connects two Azure VNets so resources communicate directly over Microsoft's private backbone. ExpressRoute connects on-premises to Azure, not two VNets. VPN Gateways would send traffic over the internet. A private endpoint connects a VNet to an Azure service, not two VNets to each other.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
Q3.A small company wants to connect its office network to Azure quickly and cheaply, with encrypted traffic. Bandwidth needs are modest. Which service fits best?
Explanation: VPN Gateway connects on-premises to Azure over the public internet through an encrypted tunnel — quick to set up and inexpensive, which matches a small company's needs. ExpressRoute is a private dedicated connection: more expensive and slower to provision, overkill for modest needs. Azure DNS hosts DNS records. VNet peering connects Azure VNets, not an office to Azure.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
Q4.A company hosts its website's DNS records in Azure so that domain names resolve to its web servers using Microsoft's global name servers. Which service is it using?
Explanation: Azure DNS hosts DNS domains and resolves names to IP addresses using Microsoft's name servers. VPN Gateway and ExpressRoute are connectivity services, not DNS. Azure Private Link is the underlying technology for private endpoints, not a DNS hosting service.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
Q5.A virtual machine in a VNet needs to access an Azure storage account, and company policy requires that the traffic never crosses the public internet. What should be configured for the storage account?
Explanation: A private endpoint gives the storage account a private IP address inside the VNet, so traffic stays on the private network. A public endpoint is reachable over the internet by definition, even with a firewall. A VPN Gateway connects on-premises networks, not a VM to a storage account. ExpressRoute connects on-premises to Azure; it does not give a storage account a private IP in a VNet.
Exam objective: AZ-900 Describe Azure compute and networking services: define public and private endpoints
Q6.A company organises its virtual network into three segments: one for web servers, one for application servers, and one for databases, each with different security rules. What are these segments called?
Explanation: Subnets are smaller address ranges within a VNet, used to organise and secure resources by tier with different rules per subnet. Availability zones are physically separate datacenters in a region. Resource groups and management groups are management hierarchy containers, not network segments.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
Q7.Which statement about an Azure virtual network (VNet) is correct?
Explanation: A VNet is scoped to one region; resources in different regions need separate VNets. A VNet holds many resource types (VMs, app services, databases, gateways), not only VMs. It is a logical isolated network in the cloud, not a physical building.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
Q8.A company is choosing between VPN Gateway and ExpressRoute. Its compliance policy forbids sending company data over the public internet in any form. Which option must it choose, and why?
Explanation: ExpressRoute uses a private dedicated connection that never touches the public internet, which is what the policy requires. VPN Gateway traffic is encrypted but still crosses the public internet, so it fails the policy. The two are not equivalent on this point, and Azure can meet the requirement through ExpressRoute.
Exam objective: AZ-900 Describe Azure compute and networking services: describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute