Microsoft has pushed back the date when it will begin making the new Outlook for Windows the default experience for enterprise users. The opt-out phase — originally slated for April 2026 — will now start in March 2027, giving organizations nearly a full year of additional preparation time. The core message, however, remains unchanged: Microsoft still intends to move every Classic Outlook user to the web-based client, and the clock is ticking.

What actually moved — and what hasn't

The delay affects a single but significant milestone on Microsoft’s migration roadmap. In March 2027, the company will start transitioning enterprise environments into what it calls the “opt-out phase.” During this period, new Outlook becomes the expected default, but users and administrators retain the ability to switch back to Classic Outlook. Microsoft has not yet set a date for the “cutover phase,” when switching back will no longer be an option. Classic Outlook itself is not retiring in 2027; support for both perpetual and subscription installations is currently guaranteed until at least 2029.

The delay, first reported by Windows Latest, was confirmed in an official update from Microsoft. The company framed the move as a response to requests for more preparation time, noting that organizations would now have 12 months of lead time once the opt-out clock starts. Government and Department of Defense timelines remain separate and will be communicated later.

This is not the first time Microsoft has shifted the schedule. The original April 2026 target was itself a postponement from earlier plans, reflecting the complexity of moving millions of knowledge workers away from a desktop client that has been the backbone of corporate email for decades. The opt-out phase is not a silent push: Microsoft will actively prompt users to try the new Outlook, and some may find themselves redirected automatically before they realize they can revert. The company used similar tactics when it replaced the Mail and Calendar apps, and users reported being cycled back into the new client even after they had opted out.

What the 2027 deadline actually means for you

For enterprise administrators

The extra year is not a holiday. It’s a window to run a thorough, controlled migration evaluation before the pressure of a default-setting flip. The most urgent task is to identify every dependency that still binds your organization to Classic Outlook. The hardest gap to close remains COM add-ins — the custom integrations, compliance tools, CRM connectors, and line-of-business helpers that have been built up over decades. Microsoft’s own migration guidance is blunt: “COM add-ins are not supported in new Outlook. Transition to web add-ins where possible.”

You will also need to test .pst archives under realistic conditions. New Outlook can now read, move, copy, delete, and flag messages inside .pst files, and support is expanding, but Microsoft still caveats that future releases will “expand .pst capabilities.” That means feature presence does not equal feature parity. The same caution applies to offline mode: the client now caches email, calendars, and contacts for 30 days by default, but attachments, shared folders, and delegate scenarios still have documented limitations.

Microsoft provides several administrative controls right now. You can hide the “Try the new Outlook” toggle through cloud policy or registry keys, block the app’s installation on managed devices, prevent work or school mailbox access from the new client via Exchange policy, and configure whether individual users see the automatic migration prompt. Using these controls intentionally — rather than ignoring them until the deadline — lets you run a pilot where test users work side-by-side with both clients. Microsoft itself recommends this approach, telling organizations to “keep both clients accessible so users can return to the established client when a workflow requires it.”

For end users and power users

If your organisation hasn’t yet started a migration programme, the 2027 change may feel distant. But the features you rely on daily are the ones most likely to be disrupted — shared mailbox workflows, delegate access, customised views, or finely tuned rules. The frustration quoted by Windows Latest from one user — “painful and drives me crazy” — is typical not of Luddites, but of people whose proven, efficient routines break in the new client. Pinning, snoozing, and a cleaner inbox layout are welcome additions, but they don’t compensate for a missing COM add-in that routes legal documents to a records system.

As the deadline nears, you’re likely to see more prompts to switch. If you’re pushed into new Outlook and find a missing tool, report it immediately to your IT team — the more detailed the feedback, the better they can plan. And if you maintain local .pst archives, don’t assume they will behave identically; test moving a small batch of messages before committing to an archive migration.

For developers and add-in vendors

The 2027 timeline is also a signal to finish any web add-in replacements if you haven’t already. Organizations that depend on your COM-based tooling will be knocking on your door over the next year. Microsoft’s guidance recommends running an add-in inventory now, and that inventory will quickly turn into a list of must-have replacements. The web add-in model is the strategic path forward, and customers will expect feature coverage that doesn’t break critical business processes.

How we got here

New Outlook for Windows first appeared in 2023 as a preview built on the same web architecture that powers Outlook on the web. It was a deliberate break from the Win32 Classic client, designed to accelerate feature delivery, converge the codebase across platforms, and more deeply integrate Microsoft 365 cloud services. In 2024, it replaced the lightweight Mail and Calendar apps, with support for those ending on December 31, 2024. That transition previewed the friction to come: Mail and Calendar were simple, but even that switch generated complaints about lost features and changed workflows.

Classic Outlook, meanwhile, has accumulated decades of capability. Many of its features — COM add-ins, offline caching, intricate delegation rules, custom forms, and macros — were built for a world where the PC was the primary computing surface and internet connectivity wasn’t guaranteed. Rewriting all of that for a web-first client is a monumental engineering task, and Microsoft has been racing to close the gap. Over the past year, it added offline support, .pst management, shared mailbox improvements, and inbox tools like Sweep, scheduled send, and multiple category tagging. The pace is real, but as critics note, many of these are catch-up features, not innovations. The February 2025 Tech Community post that listed 15 new productivity additions was effectively a parity report.

User sentiment, while improving, remains sharply divided. A vocal segment of Outlook Classic users describes the new client as unfinished and restrictive. Their objections are not superficial: they centre on missing COM add-ins, unpredictable offline behaviour, and workflows that require more clicks or workarounds. Microsoft insists adoption is “strong and accelerating,” and that may be driven partly by organisations eager to use Copilot, which is more deeply embedded in the new client. But an increased adoption number does not tell you whether the most complex, mission-critical workflows have actually migrated.

What to do now: a practical checklist for IT teams

Use the added time to shift from “wait and see” to structured testing. Here’s a concrete list:

  • Inventory your Classic Outlook dependencies. Start with a COM add-in audit. Next, map .pst files: where they’re stored, who uses them, and what actions they perform. Document shared mailboxes, delegation setups, public folders, custom forms, and any macros.
  • Segment your user base by workflow, not job title. The sales team might be fine with the new client; the executive assistants and finance specialists probably won’t. Identify the small groups that carry the highest migration risk.
  • Set up a side-by-side pilot. Select users who represent high-risk workflows. Give them access to both clients and ask them to log every occasion they need to switch back to Classic. This data is your real readiness score.
  • Test offline and archive behaviour under field conditions. Don’t limit testing to the office Wi-Fi. Simulate patchy connections, large attachments, attachment-less email chains, and recovery after disconnection.
  • Configure migration policies now. Decide whether you want automatic migration prompts, and implement the corresponding registry or cloud policy settings. Microsoft’s documentation lists the relevant Admin control IDs.
  • Build training that focuses on changed workflows, not just the new interface. A walk-through of the ribbon won’t help if a COM add-in used to process invoices is gone. Training should include clear fallback instructions: when and how to return to Classic Outlook.
  • Define exit criteria for declaring migration successful. “Email arrived” is not a success metric. A successful migration means critical business processes continue to function, security controls are intact, and user acceptance meets a documented threshold.

What to watch next

Microsoft has bought enterprises breathing room, but not an off‑ramp. The opt‑out phase will eventually give way to a full cutover, and the company’s pace of feature delivery shows it intends to keep closing the gap. The risk for organizations is assuming that another year will solve everything by itself. The most effective way to spend the time is to demand proof of readiness — not from roadmaps, but from the experience of your own users. When the March 2027 prompts start appearing, the teams that have already tested, trained, and built a fallback plan will be the ones who don’t panic.