1. Overview

Microsoft is transitioning to a modernized Outlook for Windows experience, built upon a unified codebase that aligns with Outlook on the web. This new iteration is currently available as a preview and can be deployed via the Microsoft Store or the Office Content Delivery Network (CDN). For organizations currently utilizing “classic” Outlook, the new version is primarily introduced via a “Try the New Outlook” toggle, allowing users to opt-in and migrate their existing configurations, add-ins, and supported accounts.

Administrators have granular control over this transition, with the ability to manage the toggle’s visibility, perform wide-scale silent installations, or run the new client side-by-side with the legacy version to ensure feature parity and workflow continuity during the evaluation phase.

2. Key Technical Details

System & Infrastructure Prerequisites

• Mailbox Configuration: Access to the new Outlook requires Outlook on the Web (OWA) to be enabled for the target mailbox. This is controlled via the OWAEnabled parameter in Exchange settings.
• Operating System Support:
  • Windows 10 Version 2004 (Build 19041) or higher.
  • Windows 11 Version 23H2 or higher (where it is preinstalled).
  • Windows Server 2022 (Build 20348.2402) or higher.
  • Note: Windows Server 2016 and 2019 are explicitly not supported.
• Dependencies: The latest version of the WebView2 Runtime is required for rendering the application interface.
• Classic Outlook Version: To utilize the built-in toggle mechanism, users must be on Version 2303 (Build 16227.20318) or later.

Deployment Methodologies

Administrators can choose between several installation paths depending on the environment’s restrictions:

• Standard Admin Deployment (Per-Machine): To provision the app for all users on a single workstation, use the Setup.exe with elevated privileges:

  .Setup.exe --provision true --quiet --start-

• Windows Package Manager (winget): Ideal for non-administrative, per-user installations:

  winget install -i -e --id=9NRX63209R7B --source=msstore --accept-package-agreements

• Microsoft Intune: Admins can push the Microsoft Store version directly to enrolled devices without requiring local admin rights for the end-user.
• Offline/Bandwidth-Constrained Environments: MSIX packages (x64, x86, Arm64) are available for provisioning via Add-AppxProvisionedPackage.

Side-by-Side Execution & Microsoft 365 Integration

• Version 2502 and Beyond: Starting with this version, the new Outlook will be included by default in all new Microsoft 365 desktop client deployments.
• Customization: Admins can use the Office Customization Tool or modify the ExcludeApp element in the ODT XML to prevent the installation of either the classic or the new client.
• Interoperability: Running both versions concurrently is recommended for users relying on legacy features like .pst files, COM add-ins, or advanced Office integration (e.g., Word Mail Merge and People Pickers) while they transition.

3. Impact

For IT Administrators

The shift allows for a more streamlined update cycle, as the new client shares its architecture with the web version. However, it requires proactive management of the Try the New Outlook toggle via Group Policy or Cloud Policy to prevent shadow IT or premature adoption. Admins must also account for the fact that Windows Single Sign-On (SSO) handles most authentications, but some legacy account types may require users to re-authenticate during the initial migration.

For End-Users

Users gain a modern interface and closer feature parity with the web and mobile versions of Outlook. The migration process is designed to be non-destructive; settings and supported accounts are imported from the classic version. Crucially, the ability to toggle back to the classic experience ensures that if a specific workflow is interrupted, productivity is maintained while the new client evolves.