Microsoft 365 Joiner, Mover, Leaver and Endpoint Onboarding Lab
Role Fit
This project is best aligned with Microsoft 365, IT Support, and Modern Workplace roles. It demonstrates practical administration across user lifecycle tasks, endpoint management, access changes, and repeatable troubleshooting.
Project Summary
This project is a focused Microsoft 365 support-admin lab built around practical, repeatable tasks rather than broad tenant theory. The core idea is to connect user lifecycle work with endpoint onboarding and support thinking, so the project shows how identity, groups, licensing, devices, and service access affect each other in real admin work.
What this project is meant to prove
- user administration is easier when identity, access, and device state are treated as separate layers
- joiner, mover, and leaver work can be documented as a clear support flow rather than scattered admin actions
- endpoint onboarding is more useful when connected to compliance, policy, and application outcomes
- Microsoft support work is stronger when the right admin centre is chosen deliberately
Tools and Technologies
- Windows 11 VM
- Microsoft 365 admin centre
- Entra admin centre
- Intune admin centre
- Teams
- SharePoint
- GitHub or documentation repository
Intended Build
- a small Microsoft tenant lab
- several users and groups with different access paths
- joiner, mover, and leaver workflow examples
- one Windows 11 device enrolled into Intune
- one compliance policy
- one configuration profile
- one deployed application
- Teams and SharePoint access examples
- troubleshooting notes tied to realistic support scenarios
Delivery Scope
1. Tenant and User Lifecycle
- Create the tenant and test users
- Build the joiner, mover, and leaver process
- Record group assignment and access changes
2. Endpoint Management
- Enrol a Windows 11 VM into Intune
- Apply compliance and configuration policies
- Push one application
- Review device state and compliance results
3. Support and Documentation
- Build a Teams and SharePoint access example
- Write a failed sign-in KB article
- Write a device non-compliance KB article
- Record admin decisions, limitations, and screenshots
What a finished version should show
- tenant scope and licence note
- joiner, mover, leaver checklist
- device enrolment steps
- policy summary
- screenshots from the right admin centres
- short support write-ups for common access and compliance problems
- admin decisions and limitations of the lab
Evidence worth capturing
- user creation and group assignment
- Intune enrolment and device state
- compliance results
- application deployment result
- Teams or SharePoint access validation
- sign-in or audit evidence where available
- one ticket-style workflow from request to validation
Technical Assumptions
This is a tightly scoped support-admin lab, not an enterprise rollout. The purpose is to show realistic administration and troubleshooting within the limits of a test tenant and trial licensing.
Key Risks
- Licensing confusion
- Enrolling the wrong device
- Weak documentation
- Spending too long in admin portals without capturing usable evidence
Current State
This project is still in progress, but the direction is already clear: keep it small, support-focused, and evidence-driven. The finished version should read like practical administration work, not like a list of portal features.
Interview Talking Point
The best way to explain this project in an interview is as a ticket flow: what the request was, which admin centre was checked first, what change was made, what the user experienced, and how the fix was documented.