Summary

Microsoft is introducing a new Exchange Online PowerShell cmdlet that allows admins to change meeting organizers without recreating meetings or losing history. The cmdlet will roll out starting mid-May 2026. User-driven organizer changes are planned for Outlook and Teams in a future release.

When users switch roles or leave the organization, they don’t just hand over their responsibilities; they often leave behind a calendar full of meetings they still “own.” For admins, managing recurring meetings owned by inactive organizers can quickly become a major challenge.

These meetings hold more than schedules: attendance reports, shared history, and Loop-based notes. And in Microsoft 365, there simply hasn’t been a supported way to change the organizer of an existing meeting.

Until now, admins have been forced to rely on disruptive workarounds like:

  • Cancelling and recreating meetings under a new organizer,
  • Letting important meetings continue under inactive accounts,
  • Scheduling critical sessions through shared mailboxes for continuity.

Now, Microsoft is finally closing this long-standing gap with a new Exchange Online PowerShell cmdlet that allows admins to change meeting organizer. Let’s take a closer look at what this update brings!

Why Transferring Meeting Ownership Matters

Let’s start by understanding why transferring a meeting organizer is so important in Microsoft 365. When a meeting is tied to an inactive or orphaned organizer, recurring meetings can quickly become difficult to manage. Transferring the organizer to a new active user helps ensure meetings continue without disruption and that critical meeting data remains accessible. Below are some common scenarios where this capability becomes critical:

  • Orphaned Meetings After User Offboarding
    When a user offboards, meetings organized by them can become orphaned and may eventually be deleted. This can disrupt ongoing schedules, remove access to meeting history and artifacts, and leave teams without a clear owner to manage future meetings.
  • Maintaining Momentum During Leadership Changes
    Project reviews, training sessions, and governance meetings should be handed over to a new owner to maintain project momentum. Handing over ownership ensures that decisions continue to be tracked, progress isn’t lost, and knowledge is preserved.
  • Preserving Records for Compliance and Audits
    When a finance team or compliance department conducts quarterly financial reviews or regulatory audits, meetings often include critical records such as attendance reports, recordings, and Loop-based notes. Updating the organizer of these meeting ensures these records remain accessible for follow-ups and audit purposes.
  • Keeping Recurring Cross-Functional Meetings on Track
    For recurring meetings involving multiple departments like weekly engineering syncs or product roadmap reviews, an active organizer is essential to update schedules, manage participants, and document decisions.

Overview of New Exchange Online PowerShell Cmdlet

To make the above scenarios easier to handle, Microsoft is introducing a new Exchange Online PowerShell cmdlet. Admins managing Exchange Online can use this cmdlet to change the organizer of an existing meeting or a recurring meeting series. It helps transfer meeting ownership seamlessly, keeping schedules intact when the organizer’s role changes or offboards.

Rollout Timeline for PowerShell Cmdlet to Change Meeting Organizer

Microsoft is rolling out the general availability of the new Exchange Online PowerShell cmdlet during the following periods:

  • Worldwide and GCC tenants – Rollout begins in mid-May 2026 and is expected to complete by late June 2026.
  • GCC High and DoD tenants – Rollout begins in mid-May 2026 and is expected to complete by late July 2026.

Once the rollout reaches your tenant, the capability will be available automatically and requires no admin action.

What Happens When an Admin Changes a Meeting Organizer?

When an admin changes the meeting organizer using the new cmdlet, ownership is transferred without breaking the meeting series or disrupting attendees. The meeting continues seamlessly under the new organizer with full continuity and control. Below are the key outcomes you can expect after the transfer:

Full Control for the New Meeting Organizer

The new organizer gains full control of the transferred meetings, ensuring they continue without disruption. After the transfer, the new organizer of the Microsoft Teams meeting can perform the following actions:

  • Modify recurrence patterns,
  • Update the meeting description,
  • Add or remove attendees,
  • Manage meeting options and meeting details, etc.

Seamless Experience for Internal Attendees

When the meeting organizer is modified, attendees within the tenant do not need to re-RSVP. In other words, users don’t need to accept or decline the meeting invite again. The existing meetings on their calendars are silently updated with the new organizer information, ensuring internal meetings remain seamless and disruption-free.

Meeting Transfer Notification for External Participants

When a meeting’s ownership is transferred and it includes external users, the updates are clearly notified to avoid confusion. The external meeting participants will receive the below two meeting messages:

  • One message ending the meeting series from the previous organizer.
  • A new meeting invitation for the series starting with the new organizer.

External attendees must accept the new invitation to continue attending meeting series.

Continuous Access to Meeting History and Artifacts

Long-running meetings, such as those tied to compliance reviews, audits, or ongoing projects, need to retain their historical context even when organizers change. When ownership is transferred, all meeting history, recordings, notes, and related artifacts are preserved and accessible to the new organizer and attendees.

Note on User-Initiated Organizer Changes (Coming Later)

Soon, users will be able to transfer meeting organizer directly from the Modern Calendar in Outlook on the web, the new Outlook, and Teams. Unlike admin-initiated transfers via PowerShell, the user-initiated transfer will only take effect after the new organizer accepts the meeting.

That’s all on this update! Get ready to test the new PowerShell cmdlet once it becomes generally available. Keep an eye on this blog for updates and hands-on details as soon as it rolls out! 🚀 If you have any questions or feedback, feel free to leave a comment below. We’re happy to help!