Transferring Recurring Meetings During Offboarding Just Got a Supported Answer
Exchange Online's new Invoke-ChangeMeetingOrganizer cmdlet lets you hand off a departing employee's recurring meetings without recreating them, but it works one series at a time and has real gaps admins need to plan around.
The gap this closes
Ask any MSP engineer what happens to a departing employee's recurring meetings, and the honest answer has usually been that someone deletes the series and rebuilds it from scratch, losing history and irritating every attendee in the process. Exchange Online now has a supported way to do this properly. The new Invoke-ChangeMeetingOrganizer cmdlet hands an existing meeting or series to a new organizer without touching the underlying event. It shipped as generally available, enabled by default, with the worldwide and GCC rollout completing around July 2026 and GCC High and DoD trailing into August.
How it actually works
Run the cmdlet against the departing user's mailbox, target a meeting by subject or event ID, and name the new organizer. Exchange moves the series forward from the next instance, or from a future date set with the TransferSeriesStartDate parameter. Internal attendees see nothing: their calendar entries update silently, and personal touches like reminders, categories, and privacy settings survive the move. Attendees outside the tenant, and anyone on a hybrid on-premises mailbox, are not so lucky. They get a cancellation for the old series followed by a fresh invite for the new one, and they have to re-RSVP.
The constraints that keep this out of one-click territory
- It runs one meeting per invocation. A departing employee with a dozen recurring series means a dozen separate commands, not a single sweep.
- Only the default calendar is in scope. Shared, room, and group mailboxes aren't supported; add the new organizer to those mailboxes directly instead.
- Once a series is transferred, the portion still sitting on the old organizer's calendar can't be transferred again.
- Teams online meeting ownership does not follow the transfer. The new organizer has to manually rebuild the join link and meeting options every time.
Put it in the runbook, not the panic button
Because the external attendee experience is a visible cancel-and-reinvite, this belongs in the scheduled leaver process rather than something a technician runs reactively after a ticket comes in. Enumerate the departing user's recurring series ahead of the last day, decide who inherits each one, and use TransferSeriesStartDate to time the cutover deliberately rather than triggering client-facing cancellations by accident. Add rebuilding the Teams link as its own checklist item for the new organizer, and test with -WhatIf before running it against a real client tenant.
How many recurring series are sitting on your soon-to-be-former admins' calendars right now, and does your offboarding checklist already account for them?