Classic Outlook does not die in 2027: what dies is your COM add-in

The question always arrives the same way: "is it true they are taking Outlook away from us in March?". And the honest answer is uncomfortable, because the date — the one part everybody wants — is exactly the part you do not control and the part that will cost you the least work. The work sits in a list almost nobody has written down: the things that work inside your Outlook today and that do not cross over to the new one.

The date exists. It is not where you are looking

Let us start by granting that the date is real and it is the vendor's. It sits in a Microsoft 365 Message Center post, MC949965, titled "Toggle to new Outlook", published on 6 December 2024 and last updated on 20 February 2026: the opt-out stage for Enterprise environments begins in March 2027, pushed back from the April 2026 announced earlier, with twelve months of lead time to prepare. In the same post: users moved to the new client can switch back to classic during the transition.

Now the part almost nobody mentions, and it is the part that changes your plan: opt-out does not mean it is taken away. The vendor page describing the migration — "Stages of migration to new Outlook for Windows" — defines three stages and only the third one shuts the door. Opt-in: the new client is off by default and the user decides with the toggle. Opt-out: on by default, but you can still go back. Cutover: you cannot. March 2027 is the second one. The third has no public date, and for existing installations the same page says "Existing installations of classic Outlook through perpetual and subscription licensing will continue to be supported until at least 2029".

And here is the detail that made us write this post. That public page carries no transition date between stages — it has a single dated milestone, general availability on 1 August 2024 — and to this day its first stage still carries the sentence "Currently, new Outlook for Windows is in the opt-in stage". Its last-revision stamp reads 23 February 2026: three days after the last update of the message that sets March 2027. Somebody touched the page and the date did not make it in.

The consequence is practical, not philosophical: the date that governs your project lives in your tenant, not in the public documentation. If your procedure for finding out about changes is "I look up the official page and read it", you are behind your own Message Center and you do not even know by how much. We saw the same mechanics with the update channel you thought you had: the problem was never the date, it was that nobody knew which channel each machine was on. Twelve months' notice is a gift only to whoever has the list ready on the day the notice lands. For everyone else it is twelve months of staring at a calendar.

The most dangerous word in the table is "partially"

The vendor publishes a feature comparison between classic and new Outlook. We checked it on 30 October; its last update is dated 23 September 2026. These are the rows that decide whether your migration is an icon change or a project:

"Not supported" is bad news you can plan around. "Partially available" is worse: it does not tell you whether your case falls in the part that works. And the only way to find out is for someone in your own shop to test it with your mailboxes and your delegations, not by reading the table. It already happened to us with an oddity that looked impossible and turned out to be documented: changing a meeting organizer in a shared mailbox. Until you sit down in front of it, you do not know which side of "partially" you are on.

Your ERP is not a program: it is an add-in

Here is the knot. In the companies we see, Outlook is not a mail client: it is where business things happen. The plug-in that files mail into the document manager. The one that creates the CRM opportunity from a message. The one that signs with the corporate template. The macro someone wrote in 2014 to move delivery notes into a folder, which has been running for twelve years without anyone remembering who wrote it.

All of that is COM add-ins, and the vendor page that catalogs them opens with a sentence worth reading twice: "These add-ins are now in maintenance mode" — meaning no new development will be done on them. It is not a threat; it is a notice that the platform holding up part of your operation stopped evolving a while ago.

And there are dated precedents in that same table, which is what makes it useful: the Azure Information Protection add-in for Office was retired on 11 April 2024 and its job now lives in native sensitivity labels; the Dynamics 365 COM add-in was deprecated in favour of its web version in 2020; the SharePoint Colleague Import add-in went out of support in October 2020 and we still find it installed. For VBA, the vendor itself points at three roads — Graph, Office.js and Power Automate — and none of them is "copy the macro".

The list takes twenty minutes

The good thing about this problem is that the inventory is cheap. Three roads, from most convenient to most complete:

Getting the list is the easy part. What costs you is the next column, and no tool gives it to you: what each add-in is for and who stops working if it disappears. That column gets filled in by talking to people, not by reading the registry.

Who decides the day: you, or a registry key

The automatic migration to new Outlook has a switch, and it is documented. It is governed by Group Policy, by the cloud policy service, or straight from the registry: DoNewOutlookAutoMigration under HKCU\Software\Microsoft\Office\16.0\Outlook\Options\General, where 1 starts the migration flow and 0 switches it off. Create it under the \Policies\ branch and the user cannot change it. It is worth knowing what that 1 starts: not a single switch, but three sessions — a teaching callout, then a bar saying the organisation recommends the new client, and on the third a dialog after which the new one opens on the next launch — and the user can go back to classic whenever they want.

