Study guide

12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing

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

12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing

Key Takeaways Explain This Topic AI

Network Policy Server is Microsoft's RADIUS server and RADIUS proxy, and every authenticator such as a VPN server, wireless AP, or switch must be registered on it as a RADIUS client.

An authenticator that is not defined as a RADIUS client is silently ignored, which is the usual cause of authentication requests that never appear in the NPS log.

A Connection Request Policy decides where authentication happens: locally against Active Directory or forwarded to a remote RADIUS server group for another realm.

A Network Policy decides whether access is granted and under what constraints, evaluating conditions top-down by processing order until the first match.

Because evaluation stops at the first matching Network Policy, a broad deny or restrictive policy placed above a specific grant policy blocks users the administrator intended to allow.

Last updated: August 2026

  • Network Policy and Access Services (NPAS), RADIUS & Policy Processing
  • 1. Network Policy and Access Services (NPAS) & RADIUS Framework

The Network Policy and Access Services (NPAS) role provides centralized Authentication, Authorization, and Accounting (AAA) via the Remote Authentication Dial-In User Service (RADIUS) protocol (RFC 2865 for Authentication/Authorization and RFC 2866 for Accounting). +-----------------------------------------------------------------------------------+

  • | NPAS / RADIUS ARCHITECTURE FLOW |
  • | |
  • | [CLIENT] [RADIUS CLIENT (NAS)] [NPS SERVER (AAA)] |
  • | - VPN Client - RRAS Server - Evaluates CRP |
  • | - 802.1X Workstation - 802.1X Switch / Wi-Fi AP - Evaluates NP |
  • | | | | |
  • | |--- (1) Auth Request ---->| | |
  • | | (EAP / Credentials) |--- (2) RADIUS Access-Request ->| |
  • | | | (UDP 1812 / 1645) | |
  • | | | |-- (3) Active|
  • | | | | Directory |
  • | | |<-- (4) RADIUS Access-Accept ---| Lookup |
  • | |<-- (5) Session Granted --| (or Access-Reject) | |
  • | | | | |
  • | | |--- (6) RADIUS Accounting ----->| |
  • | | | (UDP 1813 / 1646) | |
  • +-----------------------------------------------------------------------------------+
  • Network Access Servers (NAS / RADIUS Clients)

Any device that forwards user authentication requests to NPS is a RADIUS Client (Network Access Server). This includes Windows Server RRAS instances, enterprise Wi-Fi Access Points (802.1X), Cisco/Aruba switches (802.1X port-based access), and hardware firewalls. # Register the NPS Server in Active Directory Domain Services

# (Grants NPS permission to read user account dial-in properties and tokens)

# There is NO Register-NpsServer cmdlet. The NPS module ships exactly seven cmdlets:

  • # Get/New/Remove/Set-NpsRadiusClient, Get-NpsSharedSecretTemplate, and
  • # Import/Export-NpsConfiguration. Registration is done in the NPS console

# (right-click \"NPS (Local)\" > \"Register Server in Active Directory\") or with netsh:

netsh nps add registeredserver corp.contoso.com NPS-01

  • # Add a new RADIUS Client (RRAS VPN Gateway)
  • New-NpsRadiusClient `
  • Name 'Edge-RRAS-01' `
  • Address '192.168.10.1' `
  • SharedSecret 'RadClientSecret2026!Complex' `
  • AuthAttributeRequired $true

Important

Active Directory Registration Requirement: If an NPS server is not registered in Active Directory (via the NPS console context menu Register Server in Active Directory , or netsh nps add registeredserver <domain> <server> for a server outside its own domain), it cannot read user account dial-in permissions or Kerberos/NTLM authentication properties, resulting in all RADIUS connection attempts failing with generic access-denied errors.

2. Connection Request Policies vs. Network Policies

