TECHNOLOGY & CERTIFICATION EDITORIAL

Microsoft MD-101 After Retirement: Endpoint Management Skills

MD-101: Managing Modern Desktops retired on September 30, 2023 alongside MD-100. Microsoft replaced the former two-exam path with MD-102 for the Endpoint Administrator Associate role. MD-101 should therefore be studied as a historical collection of deployment, policy, application and security concepts—not as a current certification booking. Its most useful lessons concern how to manage many devices without breaking the users who depend on them.

Separate MD-101 history from the present exam

The legacy MD-101 emphasized provisioning and enterprise endpoint management. The modern role includes cloud-driven device lifecycle management, Intune-based configuration, endpoint security and operational troubleshooting. Don’t assume that the percentage weights, product names or task wording from an old MD-101 practice test apply to MD-102. Read the current official study guide and map each historic topic to a current management task before investing study time.

If you earned the earlier award, list its historical identity and completion date accurately. If you want a new certificate, MD-101 is no longer a path to one. The meaningful question is whether you can enroll devices safely, evaluate compliance, deploy and recover applications, and explain why a specific policy is applied.

Design an enrollment flow for two types of users

Imagine an organization with company-owned laptops for employees and personally owned phones for temporary contractors. These should not receive identical management policies. Map which information the organization can inspect, which work data needs protecting, and what happens when a user leaves. Select enrollment and application protection methods only after confirming device platform, licensing, ownership and privacy requirements. A support call for “device not compliant” may originate in an enrollment failure, not a security threat.

Document prerequisites: supported operating-system version, identity, enrollment restrictions, licensing, connectivity and required device configuration. Pilot with nonproduction identities or a small approved group. Record the device status seen by both the user and management console. A successful sign-in does not prove policy receipt; distinguish registered, enrolled, compliant and application-authorized states.

Design enrollment as separate journeys rather than one giant checklist. A company laptop may arrive with a provisioning profile and approved application set; a contractor’s personal phone may only permit protection of organizational app data. For each journey, record the identity requirement, ownership assumption, eligible enrollment method, user prompts and support fallback. Test a device that meets every prerequisite and a device blocked by an intentional restriction. The administrator should be able to explain where the restriction is enforced and why it exists. A screen that says ‘enrollment failed’ is not sufficient evidence to disable a policy: the failure may be due to licensing, a stale registration, a blocked platform version, or a missing device assignment.

Test policy precedence and safe rollout

Start with one modest setting, such as an approved screen-lock timeout, and apply it to a pilot group. Verify scope, device check-in, conflict state and the observed configuration on the endpoint. Intune policies, local settings and legacy Group Policy can interact; don’t assume an assigned policy has always won. If a setting conflicts, identify its authority before removing a different control. Use documented change windows and a rollback group rather than a tenant-wide deployment.

Evaluate compliance policies separately from configuration profiles. A device can receive a screen-lock configuration yet still fail compliance because of encryption, operating-system version or another requirement. Use conditional access only after checking the device signals it relies on. A broad rule introduced without break-glass procedures and pilot evidence can lock legitimate administrators out of critical services.

Separate three commonly confused outcomes: a configuration setting applies, a device is compliant, and a user is allowed access to an application. Each may depend on a different service and evaluation time. In a controlled scenario, configure a modest security requirement, intentionally make a test device noncompliant, and observe what the access policy does after status evaluation. Avoid claiming that a device becomes secure merely because a management console shows its last sync as successful. Record evaluation latency and the scope of any exception. If users lose access, the rollback should narrow the policy change rather than remove all controls from the environment.

Application delivery and device recovery are real tests

Package a small application in a controlled lab, declare install and detection rules, and then test deployment, update and uninstall. A failed detection rule can make a healthy install appear broken or trigger repeated installs. Collect deployment logs before changing the installer. For version changes, establish supersedence or replacement behavior rather than assuming a new package automatically cleans up the old one.

Practice remote device actions only on approved test hardware. Understand the differences among retire, wipe, selective work-data removal and loss of management access. For a personally owned phone, an inappropriate full-device wipe can be a serious privacy and operational mistake. Verify device ownership, authorization and recovery implications before any destructive administrative action.

