Bulk Transfer of Teams Meeting Organizers in Exchange Online — Recurring Series Outside Transfer Period Not Processed

Indicators

• Recurring Teams meeting series that started before the transfer window remain owned by the original organizer after running Invoke-ChangeMeetingOrganizer
• Bulk organizer transfer requests complete but leave orphaned recurring series under the old organizer
• Users offboarded but their historical recurring Teams meetings still list them as organizer in calendar views
• New organizer cannot edit or manage transferred recurring meeting series because ownership was not transferred

Likely causes

• Invoke-ChangeMeetingOrganizer cmdlet scope limitation: it does not process recurring meeting series whose start date precedes the selected transfer period
• Native cmdlet is designed for single meeting transfers, not bulk organizer migration workflows spanning historical recurring series

Diagnostic steps

1. Identify users/mailboxes whose meetings need organizer transfer (e.g., offboarding list, role change list)
   Establish scope of bulk transfer operation
2. Connect to Exchange Online PowerShell: Connect-ExchangeOnline -UserPrincipalName admin@tenant.onmicrosoft.com
   Establish authenticated session to Exchange Online for cmdlet execution
3. Enumerate Teams meetings owned by the source organizer using Get-CalendarEvents or Get-MgUserCalendarView, noting which are single occurrences vs. recurring series
   Determine which meetings are eligible for the native cmdlet and which require the supplementary script
4. Identify recurring meeting series whose start date precedes the intended transfer period — filter by RecurrencePattern and StartDateTime properties
   Isolate the gap set that requires the bulk PowerShell script
5. Validate that the new organizer's mailbox is licensed for Teams: Get-MgUserLicenseDetail -UserId neworganizer@tenant.com | Where-Object {$_.ServicePlans.ServicePlanName -like '*TEAMS*'}
   Prevent transfer failures due to licensing or mailbox state issues

Resolution path

• Connect to Exchange Online PowerShell using Connect-ExchangeOnline with an account that has permissions to modify both source and target mailboxes
• Use the native Invoke-ChangeMeetingOrganizer cmdlet to transfer standard/eligible meetings within your desired date range: Invoke-ChangeMeetingOrganizer -SourceMailbox sourceuser@tenant.com -TargetMailbox neworganizer@tenant.com -StartDate YYYY-MM-DD -EndDate YYYY-MM-DD
• For recurring meeting series that started before the selected transfer period (not handled by the native cmdlet), download and run the supplementary PowerShell script from the o365reports.com article to transfer eligible recurring series in bulk
• Process transfers in bulk by iterating the script over the list of affected organizers/meetings, logging each transfer attempt
• Confirm each transfer completes successfully and log any failures for manual remediation or re-attempt

Prevention

• Include meeting organizer transfer as a standard step in the user offboarding runbook, executed before mailbox deletion or license removal
• Maintain co-organizers on critical recurring Teams meetings so ownership survives an organizer's departure without requiring transfer
• Schedule periodic audits of recurring Teams meetings owned by users in offboarding pipeline to proactively transfer ownership
• Document the limitation of Invoke-ChangeMeetingOrganizer in internal runbooks so engineers know to use the supplementary script for recurring series

Tools

• Invoke-ChangeMeetingOrganizer (Exchange Online cmdlet for transferring meeting organizers)
• Exchange Online PowerShell (ExchangeOnlineManagement module)
• Microsoft Graph PowerShell SDK (for calendar enumeration)
• Supplementary bulk transfer PowerShell script (from o365reports.com article)

References

• Bulk Transfer Meeting Organizers Using PowerShell — Office 365 Reports