You can now change a meeting organizer; in a shared mailbox, you cannot

If you run a Microsoft 365 tenant, this week you have on your desk a feature we have been asking for over the years: changing the organizer of a meeting without cancelling it and recreating it. The notice is message centre post MC1472028, published on 14 September 2026, and the worldwide rollout of the first phase runs from late September to late October. It arrives, in Microsoft's words, "enabled by default and requires no tenant configuration". Which means there is nothing to approve. It is already landing.

And here is the part that does not make the headline. The case that made you want this feature for years — the weekly meeting of someone who left in March, still sitting in twelve people's diaries, that nobody can edit — is exactly the case where you will not be able to use it, if you previously followed the offboarding guide Microsoft itself publishes. Not because of a bug: because of the order of the steps.

What exactly is arriving, and in which clients

The mechanics are what anyone would have sketched on a napkin: in the calendar, right-click the meeting, Change organizer, type the person's name, optionally add a message, send. The chosen person gets a request and has to accept it — or decline — before the organizer actually changes. In a recurring series, the change "affects only future meeting instances"; earlier ones stay with the original organizer.

The first thing to check is where the button shows up, because that is where half the estate falls over. The notice lists as affected Outlook on the web, the new Outlook for Windows, the Microsoft 365 calendar inside Teams and Exchange Online — the last of those as the platform behind it, not as a client where you press anything. And then comes the sentence you will have to explain to your help desk: "Classic Outlook for Windows isn't supported". If your estate is still mostly on the old Outlook — and in Spanish SMEs it is — the feature exists but your people cannot see it. Before you write the internal procedure, check which client they actually have in front of them.

The notice's rollout calendar has its own small print by ring: worldwide from late September to late October 2026; GCC, early to late October; GCC High and DoD, early to late November. And what is landing now is phase 1 only. About the other two, the notice says plainly that "Phase 2 and Phase 3 timing will be announced separately", which in the message centre means precisely what it looks like.

The list of what cannot be transferred

The support documentation lists the eligibility requirements, and they are worth reading in full before promising anything, because each line closes off a real case:

• "The meeting or instance must be in the future." A single meeting cannot be transferred "after it has started", and "a recurring series in the past cannot be transferred".
• "The meeting must be a non-online meeting." This is the big one, and we come back to it shortly.
• You must be the current organizer or have delegate edit access. That is what lets you do it on behalf of somebody who has already gone, and therefore it is the first thing you lose if you rush the account.
• You can pick only one person, and they have to be "in the same organization or tenant". No handing the meeting to a customer or a supplier.
• Work or school account: "Personal Outlook.com accounts aren't supported". And the meeting has to live on the organizer's primary calendar.
• Excluded: drafts, cancelled meetings, meetings on a group calendar, encrypted meetings and — underlined — "meetings stored in Group or Shared mailboxes".

Step 4 of the offboarding guide says "shared mailbox"

Microsoft publishes an official procedure for removing a former employee. Seven steps, numbered. Step 4 is titled, literally, "Forward a former employee's email to another employee or convert to a shared mailbox". It is the step everybody takes, and rightly so: it preserves the history, keeps the address alive for customers who still write to it, and lets you drop the licence without losing anything.

Put the two sentences side by side. The conversion documentation says that "all of the existing email and calendar are retained in a shared mailbox that several people can access". The new feature's documentation says you cannot transfer "meetings stored in Group or Shared mailboxes". Side by side they point the same way: step 4 of the guide leaves that person's meetings in the one place the new feature cannot reach. You keep the calendar, yes — but you keep it in museum mode.

This needs bounding honestly, because it is our reading and not a Microsoft statement: no document describes the interaction between the two. Nobody in Redmond has written "convert the mailbox and you lose the button". What exists are two documents that, read together, point the same way. If this genuinely affects you, the check is short: convert a test mailbox holding a future non-online meeting and see whether Change organizer is still there.

