PRACTICE / MODULE 009 / MICROSOFT

A new employee
starts Monday.

Learn the relationships, make the configuration decisions, and prove access works. Our fictional Microsoft 365 tenant responds to what you change—and lets you troubleshoot what breaks.

← Review Microsoft 365 Fundamentals Explore the Microsoft topic hub →

03 / INTERACTIVE MICROSOFT 365 TENANT

Own the ticket. Verify the outcome.

Configure Alex's fictional account, inspect validation evidence and resolve a second SharePoint incident. Deliberately try an incorrect license, role or group to see what fails. No live Microsoft services are accessed.

JOELEarns / SIMULATED ADMIN CENTERNorthstar Services Microsoft 365

TRAINING DATA ONLYONBOARDING NS-2041 OPEN

ACTIVE EMPLOYEEAlex Morganalex.morgan@northstar.example.test

VERIFIABLE CHECKS0 / 7Current modeled state

SCENARIO PROGRESS0 / 2Onboarding + incident

LATEST SIMULATED RESULTBegin by creating Alex's standard user account.

MICROSOFT 365 / USERS / ACTIVE USERS

Identity profile

A user object is the starting point, not the complete onboarding. Confirm the department and avoid accidentally creating a privileged identity.

Alex Morganalex.morgan@northstar.example.testPending creation

NOT CREATED

Department

Department information should match the approved HR request.

Why this matters

Entra ID stores the identity and sign-in properties. Mailbox provisioning, group-based access and subscription assignment are distinct tasks.

SIMULATED ACTIVITY LOG1 events

TICKET
NS-2041 opened: Alex Morgan joins Finance on Monday.

SESSION / TICKET NOTESFictional data

Copy the current simulated status for a practice ticket. No information is sent to any external service.

JOELEarns / SIMULATED MICROSOFT 365 TICKET NOTES
Organization: Northstar Services (fictional)
Employee: Alex Morgan · Finance
UPN: alex.morgan@northstar.example.test
Ticket: NS-2041 / New Hire
Account created: No
Department: Operations
Usage location: unset
License: None
Finance Team M365 Group: Not member
Finance Reports Security Group: Not member
Administrator role: None
MFA required: Yes
Checks (computed from current state):
- FAIL: Identity profile — The user hasn't been created.
- FAIL: Usage location — Set Alex's usage location before assigning the license.
- FAIL: Approved service license — The modeled license cannot be assigned until a usage location is specified.
- FAIL: Exchange mailbox — No active Exchange service plan or account prerequisites are missing.
- FAIL: Finance SharePoint site — SharePoint licensing is not ready.
- FAIL: Finance reporting app — Alex is not in Finance Reports Access; this security group is separate from the Finance Team site group.
- FAIL: Security baseline and privileges — No user to evaluate.
Note: Fictitious training scenario. No live Microsoft tenant, accounts, licenses, mailboxes or policies were changed.

LEARN AND PRACTICE / YOUR CHOICE

Administration is more than clicking Save.

Understanding identity, service entitlement, resource permission and security controls is the foundation for reliable Microsoft 365 support.

Review the learning guide →Explore Conditional Access →Back to Microsoft →