Start before the final working day
A change in the team affects more than one user account. Documents, shared mailboxes, project groups and ongoing conversations still need clear owners. Begin early with an overview of responsibilities. Which information must be handed over, who will answer questions and which access should end? HR, the relevant department and IT should share the same timetable. This creates an agreed process instead of a search for important information after the employee has already left.
Separate access from retention
Ending access is not the same decision as deleting all associated information. Microsoft describes several steps for blocking access and handling mailbox and OneDrive content in an organised way. The appropriate steps need to be checked against the actual environment. Agree who is authorised to access business information after handover. Questions about retention, personal material and deletion belong with the responsible organisational and privacy contacts. Avoid treating a technical account change as a substitute for those decisions.
Include groups and devices
Build a checklist that extends beyond the individual mailbox. It may include group membership, ownership roles, applications, mobile devices and external services. Check whether another authorised person will take responsibility for shared workspaces. Do not simply share the previous password to make the handover easier. Named access and understandable permissions make it possible to establish who performs each task later. Hybrid environments also require attention to the authoritative local identities and the synchronisation processes connecting them to cloud services.
Confirm completion clearly
After the agreed date, IT should verify the intended changes and report outstanding points. Together with the department, check that transferred files can be found and necessary workflows still function. Document the handover without passwords or unnecessary personal information. A useful completion record identifies finished tasks, remaining exceptions and their owners. The same structure helps with internal role changes: new rights are granted for a purpose, while old rights are deliberately reviewed rather than allowed to accumulate indefinitely over time.
Further reading: Microsoft Learn: Remove a former employee.