And a precision that takes the drama out of it, because it sits in the same step 4 document and keeping quiet about it would be cheating: the conversion can be undone. Literally, "you can convert a shared mailbox back to an individual user's private mailbox later if needed". So it is not a bricked-up door: it is a locked one. If you overshot, the way back exists — convert it back and re-licence it — but that means touching the account of someone who has left all over again and paying for the licence you had removed. That is why we recommend the order: not because it is irreversible, but because getting it right first time costs nothing and undoing it does not.

And that same step 4 still says: cancel them all

Inside that step 4 there is a section titled Cancel Outlook meetings. It says this: "Make sure to cancel all meetings that the former user had on their calendar. This lets people remove the meetings created by the former user." So no, the guide does not forget the calendar. It remembers it perfectly well. The thing is that it only knows one thing to do with it, and that thing is cancelling.

And right after it comes the sentence that explains why the section exists, and the one that reaches your help desk as a ticket: "If the person had meetings that booked equipment or rooms, they won't be available to be booked until those meetings are canceled." Translated into a real office: the big room is still busy on Tuesdays from 10 to 12 for somebody who left in March, the resource mailbox has no way of knowing, and people end up booking the small one and complaining there are no rooms.

This is the part we genuinely think is worth telling. As of this week there is a button for not having to cancel: you hand the meeting over, the room stays booked, attendees do not lose the appointment, and the resource changes owner along with it. And the official advice — the one the technician offboarding somebody tomorrow is still going to read — remains "cancel them all", and it lives inside the very step that, run first, takes the button away. It is not a Microsoft contradiction: the offboarding documentation and the calendar documentation are written by different people, and the one who pays the difference is whoever executes both documents on the same Friday afternoon.

The other clock: thirty days

Whoever decides not to convert the mailbox does not have unlimited time either. Step 6 of the same guide — removing the licence — spells it out: "when you remove or delete a license, the former employee's email, contacts, and calendar are retained for 30 days, and are then deleted permanently". And step 5 repeats the window for a deleted account: "after you delete an employee's account, the content in their OneDrive and Outlook is retained for 30 days".

And here it pays not to stretch the window beyond what it says, because it is easy to misread. Thirty days is how long the data is kept, not a promise that the button keeps working for thirty days. The transfer requires being the organizer or having delegate edit access, and delegation needs licensed mailboxes at both ends; so the moment you remove the licence, the prudent assumption is that the window to operate closes before the retention one does. Data still being there does not mean you can touch it. It is the same pattern as other Microsoft 365 offboarding stories we have covered: Project Online had something similar, and we wrote it up in when the licence goes and there is no export left.

The sequence, in the order that matters

This is what we would take into an offboarding from this week on. It is not a list of tips: it is a sequence, and the value is in where each item falls relative to the others. The right-hand column is the one nobody usually writes down.

Steps 2, 3 and 4 of this sequence come before step 4 of Microsoft's guide. Written like that it sounds like a tongue-twister, which is why it gets skipped. Put another way: you fix the calendar while the mailbox still belongs to a person.

What phase 1 still does not fix

The requirement worth labouring is the one that hurts most, because it rules out half the cases: today the feature only accepts non-online meetings. The weekly committee meeting, the dev team stand-up, the customer review — all with their Teams link — are outside phase 1. In other words: a tool for handing meetings over arrives at precisely the historical moment when almost no meeting is "non-online".

Phase 2 promises to cover them, and brings a detail worth knowing before you sell it internally: "for Teams meetings, the transfer will generate a new Teams meeting link owned by the new organizer". The link changes. Whatever was in the body of the invite, the bookmarks people saved, the link pasted into the project document: all of it points at the old one. And the notice itself reminds you to tell users that external attendees will have to respond to the replacement invitations.

