For two decades, serious business software met its users inside Office through one mechanism: the desktop add-in. COM and VSTO components installed on each machine, hooked deep into Outlook and Word, and did whatever the desktop APIs allowed. That model is now being retired. New Outlook for Windows does not run COM add-ins at all, and Microsoft’s replacement – web add-ins, also called modern apps – works differently in ways that change deployment, reach and what integration means. If your firm runs a DMS inside Outlook, this transition is arriving whether scheduled or not, so it is worth understanding what actually changes.
Two architectures, briefly
A desktop add-in is code installed on a machine, running inside the Office process with broad access to the application and the operating system. It is powerful and local: every machine needs the install, every update needs a rollout, and it exists only on Windows desktops where it was deployed.
A web add-in is an application served from the cloud and rendered inside Office through a defined API surface. Nothing installs on the machine; the add-in is assigned to users centrally and appears wherever that user opens Office – Windows, Mac, the web, and in Outlook’s case New and Classic clients alike. Updates ship server-side and arrive for everyone at once.
What the shift changes in practice
Deployment inverts. Desktop add-ins are packaged, tested against desktop images and rolled out machine by machine – familiar work for IT, and a real cost every upgrade cycle. Web add-ins are assigned from the Microsoft 365 admin centre to users or groups, and new starters have the tools the moment their account exists. The per-machine dimension of software management simply drops out.
Reach widens. The same add-in follows the user across Windows, Mac, browser and mobile surfaces the vendor supports. For firms with mixed fleets, or partners and mobile staff who were always second-class citizens under the desktop model, this is the headline gain.
Depth narrows – honestly. Web add-ins run sandboxed against defined APIs, and some things a COM add-in could do the sandbox does not permit. Some desktop integrations were deep for good reasons. The fair way to assess a modern replacement is against the jobs that matter – navigate, save, profile, search – rather than a line-by-line feature match with a twenty-year-old component.
Resilience changes shape. Desktop add-ins fail locally: one machine’s broken install is one person’s problem. Web add-ins depend on a service being up, and fail or recover for everyone at once. Different risk, different management.
What it means for document management
A DMS lives or dies inside Outlook and Office, which is why this transition hits document management hardest. A firm whose filing depends on a desktop-era DMS add-in has a hard dependency on Classic Outlook – workable today, since Classic remains supported until at least 2029, and a shrinking position every quarter after defaults change in 2027.
This is the transition MacroView DMS Next was built for: document management delivered as a modern app, providing tree-view navigation of SharePoint, Teams and OneDrive, saving with metadata capture, and search – in New Outlook, Classic Outlook and Teams, on Windows and Mac. Firms that need desktop-depth integration with Word, Excel and Adobe keep it through MacroView DMS on the desktop side; the two run against the same SharePoint structure, so moving between clients does not mean moving content. And MacroView Mail covers saving from any device, which under the old model was not a sentence anyone could write.
The practical move this quarter is an audit rather than a migration: list what runs inside Outlook today, check each item’s modern-app status, and pilot the replacements using both Outlook clients side by side. Firms that do this in 2026 can treat 2027 as a non-event.
