Study guide

11.4 IP Address Management (IPAM) Deployment & Auditing

Administering Windows Server Hybrid Core Infrastructure AZ-800

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About Exam AZ-800: Format, Scoring & the September 2026 Retirement

2 Chapter 1: Active Directory Domain Services Architecture & Deployment

1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships

3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join

2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale

4 Chapter 3: Hybrid Identity & Microsoft Entra Integration

3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

5 Chapter 4: Group Policy in AD DS and Hybrid Environments

4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

6 Chapter 5: Remote Server Management in Hybrid Environments

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion

7 Chapter 6: Hybrid Management with Azure Arc and Azure Services

6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration

7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization

9 Chapter 8: Hyper-V High Availability, Security & Containers

8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry

10 Chapter 9: Azure IaaS Virtual Machine Administration

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity

11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution

10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC

12 Chapter 11: IP Addressing, DHCP & IPAM Management

11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments

13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections

14 Chapter 13: File Services, DFS, SMB & Azure File Sync

13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync

15 Chapter 14: Windows Server Storage Infrastructure & High Availability

14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O

11.4 IP Address Management (IPAM) Deployment & Auditing

Key Takeaways Explain This Topic AI

Windows Server IPAM provides agentless, centralized discovery, monitoring, and administration of enterprise IP address spaces, DHCP servers, and DNS zones across Active Directory forests.

IPAM deployment prerequisites mandate a domain-joined standalone or member Windows Server; IPAM cannot be co-located on an Active Directory Domain Controller.

Group Policy-based provisioning automates server access configuration across discovered Domain Controllers, DHCP servers, and DNS servers via Invoke-IpamGpoProvisioning.

IP Address Space Management (ASM) organizes network addressing hierarchically into IP Address Blocks, IP Address Ranges (mapping to scopes), and Individual IP Addresses, tracking utilization thresholds.

Forensic IP address tracking and event auditing correlates DHCP lease events, Active Directory user logons (Event ID 4624), and NPS accounting logs to trace user identities and MAC addresses over time.

Last updated: August 2026

IP Address Management (IPAM) Deployment & Auditing

As enterprise hybrid networks scale across physical datacenters, remote branch offices, and cloud virtual networks, managing IPv4 and IPv6 address allocations across disparate DHCP servers and DNS zones using disconnected spreadsheets or isolated management consoles becomes untenable. Windows Server IP Address Management (IPAM) provides a centralized, agentless framework for discovering, tracking, auditing, and managing the entire enterprise IP address space, DHCP server configurations, and DNS infrastructure.

1. IPAM Architecture, Capabilities & Deployment Prerequisites

IPAM operates as an integrated management framework built into Windows Server that automates address space allocation and server role administration. +-----------------------------------------------------------------------------+

  • | WINDOWS SERVER IPAM ARCHITECTURE |
  • | |
  • | [IPAM MANAGEMENT SERVER (Dedicated Member Server)] |
  • | - Backend Database: Windows Internal Database (WID) or Microsoft SQL |
  • | - Agentless Remote Management: WMI, RPC, WinRM, PowerShell Remoting |
  • | | |
  • | +----------------------------+----------------------------+ |
  • | | | | |
  • | v v v |
  • | [DOMAIN CONTROLLERS / NPS] [DHCP SERVERS] [DNS SERVERS] |
  • | - GPO: IPAM1_DC_NPS - GPO: IPAM1_DHCP - GPO: IPAM1_DNS|
  • | - Audits User Logons (4624) - Syncs Scopes & Leases - Syncs Zones |
  • | - Audits Machine Accounts - Configures Failover - Manages A/PTR |
  • +-----------------------------------------------------------------------------+

Core Capabilities of IPAM:

IP Address Space Management (ASM): Centralized tracking and planning of IPv4 and IPv6 address blocks, subnets, ranges, and static/dynamic IP allocations with automatic utilization threshold monitoring.

Multi-Server Management (MSM): Centralized discovery, monitoring, and configuration of multiple distributed DHCP servers, DHCP scopes, failover relationships, DNS servers, and DNS zones from a single pane of glass.

