Microsoft AZ-800 Is Retired: AZ-802 Study Transition
Microsoft AZ-800 retired on September 30, 2026, so “reasons to prepare for AZ-800” must now be reframed as reasons to reuse that preparation for AZ-802: Administering Windows Server. Candidates who already studied the old hybrid core exam have a valuable head start, but they should stop following retired domain weights and rebuild the plan around the current consolidated exam.
AD DS, DNS, authentication, group policy, and hybrid identity remain essential. Review them as an operating system of dependencies rather than isolated facts. Practice diagnosing sign-in failures by checking name resolution, time, replication, permissions, and the actual authentication path before making changes.
Server configuration, remote management, updates, monitoring, and Azure-connected administration continue to matter. Use PowerShell and Windows Admin Center in labs so your study produces repeatable evidence instead of menu memory. Understand what Azure Arc or cloud management adds and what still depends on the underlying Windows Server state.
Hyper-V, virtual switches, routing, DNS, file services, storage, and permissions all remain transferable. These areas also combine naturally in scenario questions. A VM can be healthy but unreachable; a file share can exist but fail authorization; a hybrid server can be registered but unable to communicate with a dependency. Practice the boundaries.
AZ-800 and AZ-801 were separate exams. AZ-802 is the current consolidated target. Do not allocate time simply because an old topic had a particular percentage. Use the AZ-800 to AZ-802 mapping guide and rebuild priorities from the active blueprint.
A candidate who focused narrowly on AZ-800 may be weaker in areas that previously sat more heavily in AZ-801, such as advanced security, monitoring, troubleshooting, migration, or resilience. Treat the transition as a breadth check. Run a diagnostic across the entire current role and let the weakest operational area determine the next lab.
Build one environment with AD DS, a member server, a Hyper-V workload, file services, hybrid management, and monitoring. Introduce failures deliberately: break DNS, change a permission, stop a service, misconfigure a virtual switch, or remove cloud connectivity. Then diagnose the issue without changing several things at once.
Start with scope: one user, one server, one site, or the whole environment? Then prove identity, name resolution, route, service, permission, workload state, and management-plane evidence in a sensible order. The Windows Server readiness guide provides a useful skill checklist even though the AZ-800 label in its URL is now historical.
If an old resource teaches a durable Windows Server skill, keep it. If it teaches exam logistics, final AZ-800 weighting, or a two-exam certification sequence, retire it. The best reason to continue studying is that the knowledge transfers directly into the current AZ-802 role and into real Windows Server administration.
For each major Windows Server capability, record one configuration task, one failure you can reproduce, one source of evidence, and one safe recovery action. A domain controller might be paired with replication evidence; Hyper-V with host and guest networking checks; file services with share and NTFS authorization; hybrid management with agent and connectivity state. This makes the transition measurable and prevents a study plan from becoming a list of topics that were read but never operated.
