Admin policy to migrate users from classic Outlook to new Outlook for Windows

Updated September 4, 2024: We have updated the rollout timeline below. Thank you for your patience Microsoft is releasing a new Admin-Controlled Migration to New Outlook policy that will allow IT admins to migrate users from classic Outlook for Windows to new Outlook for Windows. User experience Enabling this policy (see instructions below) switches users from classic Outlook to new Outlook in three steps. Each step runs on a new app session (app launch).  Step 1: Users see a teaching callout encouraging them to try the new Outlook in the first session after the migration policy is enabled. Step 2: If users don’t switch to new Outlook in step 1, they’ll see this Business bar message in the next session: “Your organization recommends using the new Outlook for Windows. If you skip this now, you’ll be taken to the new experience the next time you start Outlook.” Step 3: Users see a blocking prompt encouraging them to switch to new Outlook. Users will be able to toggle back to classic Outlook for Windows any time.   Pre-requisite to enabling the policy The new Outlook toggle should be available to users; users will not see the migration experience if the new Outlook toggle is hidden via group policy (GPO) or Windows Registry key. If you previously disabled access to the toggle, you can enable it by following the instructions here: Enable or disable access to the new Outlook for Windows. Setting the policy Policy name:Admin-Controlled Migration to New Outlook Possible values (Boolean): 1 (enabled) / 0 (disabled) This is a GPO and can be managed via Cloud Policy. It can also be deployed as a Registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\General “DoNewOutlookAutoMigration”: dword:00000001 The migration will run only once until users switch to new Outlook. You can set the interval policy (see below) to re-initiate migration in the scenario that users toggle back to classic Outlook. The policy functionality can be used in Current Channel Version 2406 (Build 16.0.17830.20138). Policy to define the interval between migration attemptsA new Interval between new Outlook migration attempts policy can be used to re-initiate the migration to new Outlook for Windows if users switch back to classic Outlook, based on the defined interval. Pre-requisite: The admin-controlled migration policy must be enabled for this policy to be respected. Policy name: Interval between new Outlook migration attempts Possible values:0/Not set: New Outlook for Windows migration will not be re-initiated.1: Migration will be attempted each time and users will see the blocking prompt (as in step 3) on every launch of classic Outlook for Windows.2-99000 (N): Migration will be re-initiated from step 1 N days after user switches back. This is GPO and can be managed via Cloud Policy. It can also be deployed as a Registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\General “NewOutlookAutoMigrationRetryIntervals”: dword:00000001 Important note: new Outlook is not supported in on-premises environments and in sovereign clouds. When will this happen: General Availability (Worldwide, GCC): We will begin rolling out early August 2024 and expect to complete by mid-September 2024 (previously mid-August). How this will affect your organization: No changes will be made unless you enable this policy for a set of or for all of your users. Users who have this policy enabled will go through the migration flow as described above. What you need to do to prepare: No action is required to prepare for the rollout. Organizations ready to migrate users to the new Outlook for Windows can use this policy.