Network Auditing & IP Tracking: Comprehensive forensic tracking correlating IP lease histories, MAC addresses, hostnames, and Active Directory user logon events.

Role-Based Access Control (RBAC): Granular delegation of administrative permissions across specific geographic sites, subnets, or server roles.

Critical Deployment Prerequisites:

Domain Membership: The IPAM server must be joined to an Active Directory Domain Services domain.

The Domain Controller Co-Location Prohibition:

IPAM CANNOT be installed on an Active Directory Domain Controller .

Why? Installing IPAM on a DC breaks IPAM's agentless privilege isolation model and prevents the server discovery engine from properly cataloging and auditing other domain controllers and DHCP servers in the forest.

Single Forest Root Scope: A single IPAM server can discover and manage infrastructure servers across multiple trusted domains within a single Active Directory forest.

Database Backend Options:

Windows Internal Database (WID): Installed locally by default; suitable for small-to-medium single-site environments (up to 150 DHCP servers and 500 DNS servers).

Microsoft SQL Server: Required for large enterprise multi-site deployments, high availability, or disaster recovery configurations.

2. IPAM Provisioning: Manual vs. Group Policy-Based

When deploying IPAM, administrators must choose a provisioning method to grant the IPAM server administrative and auditing access to target infrastructure servers. Once selected during initial setup, the provisioning method cannot be changed without reinstalling IPAM. +-----------------------------------------------------------------------------+

  • | IPAM PROVISIONING METHOD COMPARISON |
  • | |
  • | FEATURE MANUAL PROVISIONING GROUP POLICY PROVISIONING |
  • | -------------------+------------------------+-----------------------------|
  • | Configuration | Manual configuration of| Automated via PowerShell |
  • | Mechanism | local security groups, | Invoke-IpamGpoProvisioning |
  • | | firewall ports, shares | cmdlet |
  • | Scalability | Extremely poor; high | High; automatically applies |
  • | | configuration drift | as new servers are managed |
  • | GPOs Created | None | 3 GPOs per domain: |
  • | | | _DHCP, _DNS, _DC_NPS |
  • | Security Filtering | N/A | IPAM adds managed server |
  • | | | computer accounts to GPO ACL|
  • | Recommended For | Non-domain environments| Production Active Directory |
  • +-----------------------------------------------------------------------------+

Group Policy-Based Provisioning Mechanics:

Executing Invoke-IpamGpoProvisioning generates three distinct Group Policy Objects (GPOs) in the target domain:

<Prefix>_DHCP : Applied to managed DHCP servers. Configures the DHCP Users local group, enables remote RPC/WMI firewall rules, and grants IPAM read/write access to DHCP service configurations.

<Prefix>_DNS : Applied to managed DNS servers. Configures DNS RPC/WMI access, opens DNS management firewall ports, and grants read/write permissions to DNS zones.

<Prefix>_DC_NPS : Applied to Domain Controllers and Network Policy Servers (NPS). Adds the IPAM server computer account to the Event Log Readers built-in security group and enables remote event log firewall ports to read Security Event Log Event ID 4624 (Successful Logon) and NPS accounting logs for IP address tracking. # 1. Install IPAM Role and Tools on dedicated member server

Install-WindowsFeature -Name IPAM -IncludeManagementTools

  • # 2. Provision IPAM GPOs in the target domain
  • Invoke-IpamGpoProvisioning `
  • Domain 'corp.contoso.com' `
  • GpoPrefixName 'IPAM1' `
  • IpamServerFqdn 'ipam01.corp.contoso.com' `
  • DelegatedGpoUser 'Administrator'
  • 3. Server Discovery & Manageability Lifecycle

