Home labs & practical projects
Prepare a Microsoft 365 administrator handover
A project to do with your own tools, with guidance on what to create and capture.
For existing holders and historical learning. Check the current credential before starting exam preparation.
What you could create
A small organisation is changing its Microsoft 365 administrator. It needs a clear record of privileged access, service dependencies and operational responsibilities.
| Evidence | What to capture |
|---|---|
| Tenant operations ownership map | Show the inputs, scope and decisions behind this record. Ownership of each service is explicit. |
| Administrator transition checklist | Include the evidence supporting your conclusion. Privileged access is reviewed before the outgoing administrator’s account is removed. |
What you'll need
Document, spreadsheet or diagram tool
Invent a tenant with users, groups, two administrators and three business services. Include a stale privileged account and an undocumented ownership gap.
Project record
Keep the working files for tenant operations ownership map 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
No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.
The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.
Suggested milestones
- 1
Plan and investigate
Map administrator roles and service ownership.
- 2
Develop your approach
Define lifecycle, service-health and incident responsibilities.
- 3
Verify and explain
Create a handover checklist with recovery access and verification evidence.
Useful resources
Use these resources to deepen your understanding and check key details.
A useful starting point
Invent a tenant with users, groups, two administrators and three business services. Include a stale privileged account and an undocumented ownership gap.
What a good result looks like
- Ownership of each service is explicit.
- Privileged access is reviewed before the outgoing administrator’s account is removed.
Finish the project
Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.
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.