The same key holds a second value, NewOutlookAutoMigrationRetryIntervals, which decides what happens to whoever switches back: 0 or unset, no retry; 1, the blocking dialog on every launch of classic — the most aggressive option; 2 to 99000, the number of days from the user switching back until migration restarts. And if what you want is to close the door, that is no longer a registry value but a mailbox policy: Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -HideClassicOutlookToggleOut $true hides the way back. Three distinct levers, and worth not mixing up. There is a fourth, on a different vendor page, and it is the one that causes the most confusion: NewOutlookMigrationUserSetting set to 0 under HKCU\Software\Policies\Microsoft\office\16.0\outlook\preferences turns off the user's automatic-migration setting, but its own documentation warns that it "doesn't apply to migrations that are initiated through the 'Admin-Controlled Migration to New Outlook' policy". Translated: if you set it believing it shields you and you also have the other one at 1, it does not shield you.

Said plainly: the first of them, DoNewOutlookAutoMigration, cuts both ways. It is what you use so the migration does not catch you out, and it is what you use to migrate a pilot group of twelve people next Tuesday. What it is not, is a plan. Setting it to 0 and forgetting is deferring with a registry key a decision you will have to make anyway — only later and with less room. We set it to 0 on day one and touch it the day the add-in list has an owner on every row; between those two dates there is work, not waiting.

Five checks, none of them is a date

When this does not affect you (which is a lot of people)

And now the part that does not suit us commercially. If your mailboxes are in the cloud, nobody has macros, there are no third-party plug-ins and people already use mail from their phone and the browser, this change is a non-event: the icon changes, the toolbar moves, and in two weeks nobody remembers. There is no project to sell there, and saying otherwise would be selling you a fear.

The problem is the other profile, and it is very common in long-established SMEs: fifteen years of Outlook with layers piled on top, an ERP that talks to mail, a document manager that files messages, and an Exchange still sitting on a machine in the cupboard. That is not a client change; that is the moment somebody finds out what their operation depended on. Better to find out with the inventory in front of you than on a Tuesday morning.

If you want us to build that list, it is part of what we do in managed Microsoft 365: estate inventory, add-ins with an owner, and a pilot with the odd cases inside it. And if the answer is that there is no project here, we will tell you; that is exactly what we sell in IT consulting. drop us a line and we will take a look.

Sources (checked on 30 October 2026): the March 2027 date for the opt-out stage in Enterprise environments, the postponement from April 2026, the twelve months of lead time and the fact that migrated users can switch back to classic during the transition come from Microsoft 365 Message Center post MC949965 "Toggle to new Outlook" — published 06-12-2024, last updated 20-02-2026 — which we read on its public mirror, because the Message Center is tenant-specific: check yours. The three stages, the 01-08-2024 general-availability milestone, the "until at least 2029" support statement and the sentence "Currently, new Outlook for Windows is in the opt-in stage" — with a 23-02-2026 revision stamp — are from Stages of migration to new Outlook for Windows. The per-feature statuses (COM add-ins, VBA, custom forms, voting buttons and business cards "not supported"; PST, on-premises Exchange, offline work, public folders and shared-mailbox delegate access "partially available", the latter stamped April 2026 while calendar delegate access is "available") are from the official feature comparison, updated 23-09-2026. The "maintenance mode" wording, the inventory path in config.office.com, the HKLM\SOFTWARE\Microsoft\Office\Outlook\Addins\* key, the File > Options > Add-ins route and the dates for AIP (11-04-2024), Dynamics 365 (2020) and SharePoint Colleague Import (October 2020) are from Identify COM add-ins in your organization. The DoNewOutlookAutoMigration and NewOutlookAutoMigrationRetryIntervals keys, their paths and values, the three steps of the migration flow, HideClassicOutlookToggleOut, the sentence "New Outlook isn't supported for on-premises environments" and the sovereign-cloud warning are from the admin-controlled migration policy; the NewOutlookMigrationUserSetting key, its path and its caveat ("This policy doesn't apply to migrations that are initiated through the 'Admin-Controlled Migration to New Outlook' policy") are in Control installing and using new Outlook. The VBA alternatives (Graph, Office.js, Power Automate) are from VBA, Macros, and Custom Flows Alternatives. The three days between the message update and the page revision, the thesis about "partially available", the order of the five checks and the opinion about setting the key to 0 are ours.