BestPaid guides · Microsoft 365 · Outlook

The new Outlook becomes the default for enterprise users from March 2027. Your VSTO and COM add-ins won't come along

The new Outlook for Windows runs only web add-ins built on Office.js, and Microsoft has been switching classic Outlook users on Microsoft 365 Business plans (Current Channel) to it automatically since January 2025. COM and VSTO add-ins, the C# kind many companies built years ago for CRM filing, classification or archiving, don't load there at all. They can't be converted; they have to be rebuilt as web add-ins in JavaScript or TypeScript, though some of the C# code can be reused by moving it to a back-end web API that the add-in calls.

Sources: Microsoft's guide to new Outlook availability, Microsoft Support on the automatic switch for Business plans, and reports on Message Center post MC949965 that moved the Enterprise opt-out phase to March 2027 (The Register, Petri). For the add-in side: Microsoft's VSTO add-in developer's guide, platform support for the unified manifest, authentication options in Outlook add-ins and the Exchange Team's EWS retirement timeline. Checked on November 21, 2026. This page is our own summary; follow Microsoft's documentation for every detail.

The timeline

What maps to what

In a VSTO or COM add-inIn a web add-in
Ribbon buttons and custom task panes (WinForms or WPF)Add-in commands and an HTML task pane or dialog
Application.ItemSend checks before sendingEvent-based activation with OnMessageSend (Smart Alerts)
Code that runs when a message is composedEvent-based activation, for example OnNewMessageCompose
Reading and changing the open itemThe Office.js mailbox API (Office.context.mailbox.item)
Bulk work on folders and other mailboxesMicrosoft Graph, called from the add-in or from your own back end
Calls to EWS from the add-in, for example through the EWS Managed APIMicrosoft Graph with nested app authentication (MSAL.js). Starting October 1, 2026, Microsoft has been turning EWS off, tenant by tenant, in Exchange Online tenants whose admins didn't keep it on; admins can turn it back on until April 2027, and on April 1, 2027 EWS is disabled for good. (The legacy Exchange tokens that older web add-ins used are already turned off.)
MSI installer on each PCCentral deployment from the Microsoft 365 admin center (Integrated apps)

What doesn't carry over

The upside: a web add-in that uses the add-in only (XML) manifest also runs in Outlook on the web, on Mac and in classic Outlook, so you can roll it out to everyone before the switch and retire the VSTO version once nobody needs it. An add-in on the newer unified manifest for Microsoft 365 can't yet be installed in Outlook on Mac, on mobile or in perpetual versions of classic Outlook; to reach those users, Microsoft says you need a second version of the add-in with the add-in only manifest.

A sensible order

  1. List every COM and VSTO add-in in use, including vendor ones; ask vendors for their web add-in.
  2. For your own add-ins, write down each feature and decide where it lives: in the add-in, in Graph, or in a back-end service.
  3. Build the web add-in, deploy it to a pilot group next to the old one, then to everyone.
  4. Only then let users move to the new Outlook.
A VSTO add-in nobody has touched since it was written? We rebuild COM and VSTO Outlook add-ins as web add-ins, with Microsoft Graph and a back-end service where needed, at a fixed price: an add-in from $1,490, a complex one from $2,900. One add-in gets a free estimate within 2 business days. We never ask for passwords, secrets or admin access.
See the Microsoft 365 migration offer