Does this sound familiar?
It’s Friday afternoon.
HR tells you that a department manager has left the company the same day.
You disable the account. Remove the license. Block sign in.
Job done.
But is it really?
Monday morning arrives.
The weekly leadership meeting has no owner. A customer meeting is still scheduled under someone who no longer works for the company. An approval flow has stopped working. A Team no longer has an active owner. And the list goes on…
When someone leaves an organization, the first instinct is usually to think about their identity.
Removing access is important, but it is only half the job.
Every employee leaves behind more than a user account. They leave documents, Teams, Planner plans, Power Automate flows, Copilot agents, recurring meetings, and workflows that quietly keep the business running without IT, or anyone else for that matter, knowing about it. If nobody takes ownership those processes quickly become tomorrows support tickets.
It doesn’t matter if your organization follows a manual checklist or has automated much of the process with Microsoft Entra Lifecycle Workflows, the goal should be the same. Remove access while ensuring the business continues without interruption!
Over the years, I have come to think of offboarding as a business continuity exercise rather than simply an identity management task.
Then Microsoft quietly released a PowerShell cmdlet that made me stop and rethink my entire offboarding process. Not because it solved every problem, but because it solved one that administrators have been pulling out their hair to work around for years.
That cmdlet did not just solve a calendar problem, it reminded me that every offboarding task ultimately has the same purpose – Making sure the business keeps running after someone leaves.
Looking back at my own process, these are the five areas I now review whenever an employee leaves the organization.
1. Review mailbox access and shared resources
Not every mailbox should disappear the moment someone leaves. Managers may need temporary access to emails. Customer conversations may still be active. Legal or regulatory requirements may require the mailbox to be retained for a specific period.
Depending on your organizations policies, you might convert the mailbox to a shared mailbox, assign delegated access, or rely on Microsoft Purview retention policies to preserve the data.
The important part is making an active decision rather than simply removing the license and hoping nothing important is lost.
2. Transfer recurring meetings
This is the item that made me rethink my process.
For years, recurring meetings have been one of the biggest gaps in the Microsoft 365 offboarding process.
The employee leaves but their recurring meetings remain. The calendar entries still exist, attendees continue joining every week, but the organizer is someone who no longer works for the company.
If changes are needed later, things quickly become messy.
Many organizations have kept former employees licensed simply because nobody wanted to recreate dozens of recurring meetings. Others cancelled the meetings entirely and asked the new owner to send fresh invitations, creating unnecessary disruption and confusion.
Microsoft has finally introduced a supported solution through the Invoke-ChangeMeetingOrganizer. PowerShell cmdlet.
The cmdlet allows administrators to transfer ownership of future recurring meetings from one mailbox to another without recreating the meeting series from scratch.
A simple example looks like this:
Invoke-ChangeMeetingOrganizer `
-Identity "alex.wilson@contoso.com" `
-Subject "Weekly Leadership Meeting" `
-NewOrganizer "sarah.johnson@contoso.com"For meetings with internal attendees the experience is generally seamless. The meeting remains in attendees calendars while ownership moves to the new organizer.
There are a few important things to be aware of.
If external attendees are invited they will receive updated invitations and need to accept them again.
If meeting attachments are stored in the former organizer’s OneDrive, those files do not automatically move with the meeting. Permissions and file locations should be reviewed as part of the handover.
If the meeting is a Microsoft Teams meeting, it is also worth validating the meeting after the transfer. Teams specific information may need to be refreshed under the new organizer to ensure everything continues working as expected.
Before running the cmdlet, I would ask myself a few simple questions.
- Is the new organizer already an attendee?
- Does the new organizer actually own the business process or project?
- Are meeting attachments stored in the former organizer’s OneDrive?
- Are there external attendees who should expect a new invitation?
- Would recreating the meeting make more sense if ownership is changing significantly?
Even with those considerations, this cmdlet removes one of the most frustrating parts of offboarding. It is one of those features that administrators have been asking for over many years, and I suspect it will quietly become part of many organizations’ standard offboarding procedures.
3. Transfer OneDrive ownership
OneDrive often contains far more than personal files.
Project documentation, customer deliverables, meeting notes, presentations, and shared working documents frequently live there, even if they probably should have been stored in SharePoint.
Before removing a license or deleting an account, make sure the right people can access the user’s files. Microsoft provides several ways to delegate access during the retention period, giving managers and colleagues time to complete the handover.
This is also a good opportunity to identify information that should really be moved into a team or departmental SharePoint site instead of remaining tied to an individual.
4. Review Teams and Microsoft 365 Groups
People often create Teams for projects, departments, or other initiatives and then become the only owner, even though good governance should always require at least two owners.
If they leave without another owner in place, simple administrative tasks suddenly become much more complicated.
Before disabling an account, check whether they own any Teams or Microsoft 365 Groups and ensure each workspace still has at least one active owner. While you are there, it is also worth reviewing whether any external guest users still require access.
A few minutes spent checking ownership can save a lot of confusion later.
5. Check Power Automate flows, Power Apps and Copilot Agents
This is one that catches many organizations by surprise.
A business critical approval process, notification, integration, or even a Copilot agent may be running under a personal account. Everything works perfectly until that account is disabled.
Then it just stops and no one knows why, but I can assure you that IT gets the blame.
Review any flows, apps, automations, or agents owned by the departing employee and transfer ownership where appropriate. Better yet, build important business solutions using shared ownership or service accounts whenever possible.
Good offboarding is good governance
When we talk about governance, the conversation often revolves around sensitivity labels, retention policies, access reviews, or preparing for Microsoft 365 Copilot.
Those things are important but governance is not an objective in itself.
Its purpose is to make sure the business continues to function when people change roles or leave the organization.
A recurring management meeting should not disappear because its organizer has left.
An approval flow should not stop because it belonged to a single employee.
A Team should not become ownerless because nobody thought to check.
Good governance removes single points of failure before they become business problems.
That is why I like features like Invoke-ChangeMeetingOrganizer.
It is not a feature that will make headlines, but for administrators it solves a problem that has existed for years and makes one of the most important operational processes in Microsoft 365 just a little bit better.
At the end of the day, good offboarding is not about disabling accounts.
It is about making sure the business hardly notices that someone has left.
And that is exactly what good governance is all about.
