The difference between Classic and New Outlook is not cosmetic. It is architectural. New Outlook replaces the native COM-based infrastructure with a WebView2 browser shell that communicates with Microsoft 365 through the Graph API. Every limitation that power users encounter in the new version traces back to this single design decision.
What New Outlook cannot do
New Outlook imposes three hard restrictions that Classic Outlook does not have.
No local file system access. WebView2 is a browser sandbox. Add-ins running inside it cannot read files from your local drives or network shares. Attaching a file requires uploading it through a browser dialog, which means the file passes through Microsoft's cloud before reaching the recipient. For confidential documents, this creates a data custody trail that many compliance policies prohibit.
No VSTO add-in support. New Outlook only supports Office.js web add-ins. These run in the browser sandbox and communicate with Outlook through the Graph API. They cannot match the performance of a native VSTO add-in that runs in-process with Outlook and communicates through COM directly.
Throttled by the Graph API. Every operation a web add-in performs goes through the Microsoft Graph API, which enforces strict rate limits. Microsoft documents these limits in their throttling documentation. For bulk email operations, the Graph API caps requests at 4 to 10 per second. A VSTO add-in bypasses this entirely by operating locally.
Stay with Classic Outlook
FlowDrafts is built for Classic Outlook power users who need speed and security.
What Classic Outlook preserves
Classic Outlook is a native Win32 application. VSTO add-ins run inside its process and communicate through COM, the same interface Outlook uses internally. This architectural choice preserves capabilities that web add-ins cannot replicate.
Direct file system access. A VSTO add-in can attach files from any local or network path without uploading them. The file stays on your drive. The add-in tells Outlook to attach it from there. No data passes through a third-party server.
Full MAPI integration. Classic Outlook supports the full MAPI protocol, giving add-ins access to low-level email properties, custom headers, and advanced encoding options. Web add-ins are restricted to what the Graph API exposes.
Environment stability. Classic Outlook does not auto-update through the Microsoft 365 channel. IT teams control when new versions are deployed. For regulated industries where add-in compatibility must be validated before updates, this is a requirement, not a preference.
What this means for your workflow
If you use Outlook for individual email and calendar management, New Outlook will serve you well. The interface is cleaner and the integration with Microsoft 365 is tighter.
If you use Outlook for high-volume professional outreach, the choice matters. Every email you send through a web add-in travels through the Graph API, consuming your throttling budget. Every file you attach goes through a cloud upload pipeline. Every operation depends on network latency and API availability.
Classic Outlook avoids all of these because the architecture was designed for a desktop application, not a web wrapper. FlowDrafts was built on this architecture intentionally. The add-in runs at the speed of your hardware, attaches files from your local drives, and drafts emails through your local Outlook process. No cloud API calls, no throttling, no data leaving your machine.