How to Change the Meeting Organizer in Microsoft Teams

Changing the organizer of a Microsoft Teams meeting has been one of the most requested admin capabilities in Microsoft 365. Earlier, if a meeting owner left the company or changed roles, admins usually had to cancel and recreate the meeting under a new organizer. Microsoft is now addressing this with a new Exchange Online PowerShell cmdlet: Invoke-ChangeMeetingOrganizer.

This update lets Microsoft 365 admins transfer ownership of an existing meeting or recurring meeting series without rebuilding the invite from scratch. It is especially useful for offboarding, leadership changes, recurring project calls, training sessions, and long-running governance meetings.

What is Invoke-ChangeMeetingOrganizer?

Invoke-ChangeMeetingOrganizer is an Exchange Online PowerShell cmdlet that allows admins to transfer a meeting from the current organizer to a new organizer in the same Exchange Online organization. The meeting can be identified either by its subject or by its unique event ID.

Unlike the older workaround of recreating meetings, this approach helps preserve meeting continuity and reduces disruption for users. For recurring meetings, the transfer applies to future occurrences, either from the next occurrence or from a specified future start date.

Change meeting organizer by subject

If the meeting subject uniquely identifies one meeting, admins can run:

Invoke-ChangeMeetingOrganizer -Identity <OldOrganizer> -Subject "<MeetingSubject>" -NewOrganizer <NewOrganizer>

Replace <OldOrganizer> with the current organizer’s email address, <MeetingSubject> with the meeting title, and <NewOrganizer> with the email address of the user who should own the meeting going forward.

For recurring meetings, ownership transfer starts from the next occurrence by default. If you want the transfer to begin from a specific future date, use the optional -TransferSeriesStartDate parameter.

Change meeting organizer by Event ID

If multiple meetings have the same subject, use the meeting’s Event ID instead. This avoids transferring the wrong meeting.

Invoke-ChangeMeetingOrganizer -Identity <OldOrganizer> -EventId <EventID> -NewOrganizer <NewOrganizer>

If you do not know the Event ID, retrieve it with:

Get-CalendarDiagnosticObjects -Identity "<OldOrganizer>" -Subject "<MeetingSubject>" -ExactMatch $true

Important limitations

  • The new organizer must be in the same Exchange Online organization as the old organizer.
  • Meetings from shared mailboxes and Microsoft 365 Group mailboxes cannot be transferred with this cmdlet.
  • Only meetings stored in the organizer’s default calendar are supported.
  • For Teams-enabled meetings, the Teams online meeting information may not automatically transfer. The new organizer may need to update the meeting series and generate new Teams meeting details.
  • OneDrive attachments or links owned by the previous organizer may need to be re-shared or replaced by the new organizer.
  • The feature is rolling out across supported tenants, so some admins may not see it immediately.

What happens after the organizer is changed?

After the transfer, the new organizer gets control of the meeting and can update the invite, manage attendees, change recurrence, and modify meeting details. Internal attendees generally do not need to accept the meeting again because their calendars are updated silently.

External attendees may receive a clearer transition: one message ending the series from the old organizer and a new invitation from the new organizer. They may need to accept the new invitation to continue attending the series.

When should admins use this?

This capability is useful when an employee leaves the organization, a project owner changes, a department wants a new person to manage a recurring meeting, or a long-running meeting series must remain active without losing continuity.

Key takeaway

Admins can now change the meeting organizer in Microsoft 365 using Exchange Online PowerShell with Invoke-ChangeMeetingOrganizer. It is a major improvement over cancelling and recreating meetings, but admins should still review Teams meeting links, OneDrive attachments, attendee impact, and tenant rollout status before using it in production.