Microsoft MD-101 Legacy: Move to MD-102 Endpoint Admin

Microsoft MD-101 is retired, so it should not be presented as a certification that candidates can still earn in 2026. The exam belonged to the Modern Desktop Administrator path and reflected a period when Windows deployment, compliance, configuration, and endpoint management were converging around Intune, Configuration Manager, Azure AD, and modern management.

Those skills did not become obsolete when the exam retired. Microsoft’s current endpoint credential is Microsoft 365 Certified: Endpoint Administrator Associate, earned through MD-102. The current role is broader and more cloud-managed: Intune, Microsoft Entra ID, Windows Autopilot, Defender for Endpoint, application management, compliance, endpoint security, automation, and increasingly agent-assisted administration.

Separate the retired exam from the still-relevant endpoint work

MD-101 study material can be useful when it explains why device enrollment, configuration policy, compliance, application deployment, update management, and endpoint protection have to operate as one lifecycle. It becomes harmful when it implies the old exam can still be scheduled or when it freezes product terminology in the pre-Entra era.

Use the current Microsoft MD-102 endpoint administration guide as the new frame. Then keep only the legacy notes that help you reason about endpoint state, user experience, security controls, and operational recovery.

Move identity language from Azure AD to Microsoft Entra ID

Endpoint administration depends on identity because device registration, join state, conditional access, application access, privilege, and compliance all involve an identity decision. Modern preparation should use Microsoft Entra ID terminology and understand how users, groups, device identities, roles, and access policies interact.

Do not reduce identity to “sign in works.” Practice scenarios where the device is registered incorrectly, a user receives a policy intended for another group, conditional access blocks a resource, or an administrator has more privilege than necessary. The troubleshooting path should connect identity evidence with device and policy state.

Make Intune the operating center of endpoint management

MD-102 is strongly aligned with cloud-managed endpoints. Learn enrollment choices, configuration profiles, compliance, update policy, application deployment, endpoint security, reporting, and remote actions as connected responsibilities. A change to one area can affect several others—for example, compliance can become an input to access control, and application deployment can depend on assignment and device state.

Build a small lab with multiple personas and device groups. Assign policies deliberately, create one conflict, and trace which setting wins and why. The goal is to understand effective state, not simply to know where a setting exists in the portal.

Treat Windows Autopilot as lifecycle automation, not an imaging trick

Current endpoint administration increasingly assumes devices can be provisioned with less custom imaging and more policy-driven configuration. Windows Autopilot supports that shift by connecting device identity, deployment profiles, enrollment, application delivery, and security configuration.

Practice the whole experience from device registration through first user sign-in and post-enrollment management. Document dependencies and failure points. If a device gets the wrong profile or fails to complete enrollment, you should know which evidence to inspect before resetting the machine or changing policy.

Endpoint security is now an operating responsibility

The modern endpoint administrator works closely with security controls such as endpoint security policies, attack-surface reduction, encryption, firewall configuration, Defender for Endpoint integration, local administrator controls, and compliance reporting. The role is not a security analyst role, but it must implement and maintain the device-side controls that security policy depends on.

Use least privilege when delegating administration, and test how a security baseline affects real applications and user workflows. A technically “secure” policy that breaks required business activity without a managed exception process is not a finished design.

Automation matters more than it did in the MD-101 era

Large endpoint estates cannot be managed efficiently through manual portal actions alone. PowerShell, Microsoft Graph, reporting exports, remediation scripts, and repeatable assignment strategies make administration more scalable and auditable. Current Microsoft materials also increasingly acknowledge agentic tools and workflows, so administrators need to understand automation boundaries as well as automation benefits.

Automate repetitive evidence gathering before automating destructive change. A script that reports stale devices, failed deployments, or noncompliance can be low risk and high value. A script that changes assignments across the tenant needs stronger testing, scope control, logging, and rollback.

Build readiness around evidence, not familiarity

The MD-102 readiness guide is most useful after you have hands-on evidence. You should be able to enroll a device, apply and verify configuration, deploy an application, investigate noncompliance, manage updates, respond to an endpoint-security requirement, and explain what data proves the change succeeded.

Round out the path with the Microsoft 365 certification roadmap so you understand where endpoint administration sits beside identity, security, Copilot, and broader administration roles. That prevents a retired MD-101 label from defining a modern job.

Final perspective

MD-101 is historical; endpoint administration is not. Preserve the lifecycle and troubleshooting habits from the old exam, but build current practice around MD-102, Intune, Entra ID, Autopilot, Defender for Endpoint, automation, and evidence-driven operations.

  • img