💡 Our Technical Review in summary
Summary
- Microsoft is introducing a new PowerShell cmdlet for Exchange Online that allows administrators to change the organizer of an existing meeting or meeting series.
- This feature is designed to ensure business continuity when a meeting owner changes roles, goes on leave, or is offboarded from the organization.
- The update removes the long-standing requirement to manually delete and recreate recurring meeting series when the original owner is no longer available.
- The rollout is scheduled to begin in mid-May 2026 and reach completion by late July 2026 across all environments (Worldwide, GCC, GCC High, and DoD).
Impact
- Administrative Control: IT Admins can now programmatically transfer meeting ownership, providing a solution for “orphaned” meetings.
- New Organizer Capabilities: The designated new organizer receives full permissions to modify meeting properties, including the description, attendee list, and recurrence patterns.
- Internal Attendee Experience: For users within the same tenant, the calendar event will be updated silently. No action or re-RSVP is required from internal participants.
- External Attendee Experience: Participants outside the tenant will receive two notifications: a cancellation from the original organizer and a new invitation from the new organizer. These users will need to re-accept the meeting.
- Feature Roadmap: While initially restricted to PowerShell, a future update will enable end-users to initiate these transfers directly within Outlook on the web, the “new” Outlook, and Microsoft Teams.
Action Required
- Update Offboarding Procedures: Incorporate the new PowerShell cmdlet into your organization’s offboarding and role-transition checklists to manage calendar continuity.
- Monitor Documentation: Watch for the specific cmdlet syntax and parameters which will be published in official Microsoft documentation closer to the May 2026 release date.
- Internal Communication: If your organization frequently collaborates with external partners, prepare them for the “Cancel/Re-invite” workflow that occurs during an organizer transfer.
- Testing: Once available, test the cmdlet with a sample meeting series to understand the synchronization behavior before deploying it for critical executive or departmental meetings.
Microsoft Official Update
Service: N/A
Category: stayInformed
Severity: normal
[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.
[What you can do to prepare]
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.
