Edit

Share via

Deploy the New Outlook for Windows on Virtualized Desktop Infrastructure

This article outlines the requirements, limitations, and deployment guidance for using the new Outlook for Windows in virtualized desktop infrastructure environments.

Requirements

Requirement Version
Windows - Windows 10.0.19041.0 (2004) or later
- Windows Server 2022 (20348.2402) or later
WebView2 Update to the latest version. For more information, see Enterprise management of WebView2 Runtimes.
.NET Framework 4.7.2 or later

Note

Windows Server 2019 and Windows Server 2016 are not supported.

Virtualization Provider Requirements

The following sections outline the requirements for virtualization providers that support the new Outlook for Windows.

Azure Virtual Desktop and Windows 365

The following minimum versions are required for the new Outlook for Windows:

  • Remote Desktop Client for Windows: 1.2.2606
  • Remote Desktop Client for Mac: 10.7.7

Citrix Virtual Apps and Desktops and Citrix DaaS Requirements

The following sections describe the requirements for Citrix Workspace App and Citrix Virtual Delivery Agent (VDA) to support the new Outlook for Windows.

Citrix Workspace App

  • Windows 2203 LTSR (and any CU)
  • Windows 2302 CR

Citrix Virtual Delivery Agent (VDA)

  • 2203 LTSR (and any CU)
  • 2212 CR
  • 1912 CU6 (latest CU recommended; note that App Sharing is not supported on 1912)

VMware Horizon and Workspace ONE Requirements

The following minimum version is required for the new Outlook for Windows:

  • Horizon 8 2111 ESB (8.4)

Deploy the New Outlook for Windows

Note

The new Outlook for Windows is installed as part of Windows, starting with Windows 11, version 24H2.

To deploy the new Outlook for Windows:

  1. Download the .exe installer.
  2. Use a distribution method such as Intune, Microsoft Endpoint Configuration Manager, Group Policy, or a non-Microsoft tool to distribute the installer.
  3. Run the installer on each computer.

For detailed instructions, see Deploy New Outlook.

Note

If AllowAllTrustedApps is disabled, the new Outlook app installation fails. This issue was fixed in the October cumulative update KB5031455 for Windows 11 and Windows 10. If this update is unavailable, the November security update includes the fix.

For more information, see Installation issues due to policy restrictions.

Disk Footprint - Key Folders and Location

Important

For non-persistent VDI environments, FSLogix does not support roaming user data in the new Outlook for Windows.

Install Location

The MSIX installer installs the new Outlook app in the WindowsApps folder. This location provides enhanced protection against attacks that attempt to alter the Outlook app installation.

The folder name where the new Outlook app is installed changes with each version update. It starts with Microsoft.OutlookForWindows_, ends with _8wekyb3d8bbwe, and includes the version number and machine architecture. For example: Microsoft.OutlookForWindows_1.2024.717.400_x64_8wekyb3d8bbwe.

To find the current version's install location, run the following PowerShell command:

(get-appxpackage Microsoft.OutlookForWindows).InstallLocation

Note

The MSIX installer and all files in the directory are signed with a Microsoft certificate.

Profile and Cache Locations for the New Outlook for Windows

All user settings and configurations are stored in:

  • C:\Users\<username>\AppData\Local\Packages\Microsoft.OutlookForWindows_8wekyb3d8bbwe\
  • C:\Users\<username>\AppData\Local\Microsoft\olk\

Folder Exclusions for Roaming

Important

For non-persistent VDI environments, FSLogix does not support roaming user data in the new Outlook for Windows.

Folder Folder Path Purpose Exclusion Impact
Logs and Telemetry Cache %LocalAppData%/Microsoft/olk/logs
%LocalAppData%/Microsoft/olk/cache		 Diagnostics and performance logs. No effect.
WebStorage %LocalAppData%/Microsoft/olk/EbWebView/default/WebStorage Cache for web app usage in iframes. Slower app reload.

Considerations for Exclusion

Folder Folder Path Purpose Exclusion Impact
Service Worker %LocalAppData%/Microsoft/olk/EBWebView/default/Service Worker/CacheStorage
%LocalAppData%/Microsoft/olk/EBWebView/default/Code Cache		 Stores cached web/JS scripts. Slower app launches due to redownload of scripts.
IndexedDB and Local Storage %LocalAppData%/Microsoft/olk/EBWebView/default/IndexedDB
%LocalAppData%\Microsoft\olk\EBWebView\Default\Local Storage
%LocalAppData%/Microsoft/olk/Attachments		 Stores user and app data. Increased app launch time and repeated sign-ins.
Cache %LocalAppData%/Microsoft/olk/EBWebView/default/Cache Caches network call contents. Resources need to be redownloaded.

Other than the folders in this section, avoid excluding extra directories.