The single most critical exam concept in NPAS is understanding the exact architectural boundary between Connection Request Policies (CRP) and Network Policies (NP) . +-----------------------------------------------------------------------------------+

  • | CONNECTION REQUEST POLICIES VS NETWORK POLICIES |
  • | |
  • | DIMENSION CONNECTION REQUEST POLICIES NETWORK POLICIES |
  • | --------------------+-----------------------------+-----------------------------|
  • | Core Purpose | WHO evaluates authentication| WHETHER access is granted |
  • | | (Local vs Remote Proxy) | and WHAT constraints apply |
  • | Evaluation Order | Processed First | Processed Second (after CRP)|
  • | Key Decisions | - Authenticate locally | - Grant Access vs Deny |
  • | | - Forward to RADIUS Proxy | - EAP-TLS / PEAP methods |
  • | | - Realm name manipulation | - Group membership checks |
  • | Output / Action | Specifies Authentication | Issues RADIUS Attributes |
  • | | Provider / Server Group | (VLAN IDs, Filter-Id, ACLs) |
  • +-----------------------------------------------------------------------------------+
  • 1. Connection Request Policies (CRP)

Connection Request Policies inspect incoming RADIUS packets to determine whether the local NPS server should authenticate the credentials against local Active Directory or act as a RADIUS Proxy by forwarding the request to a Remote RADIUS Server Group .

Conditions: Evaluates incoming client IPv4 address, NAS Port Type (e.g., Virtual VPN vs Wireless IEEE 802.11), or User-Name regular expression patterns (e.g., ^CORP\\ vs .*@partner\.com ).

Authentication Target: Configured under Settings -> Authentication : either "Authenticate requests on this server" or "Forward requests to the following remote RADIUS server group for authentication".

2. Network Policies (NP)

Once a Connection Request Policy determines that the request will be processed locally, NPS evaluates Network Policies sequentially from top to bottom (Processing Order 1, 2, 3...) until the first matching policy is found.

Conditions: AD DS Security Group membership (e.g., CORP\VPN-Allowed-Users ), Client Machine health status, Day and Time restrictions, NAS-Port-Type.

Access Permission: Grant access or Deny access .

Authentication Methods (EAP):

EAP-TLS: Mutual certificate authentication (highest security for smart cards and managed domain devices).

PEAP-MS-CHAPv2: Protected EAP with server certificate validation and user password authentication.

Constraints & RADIUS Attributes:

Idle Timeout / Session Timeout limits.

RADIUS VLAN Tagging: Dynamically assigning authenticated switch ports or Wi-Fi sessions to specific VLANs using attributes:

  • Tunnel-Type = VLAN (value 13 )
  • Tunnel-Medium-Type = 802 (value 6 )
  • Tunnel-Private-Group-ID = <VLAN_ID> (e.g., 100 )

Caution

Evaluation Order Rule: NPS stops evaluating Network Policies immediately upon finding the first matching policy . If a user matches Policy #1, but Policy #1 denies access due to an authentication method mismatch, NPS will not continue evaluating Policy #2. Always order specific, restrictive policies above general catch-all policies.

  • 3. RADIUS Accounting and RADIUS Proxy Scenarios
  • RADIUS Accounting (RFC 2866)

NPS tracks session lifecycles for auditing, billing, and security forensics by logging:

Accounting-Start: Sent when the user connects and receives an IP address.

Accounting-Stop: Sent when the session terminates, recording total duration, input packets, output packets, and session termination reason.

Interim-Update: Periodic keep-alive metrics sent during long-lived sessions.

Storage Targets: NPS can write accounting data to local text log files in W3C Extended or IAS Format ( C:\Windows\System32\LogFiles ), or stream directly to an enterprise Microsoft SQL Server database via ODBC for centralized auditing.

RADIUS Proxy Routing

In multi-tenant, merged enterprise, or service provider environments, a central NPS server can act as a RADIUS Proxy. By inspecting the realm suffix in the user identity (e.g., user@emea.contoso.com ), the proxy forwards the RADIUS Access-Request to the EMEA NPS server cluster over UDP port 1812, proxies the Access-Accept response back to the local NAS, and preserves end-to-end authentication isolation.

Loading diagram... NPS Policy Evaluation: Connection Request Policy vs Network Policy Pipeline