Azure Networking Services

AZ-900 AZ-900 · Describe Azure architecture and services

By Abu Anns · Last updated 20 November 2026Exam version: AZ-900 (skills measured as of July 20, 2026)

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:

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

ServiceConnectsOverBest when
VNet peeringTwo Azure VNetsMicrosoft private backboneAzure networks need to talk to each other
VPN GatewayOn-premises ↔ AzurePublic internet, encryptedQuick, low-cost hybrid connection
ExpressRouteOn-premises ↔ AzurePrivate dedicated connectionHigh bandwidth, low latency, no public internet
Azure DNSDomain names ↔ IP addressesMicrosoft's name serversHosting DNS zones in Azure
Private endpointVNet ↔ Azure servicePrivate networkTraffic must stay off the internet
Advertisement

Exam traps to watch for

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

Q7.Which statement about an Azure virtual network (VNet) is correct?

Report an error

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?

Report an error