Operations guide · Lifecycle
Every joiner, role change, and departure changes the tenant.
Chaque arrivée, changement de rôle et départ modifie le locataire.
lire cette page en françaisLifecycle administration turns team events into predictable M365 actions. It reduces forgotten accounts, misaligned licences, and responsibilities that remain assigned to someone who left.
The decision to make
This guide shows what can follow a recurring checklist, what requires a business decision, and what becomes a project.
Joiner: provide what the role needs
Start with the person’s role: required licence, groups, workspaces, devices, and external access. Copying an existing account can reproduce exceptions nobody remembers.
Role change: remove as well as add
A promotion or transfer often adds rights without removing old ones. The checklist compares old and new roles, confirms workspaces still required, and transfers ownership of groups or processes.
Leaver: coordinate access, data, and continuity
Blocking an account is one step. The manager decides what must be transferred, retained, or removed under organizational obligations. Mail, files, groups, and connected applications may have different owners.
After the event: close the loop
A short verification confirms that licensing, groups, responsibilities, and access match the intended result. Complex cases—merger, acquisition, migration, or special retention—are scoped separately.
A simple matrix for assigning the work.
| Situation | Owner | Cadence | Useful evidence |
|---|---|---|---|
| Joiner | Manager + administration | Before day one | Approved checklist |
| Role change | Previous + new manager | On transfer date | Adds, removals, ownership |
| Leaver | HR + manager | Against confirmed date | Block, transfer, follow-up |
Decision checklist
What should be true before considering this area under control.
- Requests start from a known role
- Adds and removals are handled together
- Group ownership is transferred
- Retention decisions remain with the business
- A verification closes every event
Next step
Give lifecycle events an owner and a record.
Compare monthly scope and CAD service levels, then use the readiness list to name events currently escaping your process.