New Outlook VDI Support Settings: Location and Practical Limits

The new Outlook for Windows has introduced specific settings for Virtual Desktop Infrastructure or VDI environments. These settings control how the app behaves when multiple users share a single server. Without proper configuration, users may face performance issues or unexpected sign-out prompts. This article explains where to find the new Outlook VDI support settings and the practical limits you must consider before deploying them.

What Are the New Outlook VDI Support Settings

The new Outlook for Windows is a progressive web app that runs on a shared backend. In a VDI environment, multiple users connect to the same host machine and run their own instance of Outlook. Without specific VDI settings, each instance tries to sync data independently, leading to high memory use, network congestion, and authentication conflicts.

Microsoft introduced a dedicated VDI settings group in the Group Policy templates for Outlook. These settings are available starting with Outlook version 1.2023.1000 or later. The settings control session limits, caching behavior, and sign-out timeouts. They apply only to the new Outlook, not to classic Outlook.

Prerequisites for Using VDI Settings

Before you configure VDI settings, verify these requirements:

• Windows 11 or Windows 10 Enterprise with the latest updates installed.
• New Outlook version 1.2023.1000 or newer. Check in Outlook by selecting File > Office Account > About Outlook.
• Administrative access to the VDI master image to apply Group Policy or registry changes.
• Microsoft 365 Business Basic, Business Standard, Business Premium, or any Enterprise plan that includes Outlook.

Where to Find the New Outlook VDI Settings

The VDI settings for new Outlook are located in two places: Group Policy for centralized management and the Windows Registry for per-user or per-machine tweaks. Both locations use the same underlying policies.

Group Policy Location

1. Open the Group Policy Management Console
   Run gpedit.msc on the VDI master image or use a domain-based Group Policy object.
2. Navigate to the Outlook VDI folder
   Go to Computer Configuration > Administrative Templates > Microsoft Outlook 2016 > Outlook Options > VDI. The folder name says 2016 but the policies apply to new Outlook as well.
3. Enable the desired policy
   Double-click a policy such as Limit the number of concurrent Outlook sessions. Set it to Enabled and enter the maximum sessions value. Click OK.

Registry Location

1. Open Registry Editor
   Press Windows + R, type regedit, and press Enter.
2. Navigate to the VDI key
   Go to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\VDI. If the VDI key does not exist, right-click the Options key, select New > Key, and name it VDI.
3. Add or modify a DWORD value
   Right-click in the right pane, select New > DWORD (32-bit) Value, and name it MaxConcurrentSessions. Set the value data to a number between 1 and 10. Click OK.

Practical Limits of New Outlook VDI Settings

The VDI settings provide control but have specific limits you must understand before deployment.

Number of Concurrent Sessions

The MaxConcurrentSessions setting limits how many Outlook instances a single user can run at the same time. The allowed range is 1 to 10. Setting the value to 0 disables the limit, which is the default. If you set a limit and a user exceeds it, the new session is blocked and an error message appears. On a shared VDI host with 50 users, setting this to 2 per user prevents memory overload but may frustrate power users who need multiple profiles open.

Session Timeout

The policy Set session idle timeout for VDI controls how long an idle session stays active. The timeout range is 1 to 1440 minutes or 24 hours. After the timeout, Outlook signs the user out and discards cached data. The default is no timeout. Setting a short timeout, such as 15 minutes, frees memory on the host but forces users to reauthenticate frequently.

Cache Behavior

New Outlook in VDI uses a local cache stored in the user profile. The VDI policy Disable local caching in VDI turns off all local caching when enabled. Without caching, Outlook fetches data from the server on every action. This reduces disk I/O on the host but increases network traffic and slows down email browsing. Microsoft recommends enabling caching unless the VDI environment uses persistent disks with limited space.

Policy Conflicts with Classic Outlook

The VDI policies under the Microsoft Outlook 2016 node also affect classic Outlook if it is installed on the same image. Classic Outlook uses a different caching mechanism and does not respect the MaxConcurrentSessions value. If both versions run on the same host, apply the policies only to new Outlook by using a targeting filter in Group Policy or by modifying the registry under the new Outlook-specific path HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\VDI.

Common Configuration Mistakes and Their Consequences

Setting MaxConcurrentSessions Too Low

A value of 1 prevents a user from opening Outlook in a second session, such as from a second monitor or a different device. Users who need to access multiple mailboxes simultaneously will see an error. Set the value to 2 or 3 if your users typically work with two or three profiles.

Enabling Idle Timeout Without Warning Users

When the idle timeout expires, Outlook signs the user out without saving unsent messages. Drafts are saved automatically, but users may lose unsent replies in the compose window. Inform users to save drafts frequently or set the timeout to at least 60 minutes.

Disabling Caching on a Slow Network

On a VDI host with a high-latency connection to Exchange Online, disabling caching makes Outlook nearly unusable. Each folder open triggers a network request. Test the network latency first. If the round-trip time exceeds 100 milliseconds, keep caching enabled.

New Outlook VDI vs Classic Outlook VDI: Key Differences

Item	New Outlook VDI	Classic Outlook VDI
Cache location	User profile folder in AppData\Local\Microsoft\Outlook\NewOutlook	User profile folder in AppData\Local\Microsoft\Outlook\Offline Address Books
Session limit range	1 to 10 concurrent sessions	Not supported natively
Idle timeout range	1 to 1440 minutes	Not supported natively
Group Policy node	Microsoft Outlook 2016 > Outlook Options > VDI	Microsoft Outlook 2016 > Outlook Options (no VDI subfolder)
Cache disable option	Enabled via policy Disable local caching in VDI	Enabled via policy Do not download shared folders or Cached Exchange Mode settings

You now know the exact Group Policy and registry paths for new Outlook VDI settings. Configure MaxConcurrentSessions to a value between 2 and 4 for most environments. Test the idle timeout with a small pilot group before rolling it out broadly. If your VDI host uses persistent user disks, keep caching enabled to reduce network load.