Classic Outlook to New Outlook: VDI Support – Deployment notes for virtual desktops

You are migrating from Classic Outlook to the new Outlook for Windows in a VDI environment. The new Outlook for Windows is a modern client that replaces the classic Win32 application, and it requires specific deployment considerations in virtual desktop infrastructure. This article covers the supported VDI platforms, system requirements, and step-by-step configuration notes for IT administrators. You will learn how to install, configure, and verify the new Outlook in a VDI session.

New Outlook for Windows in VDI: Deployment Overview

The new Outlook for Windows is a progressive web app built on the Microsoft 365 platform. It does not support classic MAPI profiles, offline OST files, or COM add-ins. In VDI, the new Outlook runs as a per-user application installed in the user profile. It requires Windows 10 version 20H2 or later or Windows 11. Supported VDI platforms include Azure Virtual Desktop, Windows 365, VMware Horizon, and Citrix Virtual Apps and Desktops. The new Outlook does not support non-persistent VDI without profile management solutions such as FSLogix. You must plan for network connectivity to Microsoft 365 endpoints and manage user settings through Group Policy or Intune.

Prerequisites for VDI Deployment

Before deploying the new Outlook, verify the following requirements:

• Windows 10 version 20H2 or later, or Windows 11.
• Microsoft 365 or Office 365 subscription with Exchange Online mailbox.
• Internet access to Microsoft 365 endpoints. Allowlist the URLs listed in Microsoft 365 Common and Office Online.
• Profile management solution: FSLogix Profile Container or Office Container, Microsoft UE-V, or a custom script that copies AppData folders.
• No classic Outlook add-ins must be present. The new Outlook does not load COM add-ins.

Steps to Deploy New Outlook in a VDI Environment

Follow these steps to install and configure the new Outlook for all users on a VDI golden image or per-session.

Method 1: Install via Microsoft Store (Persistent or Non-Persistent with Store Apps Roaming)

1. Prepare the VDI image
   Deploy Windows 10 20H2 or later or Windows 11. Install all Windows updates. Do not install Classic Outlook side-by-side if you intend to fully replace it.
2. Install the new Outlook from the Microsoft Store
   Sign in to the VDI master image as a user with Microsoft Store access. Open the Microsoft Store app, search for “Outlook for Windows”, and click Install. The app installs in the user profile under %LocalAppData%\Microsoft\Outlook for Windows.
3. Set the registry key to enable the new Outlook
   Run the following command in an elevated PowerShell session: New-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Outlook\Options\General" -Name "NewOutlookEnabled" -Value 1 -PropertyType DWord -Force. This registry key forces the new Outlook to be the default mail client.
4. Configure profile management for roaming
   If using FSLogix, configure the Profile Container to include AppData\Local\Microsoft\Outlook for Windows and AppData\Roaming\Microsoft\Outlook for Windows. This ensures cached credentials and settings persist across sessions.
5. Test the deployment
   Log off the master image. Deploy the image to a test VDI pool. Sign in as a test user. Open Outlook from the Start menu. Verify that the user is prompted to sign in with their Microsoft 365 account and that mail, calendar, and contacts load.

Method 2: Offline Installer for Air-Gapped Environments

1. Download the offline provisioning package
   On a machine with internet access, go to the Microsoft Store for Business portal. Search for “Outlook for Windows” and download the offline app package as an .appxbundle file.
2. Transfer the package to the VDI image
   Copy the .appxbundle file to the VDI master image. Place it in a folder that all users can read, such as C:\Installers.
3. Install the package for all users
   Open PowerShell as Administrator. Run: Add-AppxProvisionedPackage -Online -PackagePath "C:\Installers\OutlookForWindows.appxbundle" -SkipLicense. This provisions the app for all new users.
4. Enable the new Outlook via Group Policy
   Open the Group Policy Management Console. Create or edit a GPO linked to the VDI OU. Navigate to Computer Configuration > Administrative Templates > Microsoft Office 2016 > Outlook Options > General. Set “Enable New Outlook” to Enabled.
5. Verify per-user installation
   Sign in as a test user. Run Get-AppxPackage -Name OutlookForWindows in PowerShell. Confirm the package is present. Launch Outlook from the Start menu.

If the New Outlook Fails to Start or Sync in VDI

Even with correct deployment, you may encounter issues specific to virtual desktops. Below are the most common failure patterns and their fixes.

Outlook prompts for sign-in every session

This occurs when the token cache is not persisted. The new Outlook stores authentication tokens in %LocalAppData%\Microsoft\Outlook for Windows. In non-persistent VDI without FSLogix, this folder is deleted at logoff. Configure FSLogix Office Container or redirect %LocalAppData%\Microsoft\Outlook for Windows to a network share using folder redirection Group Policy.

Outlook displays a blank screen or fails to load

This is often caused by missing Windows WebView2 runtime. The new Outlook depends on WebView2. Install the Evergreen WebView2 runtime from Microsoft. In a golden image, run the WebView2 standalone installer before sysprep. Also verify that the Microsoft.OutlookForWindows app package is not corrupted by running Get-AppxPackage -Name OutlookForWindows | Repair-AppxPackage in PowerShell.

Group Policy settings do not apply

The new Outlook uses ADMX files from the Microsoft 365 Apps admin templates. Download and install the latest Microsoft 365 Apps ADMX files. Place them in C:\Windows\PolicyDefinitions. Verify that the GPO administrative template path is correct. The new Outlook settings are located under Computer Configuration > Administrative Templates > Microsoft Office 2016 > Outlook Options > New Outlook.

Classic Outlook vs New Outlook in VDI: Key Differences

Item	Classic Outlook (Win32)	New Outlook for Windows
Installation method	MSI or Click-to-Run via Office deployment	Microsoft Store or offline provisioning package
Profile management	OST file in AppData; requires FSLogix for roaming	Local cache in AppData; requires FSLogix for token and settings
Add-in support	COM, VSTO, and web add-ins	Web add-ins only; no COM or VSTO
Offline mode	Full offline with cached OST	Limited offline; requires constant internet for sync
Group Policy support	Extensive via Office ADMX	Limited; uses New Outlook ADMX templates
VDI readiness	Mature with FSLogix and Citrix optimizations	Newer; requires WebView2 and profile management

You can now deploy the new Outlook for Windows in your VDI environment using either the Microsoft Store or offline installer. Configure FSLogix to persist user data and authentication tokens. Next, test the deployment with a pilot group before rolling out to all users. For advanced management, consider using Intune to deploy the new Outlook and enforce settings through policy.