If you manage Microsoft 365 at scale, you already know the pain. Someone leaves the organisation, or moves to a different role, and suddenly their recurring team meeting is in limbo. The options until now were limited: delete and recreate the series (losing history and forcing everyone to reaccept), leave it orphaned, or give the departing user a shared mailbox nobody wants to maintain. The Exchange Online meeting organizer transfer via PowerShell is Microsoft’s answer to a problem that has frustrated admins for years.
This feature is associated with Microsoft 365 Roadmap ID 554937 and is rolling out to Worldwide and GCC tenants starting mid-May 2026.
What Is the Exchange Online Meeting Organizer Transfer Cmdlet?
Microsoft is introducing a new Exchange Online PowerShell cmdlet that allows administrators to change the organizer of an existing meeting or meeting series, without touching Outlook, without forcing attendees to reaccept, and without losing meeting history.
This is an admin-initiated action. The admin runs the cmdlet, specifies the existing meeting and the new organizer, and Exchange Online handles the rest silently in the background. The new organizer immediately gains full control over the event.
What the New Organizer Can Control After Transfer
Once the organizer transfer is complete, the new organizer has full ownership of the meeting. That includes:
- Recurrence settings, modify the schedule, frequency, or end date
- Meeting description and details, update the agenda or any linked content
- Attendee list, add or remove participants
- Meeting properties, change the title, location, or online meeting link
This is genuine ownership transfer, not a delegate arrangement or a shared calendar workaround.
How It Affects Attendees: Internal vs External
This is the most important operational distinction admins need to understand before using the cmdlet.
| Attendee Type | What Happens | Action Required |
|---|---|---|
| Internal (same tenant) | Calendar entry is silently updated to reflect the new organizer | None, no re-RSVP needed |
| External (outside tenant) | Receive two messages: one ending the old series, one inviting to the new series | Must reaccept the meeting invitation |
For most organisations, the majority of recurring internal meetings will be a seamless experience. External attendees will need to take action, so communication planning matters if the affected meeting series has significant external participation.
Meeting history is preserved in both scenarios, which is the critical continuity element that makes this feature genuinely useful.
Rollout Timeline
| Phase | Region | Start | Expected Completion |
|---|---|---|---|
| General Availability | Worldwide | Mid-May 2026 | Late June 2026 |
| General Availability | GCC | Mid-May 2026 | Late June 2026 |
According to Microsoft, this should be rolling out around May 2026. No preview phase has been announced for this feature, it goes directly to General Availability.
How to Use the Meeting Organizer Transfer Cmdlet
Prerequisites
Before running the cmdlet, confirm the following:
- You have Exchange Online PowerShell connected with appropriate admin permissions
- The current organizer’s mailbox is accessible (even if the user is being offboarded, do not delete the mailbox before completing the transfer)
- The new organizer has an active mailbox in the same tenant
Connecting to Exchange Online PowerShell
If you are not already connected, run the following:
powershell
Install-Module -Name ExchangeOnlineManagement -Force
Connect-ExchangeOnline -UserPrincipalName [email protected]Running the Organizer Transfer
The specific cmdlet name and full syntax will be published in Microsoft’s official documentation once the rollout begins. Microsoft has indicated a documentation link will be added to the Message Center post (MC reference applies). When available, the general pattern will follow Exchange Online cmdlet conventions.
Monitor this URL for the cmdlet reference once published: https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell
Until the cmdlet documentation is live, admins can prepare by:
- Identifying recurring meeting series tied to accounts at risk of offboarding
- Establishing an internal process for who requests organizer transfers and under what conditions
- Testing in a non-production tenant as soon as the cmdlet becomes available in your region
Admin Tips
Start with your offboarding checklist. This feature fits naturally into any structured offboarding or role-transition workflow. Add a step to identify and transfer any recurring meeting series the departing user organises.
Do not delete the mailbox too early. Until the transfer is complete, the original organizer’s mailbox needs to remain accessible. Premature mailbox deletion before the cmdlet runs could complicate the transfer. Coordinate with your identity team on timing.
Communicate with external attendees proactively. If a high-visibility meeting series has external participants, give them a heads-up before running the transfer. Two calendar messages arriving unexpectedly can cause confusion, especially in enterprise or client-facing contexts.
Watch for the user-initiated version. Microsoft has confirmed that a future release will allow users to transfer organizer rights themselves, directly in Outlook on the web, new Outlook, and Teams. For user-initiated transfers, the new organizer must accept before the transfer completes. This changes the governance picture, so start thinking about whether you want any policy guardrails in place before that feature lands.
Document your transfers. Even though no compliance considerations have been flagged by Microsoft for this feature, maintaining an internal log of organizer transfers (who was transferred, when, by which admin) is good practice for audit readiness.
License Requirements
The Exchange Online meeting organizer transfer cmdlet is available to all organisations with Exchange Online included in their Microsoft 365 subscription. There is no premium add-on or additional licensing requirement. This applies across standard commercial Microsoft 365 plans that include Exchange Online.
The Paul-Take
This is one of those features that is unglamorous but genuinely impactful. Nobody demos ‘meeting organizer transfer’ at a conference. There is no flashy AI angle. But ask any admin who has managed offboarding at a company with more than a few hundred users and they will tell you this has been a real, recurring problem with no clean solution.
The implementation is sensible. Internal attendees get a silent update, which is exactly what you want. The external attendee experience involves two messages, which is a legitimate technical constraint given how calendar federation works across tenants. Microsoft is being transparent about that rather than hiding it, and that is the right call.
The part I am most interested in is the user-initiated version coming to Outlook and Teams. That is where the volume will be. Admins transfer organizers occasionally. Users want to transfer organizers constantly, when they delegate work, when they share responsibility for a series, when they bring in a new team lead. Getting that experience right in the client, with an acceptance step built in, is the harder and more consequential problem. The admin cmdlet is the foundation. Watch what comes next.
MVP Reference List
- Message Center ID: MC referenced in announcement (specific MC number not published in source)
- Roadmap ID: Microsoft 365 Roadmap ID 554937
- Exchange Online PowerShell Reference: https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell
- Connect to Exchange Online PowerShell: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell