{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiesnw7kbavwrd47xerxmes44txwecclpybkspa5mwesolsk5gaqwi",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3mea7qvi3jjo2"
  },
  "description": "A new Exchange Online PowerShell cmdlet will allow admins to change the organizer of existing meetings or series, preserving meeting history and updating attendees silently within the tenant. Rollout begins mid-May 2026, requiring no configuration. User-initiated organizer changes in Outlook and ...",
  "path": "/m365-message-center/message/mc1227623/",
  "publishedAt": "2026-02-07T01:00:04.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "554937"
  ],
  "textContent": "**[Introduction]**\n\nWe’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.\n\nA 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.\n\nThis message is associated with Microsoft 365 Roadmap ID 554937.\n\n**[When this will happen]**\n\n**General Availability**\n\n\n\n\n  * **Worldwide and GCC:** We will begin rolling out in **mid-May 2026** and expect to complete by**late June 2026.**\n  * **GCC High and DoD:** We will begin rolling out in **mid-May 2026** and expect to complete by**late July 2026.**\n\n\n\n**[How this affects your organization]**\n\n_Who is affected_ :\n\n  * Administrators managing Exchange Online\n  * Meeting organizers and attendees in your tenant may see updated organizer information when applicable.\n\n\n\n_What will happen_ :\n\n  * Administrators can use a new PowerShell cmdlet to change the organizer of an existing meeting or meeting series.\n  * The new organizer will have full control of the event, including recurrence, description, attendees, and meeting details.\n  * 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.\n  * 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.\n  * **Meeting history is preserved** , supporting continuity and reducing abandoned meeting series.\n  * This feature is**enabled by default** ; no configuration is required.\n\n\n\n**[What you can do to prepare]**\n\nNo action is required. The feature will roll out automatically.\n\nTo prepare:\n\n  * Review upcoming public documentation for the cmdlet when it becomes available (a link will be added to this message).\n  * Update internal processes for organizer transitions, such as role changes or offboarding.\n  * You may test the cmdlet ahead of the user‑initiated organizer change experience coming to Outlook on the web, new Outlook, and Teams.\n\n\n\n**[Compliance considerations]**\n\nNo compliance considerations identified. Review as appropriate for your organization.",
  "title": "MC1227623: Change meeting organizer via PowerShell cmdlet in Exchange Online",
  "updatedAt": "2026-02-07T01:00:04.000Z"
}