AZ-800 Is Retired: Windows Server Certification Now Centers on AZ-802
AZ-800 retired on September 30, 2026, so it is no longer a current certification exam. Microsoft has consolidated the Windows Server Hybrid Administrator Associate path around the current AZ-802 Administering Windows Server exam. That change matters for candidates who find older AZ-800 material in search results: the skills remain useful, but the exam target and blueprint have changed.
AZ-800 focused on core hybrid Windows Server administration, including AD DS, hybrid workload management, virtualization and containers, networking, storage, and file services. AZ-802 now brings those core areas together with security, monitoring, and troubleshooting in one current exam. The modern role still spans on-premises, Azure, and hybrid environments, but candidates no longer need to plan around the former AZ-800/AZ-801 pair.
The most useful way to treat AZ-800 content is as legacy curriculum that can strengthen Windows Server fundamentals while you align preparation to the current AZ-802 objective map.
AZ-800 emphasized AD DS, Windows Server workloads in hybrid environments, Hyper-V and containers, networking, storage, and file services. Those are still central administration responsibilities and appear in the current Windows Server role.
Candidates who already studied AZ-800 should not restart from zero. Mark each topic as current in AZ-802, moved to a different weighting, or expanded by newer administration and security expectations.
The legacy transition material around AZ-801 retirement and AZ-802 helps place the two-exam history into the current one-exam path.
A good transition checklist begins with inventory. Mark which AZ-800 labs you already completed, which objectives appear unchanged in AZ-802, and where the consolidated exam adds security or troubleshooting depth. This avoids repeating hundreds of pages of familiar material while also preventing hidden gaps caused by assuming the new exam is simply AZ-800 with a different number.
The current AZ-802 blueprint gives 20–25% to deploying and managing AD DS. It includes domain controllers, RODCs, FSMO roles, trusts, sites, replication, users and groups, service accounts, and Group Policy.
Hybrid management remains explicit through Windows Admin Center, PowerShell remoting, SSH, Azure Arc-enabled servers, Azure Update Manager, VM extensions, and Azure Automation. That makes the certification a Windows Server administration exam with Azure integration, not an Azure-only exam.
Build labs that include both local and Azure-hosted Windows Server so you learn where the administrative model is shared and where cloud services add new control.
AD DS preparation should include multi-site and multi-forest behavior because hybrid organizations often inherit complexity rather than design a clean single domain. Practice trusts, replication topology, site links, RODCs, service accounts, and Group Policy interaction so the identity foundation is robust enough for Azure-integrated management.
AZ-802 includes Hyper-V configuration, remote VM management, nested virtualization, memory, integration services, device assignment, GPU partitioning, checkpoints, high availability, virtual disks, NIC teaming, virtual switches, and Replica.
The best preparation is to operate a small Hyper-V environment and deliberately change its state. Create checkpoints, modify networking, move storage, test Replica, and recover from a bad configuration.
Cloud administrators can overlook these host-level skills because managed services abstract them. Windows Server administrators are still expected to understand the platform underneath hybrid workloads.
Hyper-V labs should include management from more than one tool. Perform an action locally, through PowerShell, and through a remote administration path where practical. This shows which operations depend on host connectivity, permissions, or Azure integration and makes troubleshooting more realistic than working only in one console.
Use DNS, DHCP, and NAT fundamentals to refresh name resolution and address services. AZ-802 includes AD-integrated DNS, zones, forwarding, hybrid name resolution, DNS policies and DNSSEC, plus DHCP scopes, reservations, and high availability.
Networking troubleshooting should separate DNS, address assignment, routing, firewall, and application symptoms. A domain authentication issue can begin with name resolution or time synchronization rather than with Active Directory permissions.
Hybrid designs also need consistent IP and DNS planning between data centers and Azure networks. Poor naming and addressing decisions become migration blockers later.
DNS and DHCP should be treated as directory and application dependencies, not background services. Record how clients choose DNS servers, how AD-integrated zones replicate, how conditional forwarding reaches Azure or other networks, and what happens when a DHCP failover partner or DNS path is unavailable.
AZ-802 allocates 15–20% to storage and file services. Current objectives include Azure Files, Azure File Sync, migration from DFS or file shares, Windows shares, FSRM, DFS, SMB over QUIC, Storage Spaces, Storage Replica, deduplication, SMB Direct, QoS, NTFS/ReFS, iSCSI, and BitLocker.
This is a reminder that Windows Server administration is not only identity and virtual machines. File services remain critical in enterprise environments and are often the workload that makes hybrid modernization difficult.
Build a migration lab from a traditional share to Azure Files or Azure File Sync and include permissions, performance, naming, backup, and cutover validation.
Storage labs should include recovery as well as performance. Create a share, apply NTFS and share permissions, enable a relevant protection mechanism, and then restore or migrate it. Verify that users regain the expected access and that encryption, names, paths, and applications still work after the change.
The current role expects PowerShell alongside Windows Admin Center and Azure services. Review PowerShell and automation scripting and automate tasks you first understand manually.
Use practical Windows examples such as Windows administration with PowerShell to practice inventory, configuration, service management, event logs, network settings, and remote administration.
Automation should be idempotent or at least predictable. A script that cannot be safely rerun or explain what it changed creates operational debt.
PowerShell becomes especially valuable in multi-server environments. Write small tools that report drift, patch state, service configuration, disk capacity, or AD health before you automate remediation. Observation-first automation reduces the risk of running a broad corrective command based on an incorrect assumption.
AZ-802 includes a dedicated Windows Server security domain: exploit protection, application control, Credential Guard, SmartScreen, security baselines, Windows LAPS, Defender for Servers, Windows Firewall, AD DS hardening, password controls, delegation, and authentication protocols.
That makes security part of normal administration rather than an advanced afterthought. Administrators should be able to harden a server while preserving manageability and application requirements.
Use least-privilege principles to review administrative roles and service accounts, particularly in AD DS where overprivileged identities can affect the entire domain.
Security preparation should include domain-specific blast radius. A local administrator compromise, a domain-admin compromise, and a stolen service account are different incidents. Review where credentials are stored, which systems trust them, and which containment action is possible without locking out recovery access.
AZ-802 gives 15–20% to monitoring and troubleshooting. The objective list includes Performance Monitor, data collector sets, Windows Admin Center alerts, System Insights, event logs, Azure Monitor data collection, VM Insights, connectivity, name resolution, Windows Update, time, performance, extensions, encryption, storage, AD replication, Kerberos, and trust issues.
This troubleshooting breadth is why memorizing setup steps is not enough. Practice starting from a symptom, gathering evidence, narrowing the layer, testing one hypothesis, and verifying the fix.
The general observability model helps because Windows troubleshooting also depends on trustworthy metrics, logs, baselines, and actionable alerts.
Troubleshooting exercises should produce a short incident record: symptom, scope, evidence, hypothesis, test, remediation, and verification. That discipline keeps study scenarios realistic and makes it easier to review why a fix worked rather than remember only the command that happened to resolve it.
Treat AZ-802 as an operations exam, not merely a replacement code. The consolidated blueprint expects you to move from identity to storage to network to security to troubleshooting without the artificial boundary that AZ-800 and AZ-801 once created. Mixed labs should therefore combine at least three layers—for example, an AD-authenticated file service over hybrid networking with Azure monitoring and a hardened server baseline.
Keep a troubleshooting notebook during preparation. For each failure, record the first observable symptom, the evidence that narrowed the problem, the root cause, and the verification step. Over time you will see recurring Windows patterns—DNS, time, permissions, replication, storage pressure, update state—that are more valuable than memorizing isolated repair commands.
The current Azure certifications should be the planning source for broader role progression. AZ-802 is the active Windows Server exam; AZ-800 and AZ-801 are historical paths as of October 2026.
If you find a high-quality AZ-800 course, use it selectively for AD DS, hybrid management, virtualization, networking, and storage, then add the current AZ-802 security and troubleshooting scope and verify every objective against the live guide.
The goal is to convert legacy study investment into current administration competence rather than spend time mastering an exam that can no longer be scheduled.
Because the retirement occurred only days before this article update, stale AZ-800 search results will be common. Preserve the URL and historical context for users who arrive from old bookmarks, but make the first screen unambiguous: the current scheduling target is AZ-802, and any legacy plan needs to be mapped forward before candidates spend more study time.