And then there is phase 3, which is the one that really describes how much hangs off a meeting. It lists what will one day be transferable: "chat, meeting options, transcripts, recordings, agenda, notes, and attendance reports". Seven things. Until it ships, all of that stays attached to the previous organizer's account — recordings included, a problem we covered in full in the recording that lives in the OneDrive of someone who left — with everything that implies for an audit or a dispute. It is the same lesson we wrote about in Teams chats are not in your backup: the object you see in Teams and the object an administrator can move or copy are not the same object.

When we would not use it

A feature being new does not make it the right answer. There are four cases where we would still cancel and recreate, which is ugly but predictable:

• Long series where the history matters. The change affects only future instances, so you end up with a series split between two owners. If somebody is going to audit who convened what, two clean series explain themselves better than one two-headed one.
• Meetings with many external attendees. If they are going to have to accept another invitation anyway, the transfer saves you nothing on the expensive part, which is writing to them.
• Encrypted meetings. Not eligible, full stop. If your board convenes with encryption on, do not waste the afternoon looking for the button.
• Role changes, not leavers. The notice says that "the previous organizer is not automatically added as an attendee". In an offboarding that is irrelevant, because the person has gone. But if what you are doing is handing the weekly meeting to a colleague because you are changing jobs, you have just removed yourself from your own meeting and nobody warned you.
• Estates on classic Outlook. Publishing a procedure that requires a button half the staff do not have generates more tickets than it closes. Either you migrate the client, or IT runs the procedure from Outlook on the web.

What this says about your offboarding procedure

Microsoft's procedure does look at the calendar; credit where it is due. The thing is that it looks at it with the only tool that existed when it was written, which was cancelling. And that section is still there, inside the step that also takes the alternative away from you. It is not an oversight: it is documentation that has not yet caught up with what changed this month in the product it documents.

What we recommend, and it is cheap to write down, is that an offboarding should not be called closed until somebody has opened that calendar and sorted the future meetings into two piles: the ones that can be transferred and the ones that have to be recreated. It is one more line on the checklist. Until this month that line always ended in "cannot be done"; now, for a share of the cases, it ends in a button. The only thing deciding which of the two you get is where on the list it is written.

Sources (checked 16 Oct 2026): the publication date (14 September 2026), the rollout calendar by ring, the sentence "this feature is enabled by default and requires no tenant configuration", the list of affected products with classic Outlook for Windows excluded, picking one person "in the same organization or tenant", the sentence "Phase 2 and Phase 3 timing will be announced separately", the new Teams link in phase 2, the seven items in phase 3, that "the previous organizer is not automatically added as an attendee", and the preparation actions (inform the help desk, the new organizer must accept, external attendees respond to replacement invitations, verify access to OneDrive content) all come from message centre post MC1472028, "Outlook: Change the organizer of meetings". The eligibility requirements and literal exclusions — meeting in the future, non-online meeting, organizer or delegate with edit access, work or school account, primary calendar, no drafts, cancelled meetings or group calendars, "meetings stored in Group or Shared mailboxes", encrypted meetings, past series and meetings already started — plus the accept-or-decline flow, come from "Change the organizer of a meeting in Outlook". The seven numbered offboarding steps, the 30 days of OneDrive and Outlook content after deleting the account and the 30 days of email, contacts and calendar after removing the licence, come from "Remove a former employee – Overview". And from step 4: its literal title, that on conversion "all of the existing email and calendar are retained in a shared mailbox that several people can access", that "you can convert a shared mailbox back to an individual user's private mailbox later if needed", and the whole Cancel Outlook meetings section, including that if the person had meetings booking equipment or rooms, "they won't be available to be booked until those meetings are canceled". Ours, and we bound it as such: the reading that converting the mailbox to shared puts the meetings beyond the reach of the new feature (Microsoft describes that interaction in none of the documents; it is our deduction and we recommend verifying it on a test mailbox), the warning that the window to operate closes before the 30-day retention window once the licence is gone (also a deduction, from the delegation requirement), the sequence table with its point-of-no-return column, the four cases where we would not use it, and the reading that the offboarding documentation has not caught up with the product it documents.