After provisioning GPOs, administrators execute the end-to-end server discovery and onboarding lifecycle. +-----------------------------------------------------------------------------+

  • | IPAM SERVER ONBOARDING LIFECYCLE |
  • | |
  • | [1. Configure Discovery] ---> Select Forest & Domains; Select DC/DHCP/DNS|
  • | | |
  • | v |
  • | [2. Run Server Discovery] ---> Queries Active Directory for registered |
  • | Domain Controllers, DHCP & DNS servers |
  • | | |
  • | v |
  • | [3. Set Manageability] ---> Change status from 'Unspecified' to |
  • | 'MANAGED' in IPAM Server Inventory |
  • | | |
  • | v |
  • | [4. GPO Security Filter] ---> IPAM adds Managed Computer account into |
  • | Security Filtering of the appropriate GPO |
  • | | |
  • | v |
  • | [5. Force Policy Refresh] ---> Run 'gpupdate /force' on target server |
  • | | |
  • | v |
  • | [6. Retrieve Server Data] ---> IPAM audits and pulls scopes, leases, zones|

+-----------------------------------------------------------------------------+ # Configure discovery domains and roles

  • Add-IpamDiscoveryDomain `
  • Name 'corp.contoso.com' `
  • DiscoverDc $true `
  • DiscoverDhcp $true `
  • DiscoverDns $true
  • # Start asynchronous server discovery
  • Start-ScheduledTask -TaskPath '\Microsoft\Windows\IPAM\' -TaskName 'ServerDiscovery'
  • # Set manageability status of discovered server to Managed
  • Set-IpamServerInventory `
  • ServerName 'dhcp01.corp.contoso.com' `
  • ManageabilityStatus Managed
  • # Trigger immediate data collection from managed inventory
  • Invoke-IpamServerInventory -ServerName 'dhcp01.corp.contoso.com'
  • 4. IP Address Space Management (ASM) Hierarchy

IPAM organizes enterprise IP address space into a structured three-tier hierarchy that maps continuous network blocks down to granular individual endpoints. +-----------------------------------------------------------------------------+

  • | IPAM ADDRESS SPACE HIERARCHY |
  • | |
  • | [IP ADDRESS BLOCK] |
  • | - Top-level continuous supernet allocation |
  • | - Example: 10.0.0.0/8 or 172.16.0.0/12 |
  • | | |
  • | v |
  • | [IP ADDRESS RANGE] |
  • | - Subnet-level allocation mapped directly to a DHCP scope or static VLAN |
  • | - Example: 10.10.1.0/24 (Workstations) or 10.10.2.0/24 (Servers) |
  • | - Tracks: Utilization % (Underutilized <20%, Optimal 20-80%, Over >80%) |
  • | | |
  • | v |
  • | [INDIVIDUAL IP ADDRESSES] |
  • | - Specific endpoint assignment mapped to MAC, Hostname, Device Type |
  • | - Example: 10.10.1.50 -> MAC: 00-15-5D-01-02-03 (Static / SQL Server) |
  • +-----------------------------------------------------------------------------+

ASM Hierarchy Details:

IP Address Blocks: The highest-level container representing an organization's public or private address allocations (e.g., 10.0.0.0/8 ). Blocks cannot be directly assigned to interfaces; they serve as umbrella containers for ranges.

IP Address Ranges: Mapped directly to physical subnets or active DHCP scopes (e.g., 10.10.1.0/24 ). IPAM monitors each range's utilization against configurable thresholds:

Underutilized: Less than 20% allocated (default).

Optimal: 20% to 80% allocated (default).

Overutilized: Greater than 80% allocated (default).

Individual IP Addresses: Explicit records for static or dynamically leased IP addresses. Captures MAC address, Client ID, Device Type (e.g., Server, Printer, Infrastructure), Hostname, and Assignment Date. # Add an IP Address Range to IPAM

  • Add-IpamRange `
  • StartIPAddress 10.10.1.1 `
  • EndIPAddress 10.10.1.254 `
  • SubnetMask 255.255.255.0 `
  • ManagedByService IPAM `
  • ServiceInstance Localhost
  • # Add a static individual IP allocation
  • Add-IpamAddress `
  • IpAddress 10.10.1.50 `
  • MacAddress '00-15-5D-AA-11-22' `
  • DeviceType 'Server' `
  • HostName 'SQL-PROD-01.corp.contoso.com' `
  • AssignmentType Static
  • 5. Multi-Server DHCP & DNS Management

IPAM allows administrators to centrally configure and monitor distributed DHCP and DNS servers across the enterprise from a unified management interface.

DHCP Multi-Server Operations:

