MC1227623 - Change meeting organizer via PowerShell cmdlet in Exchange Online

Introduction

We’re adding a new PowerShell cmdlet that lets administrators change the organizer of an existing meeting or meeting series in Exchange Online. This feature supports continuity when a meeting owner changes roles, goes on leave, or is offboarded—removing the need to recreate long‑running series. After the transfer, the new organizer can update meeting properties, and attendees within the tenant won’t need to re‑RSVP.

A future release will enable users to change the organizer directly in Modern Calendar experiences in Outlook on the web, the new Outlook, and Teams. For user‑initiated transfers, the new organizer must accept the meeting before the transfer completes.

This message is associated with Microsoft 365 Roadmap ID 554937.

When this will happen

General Availability 

• Worldwide and GCC: We will begin rolling out in mid-May 2026 and expect to complete by late June 2026.
• GCC High and DoD: We will begin rolling out in mid-May 2026 and expect to complete by late July 2026.

How this affects your organization

Who is affected:

• Administrators managing Exchange Online
• Meeting organizers and attendees in your tenant may see updated organizer information when applicable.

What will happen:

• Administrators can use a new PowerShell cmdlet to change the organizer of an existing meeting or meeting series.
• The new organizer will have full control of the event, including recurrence, description, attendees, and meeting details.
• For attendees within the tenant, the existing event on attendees’ calendars will be silently updated to reflect the new organizer. These attendees won't need to decline or reaccept the meeting.
• Attendees outside the tenant will receive 2 meeting messages - one ending the series with the previous organizer and another inviting them to a series with the new organizer. These attendees should reaccept the meeting.
• Meeting history is preserved, supporting continuity and reducing abandoned meeting series.
• This feature is enabled by default; no configuration is required.

No action is required. The feature will roll out automatically.

To prepare:

• Review upcoming public documentation for the cmdlet when it becomes available (a link will be added to this message).
• Update internal processes for organizer transitions, such as role changes or offboarding.
• You may test the cmdlet ahead of the user‑initiated organizer change experience coming to Outlook on the web, new Outlook, and Teams.

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.