The official Microsoft Certified: Azure Network Engineer Associate syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Design and implement IP addressing for Azure resources
Every virtual network you plan to connect to other networks or to on-premises needs a non-overlapping address space, and Azure reserves five addresses in each subnet (the first four and the last). You can extend or shrink a range while it still contains its subnets; in a peered network, every range change requires a peering sync.
Create, change, or delete an Azure virtual network ↗Update the address space for a peered virtual network ↗
A virtual network belongs to a single region and subscription, and resources that connect to it must be in the same region; for another region you create another network and peer it. When you create it you define one or more non-overlapping CIDR ranges (RFC 1918, RFC 6598 or your own public ranges), never link-local, multicast, loopback or 168.63.129.16.
Create, change, or delete an Azure virtual network ↗Azure Virtual Network FAQ ↗
Several services require subnets with a reserved name and no other resources: GatewaySubnet for virtual network gateways, AzureFirewallSubnet (and AzureFirewallManagementSubnet when the management NIC is enabled) for Azure Firewall, and AzureBastionSubnet for Azure Bastion. Application Gateway uses a dedicated subnet with a name you choose, while private and service endpoints are configured on ordinary subnets.
Azure VPN Gateway configuration settings ↗Azure Application Gateway infrastructure configuration ↗
Subnet delegation gives a PaaS service permission to create its resources in a specific subnet, for example Microsoft.Sql/managedInstances or Microsoft.Web/serverFarms. The owner can still apply NSGs and routes, but a delegated subnet doesn't support private endpoints, and the delegation can't be removed while resources of the service are deployed.
Subnet Delegation in Azure Virtual Network ↗Add or Remove Subnet Delegation in Azure Virtual Network ↗
Some services require a dedicated subnet that can hold only their own resources (Route Server, SQL Managed Instance, Application Gateway, gateways in GatewaySubnet), while virtual machines, network virtual appliances and private endpoints can share a subnet. In a shared subnet, NSGs affect private endpoints only when their network policy is enabled.
Azure Virtual Network Integration for Service Network Isolation ↗Manage network policies for private endpoints ↗
A public IP address prefix reserves a contiguous range of Azure addresses in one region and subscription, and it can be zone-redundant or zonal. Its size can't be changed later; you create static Standard public IP addresses from the prefix and associate them with resources, and a prefix can't be deleted while any of its addresses is associated.
Quickstart: Create a public IP address prefix - Azure CLI ↗Azure Public IP address prefix ↗
A prefix is the right choice when you need public addresses from a known range: allowlists with a single rule, many virtual machines, or scaled outbound traffic from a NAT gateway or Standard load balancer. Addresses you delete return to the reserved range; Azure Firewall uses only individual addresses from the prefix, and a load balancer uses the prefix only for outbound traffic.
A custom IP prefix (BYOIP) brings a public range that you keep owning to Azure in three phases: validation (a ROA at the registry and a signed message), provisioning and commissioning. Public IP prefixes and Standard addresses are derived from it, it's never attached directly to a resource, and regional commissioning without internet advertisement eases the migration of an active range.
Custom IP address prefix (BYOIP) ↗Manage a custom IP address prefix ↗
New public IP addresses use the Standard SKU (Basic was retired): static, closed to inbound traffic unless an NSG allows it, and zonal or zone-redundant. When you create one you choose IPv4 or IPv6, the regional or Global tier (for cross-region load balancers) and the routing preference, which can't be changed later; the DNS name label is optional.
Public IP addresses in Azure ↗Quickstart: Create a public IP - Azure CLI ↗
A public IP address is associated with the IP configuration of a VM network interface or with the frontend of resources such as load balancers, gateways, Azure Firewall or Bastion, always in the same region and subscription, although it can be in another resource group. Standard addresses are closed to inbound traffic until an NSG allows it, and they must be dissociated before deletion.
Associate a public IP address to a virtual machine ↗Create, change, or delete an Azure public IP address ↗
Design and implement name resolution
Inside a virtual network you can use Azure-provided resolution (no configuration, scoped to that network), Azure Private DNS zones (the preferred option), Azure DNS Private Resolver, or your own DNS servers that forward to 168.63.129.16. Azure-managed reverse DNS is scoped to each network; to span several, you use an in-addr.arpa private zone with manually managed PTR records.
The DNS servers setting of a virtual network can be Default (Azure-provided) or a list of custom servers, which are used in order and not round-robin. The DNS setting of a NIC overrides the network setting, and after any change existing VMs must renew their DHCP lease or restart to apply it.
Create, change, or delete an Azure virtual network ↗Azure Virtual Network Name Resolution Guide ↗
A public Azure DNS zone hosts the records of a domain and is published by delegating the domain to its four name servers at the registrar; subdomains are delegated with an NS record set in the parent zone. A CNAME can't exist at the apex, so alias records are used, which also follow the life cycle of public IPs or Traffic Manager profiles and prevent dangling records.
Alias records overview - Azure DNS ↗Delegate a subdomain - Azure DNS ↗
An Azure Private DNS zone is a global resource that resolves names only for linked virtual networks, in any region and without peering. It supports split-horizon with a public zone of the same name; autoregistration creates A records only for VMs and each network can have a single registration zone, so other resources are added manually.
Azure Private DNS: Secure DNS for Virtual Networks ↗Scenarios for Azure Private DNS zones ↗
Public zones are created with az network dns zone create and private zones with az network private-dns zone create; records use relative names and are grouped into record sets by name and type, with one TTL per set. A public zone is published by updating the NS records at the registrar with its name servers, and a private zone resolves only from linked virtual networks.
DNS Zones and Records Overview ↗Quickstart - Create an Azure private DNS zone using the Azure CLI ↗
A virtual network resolves a private DNS zone only if it's linked to it; peering isn't enough. With autoregistration the VNet becomes a registration network: each VNet has one registration zone but can have many resolution zones. Autoregistration only creates A records for the primary NIC of VMs, and disabling it deletes the records it created.
What is a virtual network link? ↗What is the autoregistration feature in Azure DNS private zones? ↗
Azure DNS Private Resolver removes the need for DNS server VMs. The inbound endpoint gives an IP that on-premises conditional forwarders target to resolve private zones; the outbound endpoint forwards Azure queries according to a ruleset linked to each virtual network. Each endpoint uses its own subnet delegated to Microsoft.Network/dnsResolvers, and the rule with the longest suffix wins.
What is Azure DNS Private Resolver? ↗Azure DNS Private Resolver endpoints and rulesets ↗
Design and implement VNet connectivity and routing
Service chaining steers traffic from a spoke to an NVA or a VPN gateway in a peered network by using user-defined routes. Gateway transit is enabled on the hub side and use remote gateways on the spoke, which then can't have its own gateway. You can't route between virtual networks with a UDR whose next hop is an ExpressRoute gateway.
Azure virtual network peering ↗Configure VPN gateway transit for virtual network peering ↗
Peering connects virtual networks in the same or different regions over the Microsoft backbone. It needs nonoverlapping address spaces and a peering on each network: the first stays Initiated until the reciprocal one exists. It isn't transitive, doesn't resolve names with default Azure DNS, and must be deleted before you move the virtual network.
Create, change, or delete Azure virtual network peering ↗Azure virtual network peering ↗
Azure Virtual Network Manager collects virtual networks into network groups, with static membership or dynamic membership through Azure Policy, and applies mesh or hub-and-spoke connectivity configurations to them. Direct connectivity builds a regional connected group that global mesh extends across regions. Nothing takes effect until deployed per region, and each deployment sets that region's goal state.
Connectivity configurations in Azure Virtual Network Manager ↗Manage configuration deployments in Azure Virtual Network Manager ↗
User-defined routes live in a route table and override system routes. They support the VirtualAppliance, VirtualNetworkGateway (VPN gateway only), VnetLocal, Internet and None next hop types, and they can use service tags as the address prefix. An NVA used as a next hop needs IP forwarding enabled on its NIC and should sit in a different subnet to avoid loops.
A route table is associated with subnets, never with the virtual network, and each subnet can have at most one. It can be associated only with subnets in the same location and subscription as the table, and it can't be deleted while associated. Don't associate a table with 0.0.0.0/0 to GatewaySubnet when there's a VPN gateway; after dissociation the subnet uses default routes.
Forced tunneling sends internet-bound traffic to on-premises for inspection. With site-to-site VPN it's configured by advertising 0.0.0.0/0 over BGP or by setting a Default Site with PowerShell on a route-based gateway; with ExpressRoute, only through BGP. Subnets that must go out directly use a 0.0.0.0/0 route to Internet, and direct inbound access from the internet to the subnet stops working.
About forced tunneling for site-to-site configurations ↗Azure virtual network traffic routing ↗
To diagnose routing, review the NIC's effective routes (available only while the VM runs) and Network Watcher next hop for a given destination. Azure chooses by longest prefix and, for equal prefixes, prefers user routes, then BGP, then system routes; virtual network and peering system routes beat BGP even when the BGP route is more specific.
Diagnose a virtual machine routing problem ↗Azure virtual network traffic routing ↗
Azure Route Server exchanges routes with NVAs over BGP and programs them into the virtual network and peered networks, with no route tables to maintain. It's deployed in RouteServerSubnet with a Standard public IP, always uses ASN 65515, and doesn't forward data traffic. To exchange routes between NVAs and VPN or ExpressRoute gateways, you enable branch-to-branch.
What is Azure Route Server? ↗Azure Route Server frequently asked questions ↗
Azure NAT Gateway is the recommended outbound method: it gives a whole subnet internet egress without public IPs on VMs and without accepting unsolicited inbound connections. It relieves SNAT exhaustion with dynamic port allocation, provides predictable outbound IPs through public IP prefixes, and fits private subnets, internal load balancer backends and App Service with virtual network integration.
To implement Azure NAT Gateway, create the resource, assign public IPs or prefixes, and associate it with subnets, with no route table changes. A subnet takes only one NAT gateway, which can't span virtual networks or be used in GatewaySubnet. A 0.0.0.0/0 route to a virtual appliance or gateway takes priority over the NAT gateway, which in turn wins over instance IPs and outbound rules.
Monitor networks
Network Watcher is enabled per region, in NetworkWatcherRG. Virtual network flow logs go to a standard storage account in the same region and can be set at NIC, subnet or VNet level, with precedence in that order; traffic analytics needs a Log Analytics workspace. Connection monitor and packet capture need agents, and saving captures to storage requires key access.
Virtual network flow logs ↗Enable or disable Azure Network Watcher ↗
Network Watcher bundles diagnostic tools: IP flow verify shows which rule allows or denies a TCP or UDP flow, NSG diagnostics also covers ICMP and service tags, and effective security rules aggregate the NIC and subnet rules. Connection troubleshoot tests at a point in time, while Connection monitor continuously tracks latency and loss.
What is Azure Network Watcher? ↗Connection troubleshoot overview ↗
Azure Monitor network insights, formerly Azure Monitor for Networks, shows topology, health, metrics and alerts for all network resources across subscriptions without prior configuration. Its connectivity view depends on Connection monitor tests, its traffic view on flow logs and traffic analytics, and the diagnostic toolkit opens the Network Watcher tools.
DDoS Network Protection is activated by linking virtual networks to a protection plan, which works across subscriptions in the same tenant and includes rapid response and cost protection; DDoS IP Protection is enabled on each Standard public IP without a plan. To monitor, use the Under DDoS attack or not metric in alerts and the DDoSProtectionNotifications and DDoSMitigationFlowLogs categories in Log Analytics.
About Azure DDoS Protection Tier Comparison ↗Tutorial: View Azure DDoS Protection logs in Log Analytics workspace ↗
Secure score groups Microsoft cloud security benchmark recommendations into controls such as Secure management ports or Restrict unauthorized network access; a control earns all its points when every resource meets all its recommendations, and preview recommendations don't count. You can remediate with Fix, prevent regressions with Enforce or Deny, and query controls with Azure Resource Graph.
Secure score in Defender for Cloud ↗Networking security recommendations ↗
Defender CSPM attack path analysis uses the cloud security graph to find exploitable paths that start at an external entry point, such as an internet-exposed VM, and reach a critical asset through lateral movement. Paths are sorted by risk, and each one lists the recommendations that fix it plus additional ones that only lower the risk.
Security explorer and attack paths in Microsoft Defender for Cloud ↗Identify and remediate attack paths in Microsoft Defender for Cloud ↗
Cloud security explorer, included in Defender CSPM with agentless scanning, runs graph queries to locate resources by internet exposure, vulnerabilities, permissions or lateral movement across Azure, AWS and GCP. You start from templates or your own filters, and results can be downloaded as CSV or shared by link; exposure is computed from configuration and network-path reachability.
Build queries with cloud security explorer ↗Internet exposure analysis ↗