Home labs & practical projects

Pilot an endpoint compliance policy

A project to do with your own tools, with guidance on what to create and capture.

Vendor environment Suggested time: 2–3 hoursYour own authorised environment

What you could create

An endpoint team wants to introduce a new compliance requirement. A broad rollout could disrupt users whose devices need remediation.

Example evidence format

Project evidence map (example)

Endpoint policy pilot planScope and inputs

Device-state results and remediation instructionsDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Endpoint policy pilot plan	Show the inputs, scope and decisions behind this record. Policy assignment is distinguished from actual device compliance.
Device-state results and remediation instructions	Include the evidence supporting your conclusion. The non-compliant user has a documented route to recover access.

What you'll need

Vendor environment

Use an authorised device-management training tenant and disposable or dedicated test devices. Define one compliant and one non-compliant state and confirm licensing.

Project record

Keep the working files for endpoint policy pilot plan and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Access may require a licence, trial or training subscription. Confirm availability and permitted use before committing; no free tenant is assumed.

Use an authorised training tenant with test identities and synthetic data. If access is unavailable, document the plan and label it untested.

Suggested milestones

1
Plan and investigate
Create a scoped pilot policy with clear user-facing remediation guidance.
2
Develop your approach
Observe device evaluation, reporting delay and the resulting access behaviour.
3
Verify and explain
Plan staged rollout and rollback based on the pilot evidence.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Endpoint policy pilot plan
Show the inputs, scope and decisions behind this record. Policy assignment is distinguished from actual device compliance.
2
Device-state results and remediation instructions
Include the evidence supporting your conclusion. The non-compliant user has a documented route to recover access.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your endpoint policy pilot plan needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Microsoft Official Practice Assessment (MD-102)

Check relevance, platform versions and current access terms.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Use an authorised device-management training tenant and disposable or dedicated test devices. Define one compliant and one non-compliant state and confirm licensing.

What a good result looks like

Policy assignment is distinguished from actual device compliance.
The non-compliant user has a documented route to recover access.

Finish the project

Remove test identities, policies and data, restore the initial configuration, and check trial expiry or renewal settings.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.