Application rollout deserves its own failure plan. Package a small, non-sensitive utility, specify the detection rule, and test clean installation, upgrade, rollback and uninstall on disposable devices. If the application installs but the management platform reports failure, inspect whether the detection logic is wrong before reinstalling repeatedly. Use a pilot group that includes at least one representative application conflict and an interrupted network connection. Document the expected user experience and the conditions that force a wider rollout to stop. Successful enterprise device management is about controlled change, not simply sending an installation command to a large fleet.

Build a troubleshooting and evidence habit

For a user who cannot open an internal application, gather device identity, compliance state, application assignment, enrollment logs, sign-in evidence and network conditions. Separate root-cause hypotheses into device setup, policy processing, licensing, identity and app-specific faults. Change one variable at a time where practical. Document the precise steps to reproduce and resolve the issue without exporting personal data into a public portfolio.

A useful learning project includes a policy ring diagram, screenshots of scoped assignments, one deliberate detection-rule failure and a rollback test. Show the before and after endpoint state and a short incident note. These artifacts demonstrate the type of work current endpoint administrators perform; a claim that you “mastered MD-101” does not.

Treat enrollment as a state machine rather than a yes/no box. A newly issued laptop might be joined to the intended identity directory but not yet enrolled in endpoint management; an enrolled device might fail compliance because encryption is incomplete; a compliant device might still be denied an application because the user lacks a license. Draw these states and the evidence that moves a device between them. Test them in a pilot with distinct users, then see whether your helpdesk documentation tells support agents where to look next. Every handoff that relies on “just wait and try again” hides a missing diagnostic step.

For device replacement, write two separate checklists: one for restoring productive access, another for retiring the old device safely. Confirm ownership, business data transfer, application licensing, endpoint encryption and the account’s current session tokens. Record whether a selective removal of corporate data is supported for the ownership model. The return of a desktop icon does not prove every corporate secret was revoked on a lost machine. Ask who can authorize an irreversible wipe, what evidence is required first, and how an incorrectly assigned wipe command would be prevented in the management process.

A measurable final assessment can combine the parts of this article. Given a test device with successful directory registration but failed compliance, the learner must identify the failing requirement, confirm relevant device policy, repair only the affected setting and demonstrate compliant check-in without weakening another control. Award credit for explaining the security consequence of a shortcut. As a second case, supply a failed line-of-business application update with a safe rollback package. These tasks give a much better indication of endpoint administration readiness than generalized statements about the career value of MD-101.

Which pathway makes sense now

Use historic MD-101 material to strengthen deployment and management fundamentals, then study Microsoft’s currently published MD-102 objectives for certification. If you already operate Intune in a production environment, focus on safe automation, reporting, endpoint security and device-lifecycle exceptions rather than repeating basic course material. The lasting value lies in disciplined fleet operations, not treating a retired exam code as an active destination.

A hiring portfolio should connect those tests to support procedures. Include an enrollment decision tree, one sanitized policy-assignment record, a list of evidence collected for a failed app deployment, and a written device-replacement runbook that distinguishes business-data removal from recovery of personal information. Explain which tasks still resemble historic MD-101 objectives and which reflect newer Intune and endpoint-security workflows. Check the official MD-102 study guide for the currently assessed skill areas before preparing for an exam. No one should infer from a well-written historical MD-101 article that a new MD-101 booking or renewal is available.

Finally, include a privacy and access boundary in the device-management design. For a personal phone, decide what data the organization can inspect or remove and explain that distinction to the user before enrollment. For a shared kiosk, decide how sessions end, which applications are permitted and how local state is cleared. A device that reports a compliant configuration can still expose information through an overly broad application permission or an abandoned session. Test permissions using two fictional identities and demonstrate that a device operator cannot read another employee’s private documents simply because they manage enrollment. Clear ownership and minimum necessary access are as important as the mechanics of pushing a policy.

Back to Insights
Explore what matters. Knowledge that goes beyond the exam.
Explore ExamTopics