Centrally create, modify, activate, and delete DHCP scopes across any managed DHCP server.

Create and manage native DHCP Failover relationships (Load Balance and Hot Standby) between servers.

Duplicate existing scopes and push them to remote branch servers with automated option customization.

DNS Multi-Server Operations:

Centrally create, duplicate, and manage DNS forward lookup zones and reverse lookup zones.

Add and modify standard DNS resource records ( A , AAAA , PTR , CNAME , MX , SRV ) across multiple authoritative servers.

Monitor DNS service operational status, zone transfer status, and event logging.

6. Role-Based Access Control (RBAC) & Delegation

Windows Server IPAM includes a granular Role-Based Access Control (RBAC) engine that enables administrative delegation based on roles and access scopes. +-----------------------------------------------------------------------------+

  • | IPAM BUILT-IN RBAC ROLES |
  • | |
  • | ROLE NAME PERMITTED ADMINISTRATIVE SCOPE |
  • | ----------------------------+---------------------------------------------|
  • | IPAM Administrators | Complete administrative control over all |
  • | | IPAM features, servers, and configurations |
  • | IPAM ASM Administrators | Manages IP address space: blocks, ranges, |
  • | (Address Space Management) | addresses, and subnet utilization |
  • | IPAM MSM Administrators | Manages server infrastructure: DHCP scopes, |
  • | (Multi-Server Management) | failover relationships, and DNS zones |
  • | IPAM IP Audit Administrators| Accesses IP address tracking and forensic |
  • | | event audit logs (Read-Only Audit) |
  • | IPAM Users | View-only access to IPAM data and inventory |
  • +-----------------------------------------------------------------------------+

Access Scopes Delegation:

Administrators can define Custom Access Scopes based on geographic location or business unit (e.g., Global\NorthAmerica\Chicago ). Regional administrators can be assigned the IPAM ASM Administrator role restricted exclusively to the Chicago access scope, preventing them from modifying IP address ranges or DHCP scopes in London or Tokyo.

7. Forensic IP Address Tracking & Event Auditing

Regulatory compliance standards (such as PCI-DSS, HIPAA, and SOC 2) require enterprises to maintain verifiable records of network access. IPAM includes an advanced IP Address Tracking engine that correlates data across multiple server logs. +-----------------------------------------------------------------------------+

  • | IPAM FORENSIC EVENT CORRELATION ENGINE |
  • | |
  • | [DHCP LEASE EVENTS] [ACTIVE DIRECTORY SECURITY LOGS] |
  • | (IP: 10.10.1.105 assigned to (User: 'jdoe' logged onto workstation |
  • | MAC: 00-15-5D-11-22-33) at 2026-08-22 09:15:22 - Event ID 4624) |
  • | \ / |
  • | \ / |
  • | v v |
  • | +---------------------------------------------------------------------+ |
  • | | IPAM FORENSIC AUDIT ENGINE | |
  • | | | |
  • | | CORRELATED AUDIT RECORD: | |
  • | | - Target IP: 10.10.1.105 | |
  • | | - User Identity: CORP\jdoe | |
  • | | - Host Computer: WORKSTATION-842.corp.contoso.com | |
  • | | - Physical MAC: 00-15-5D-11-22-33 | |
  • | | - Lease Window: 2026-08-22 09:00:00 to 2026-08-22 17:00:00 | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Forensic Search Dimensions:

Administrators can query the IPAM event database across four distinct search vectors:

By IP Address: Displays all physical devices, MAC addresses, hostnames, and user accounts that utilized a given IP address over a specified date/time range.

By Client ID / MAC Address: Displays all IP addresses leased by a physical network adapter over time.

By Host Name: Tracks every IP address assigned to a specific computer object.

By User Name: Identifies every IP address and workstation utilized by a specific Active Directory user account during corporate logon sessions. # Query IP address lease history for a forensic investigation

  • Get-IpamAddressHistory `
  • StartDate (Get-Date).AddDays(-14) `
  • EndDate (Get-Date) `
  • SearchType IP `
  • SearchValue '10.10.1.105'

Loading diagram... IPAM GPO Provisioning and Multi-Server Discovery Architecture