Outlook Add-ins Not Loading (COM vs. Web Add-in Conflict)

If your add-ins disappeared after switching to the New Outlook for Windows interface, your system is not broken. Rather, you are encountering a fundamental architectural shift. The New Outlook client completely removes support for legacy COM (Component Object Model) and VSTO (Visual Studio Tools for Office) plugins, running exclusively modern, web-based Office add-ins.

Fast Fix

Check your add-in type. If it relies on a local .dll or installer file (COM/VSTO), it cannot run in New Outlook. Look for an equivalent modern Web Add-in via the Apps icon on the ribbon, or deploy it through the Microsoft 365 Admin Center.

---

Diagnostic Snapshot

Property	Details
Core Issue	Modern WebView2 platform lacks Win32 COM/VSTO execution architecture
Affected Add-ins	Local CRM synchronizers, local PDF printers, legacy digital signature tools, local antivirus scanners
Supported Add-ins	Web Add-ins built with JavaScript/HTML/CSS (Office.js API)
First Action	Determine whether the missing add-in is COM-based or modern Web-based

---

The Architecture Break: COM vs. Modern Web Add-ins

For more than two decades, classic Outlook ran as a native 32-bit or 64-bit Win32 application. Third-party developers integrated tools using COM and VSTO architectures. These legacy add-ins run inside the local OUTLOOK.EXE memory space or as background Windows services. While flexible, COM add-ins frequently caused application crashes, memory leaks, slow boot times, and security vulnerabilities.

New Outlook for Windows is built on top of web technologies using the Microsoft Edge WebView2 runtime. It does not execute local C++, C#, or VB.NET code libraries. Instead, it only interfaces with the Office JavaScript API (Office.js).

Modern Web Add-ins:

• Run inside a sandboxed browser process.
• Are cross-platform (functioning identically in Outlook on the web, Mac, iOS, Android, and Windows).
• Cannot access the local Windows Registry, local file system, or execute local background processes without external cloud APIs.

Classic Outlook (Win32)
 ├── Native OUTLOOK.EXE Memory Space
 │    ├── COM Add-in (.dll) ---------> Runs directly in Outlook process
 │    └── VSTO Add-in (.vsto) -------> Requires local .NET Framework
 └── Office.js Web Add-in ------------> Supported via Internet Explorer/Edge

New Outlook (WebView2)
 ├── Edge WebView2 Sandboxed Process
 │    └── Office.js Web Add-in -------> FULLY SUPPORTED (Cloud/Manifest)
 └── Legacy COM / VSTO ---------------> NOT SUPPORTED (Blocked by design)

---

Step-by-Step Resolution Path

Step 1: Identify Whether Your Add-in is COM or Web-Based

To know if your missing plugin can run in New Outlook, inspect its configuration in classic Outlook:

1. Launch Classic Outlook.
2. Navigate to File > Options > Add-ins.
3. Look at the Manage drop-down menu at the bottom of the window. Select COM Add-ins and click Go….
4. Review the active list. Common COM-only add-ins include:
   • Adobe Acrobat PDFMaker Office COM Addin
   • Zoom Outlook Plugin (the local .exe installer version)
   • Salesforce for Outlook (legacy desktop sync)
   • Cisco Webex Productivity Tools
   • Local antivirus email scanning hooks

If your required tool appears on this list with a .dll file path, it will never load in New Outlook. You must locate the modern cloud equivalent.

Step 2: Search for and Install the Modern Web Add-in Equivalent

Most major enterprise software providers have rewritten their integrations as Office.js web add-ins:

1. In New Outlook, click the Apps icon on the left app bar (or open an email and click Apps / Get Add-ins on the ribbon).
2. Click Add apps.
3. Search for the software provider (e.g., “Zoom for Outlook”, “Salesforce”, “DocuSign”, “Adobe Acrobat for Microsoft 365”).
4. Click Add to attach the web manifest to your account.

Once added, the add-in will appear inside the message ribbon or under the more actions (…) menu when reading or composing an email.

Step 3: Resolving Blocked or Grayed-Out Web Add-ins

If you find the modern version of your add-in but cannot install or launch it:

1. Verify Connected Experiences: Web add-ins require Microsoft 365 Connected Experiences. Go to Settings (gear icon) > General > Privacy and data > Privacy settings. Ensure that Turn on experiences that analyze your content and Turn on experiences that download online content are enabled.
2. Clear WebView2 Add-in Cache: If an installed web add-in displays a white screen or spinning loader, close Outlook and clear the local runtime cache:
   • Press Win + R, paste the following path, and press Enter: %localappdata%\Microsoft\Office\16.0\Wef\
   • Delete the contents of the Wef folder and restart New Outlook.

---

Enterprise Admin Deployment

In managed enterprise environments, individual users are frequently blocked from installing add-ins from the Office Store. IT administrators must deploy approved modern web add-ins tenant-wide:

1. Navigate to the Microsoft 365 Admin Center (admin.microsoft.com).
2. Go to Settings > Integrated apps.
3. Click Get apps to browse AppSource, or select Upload custom apps if using an internally developed XML/JSON manifest.
4. Assign the app to specific users or security groups.
5. Deployment will automatically replicate to the user’s New Outlook profile within 6 to 24 hours.

---

Hard Stops: When You Must Revert to Classic Outlook

If your organization relies on proprietary, in-house business software, specialized peripheral scanners, or legal metadata scrubbing tools that only compile as Win32 COM DLLs, you cannot use New Outlook at this time.

Until your vendor ships a modern Office.js cloud manifest, you will need to switch back to classic Outlook:

• How to Revert to Classic Outlook after “Forced Update” (The Registry Fix)

If New Outlook crashes when attempting to launch web components, ensure the underlying Windows runtime is intact:

• New Outlook Crashing on Startup (The WebView2 Runtime Fix)