MC854648 – (Updated) Admin policy to migrate users from classic Outlook to new Outlook for Windows (archived)

Outlook logo

check before: 2024-08-01

Product:

Microsoft 365 Apps, Outlook

Platform:

Online, US Instances, Web, World tenant

Status:

Change type:

Admin impact, New feature, Updated message, User impact

Links:

Details:

Summary:
Microsoft has updated the Admin-Controlled Migration to New Outlook policy, allowing IT admins to migrate users from classic to new Outlook for Windows. The migration involves a three-step process to encourage users to switch, with prerequisites and settings detailed for policy implementation. Rollout begins early August 2024, completing by mid-September 2024.

Details:
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 attempts
A 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).

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2024-08-08

updated:
2024-09-05

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

Pictures

XXXXXXX ... free basic plan only

Direct effects for Operations**

User Experience Disruption
Users may experience confusion and frustration during the migration process, especially if they are not adequately prepared for the changes in interface and functionality of the new Outlook.
   - roles: End Users, IT Support Staff
   - references: https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-on-the-web/enable-disable-employee-access-new-outlookuse-the-registry-to-enable-or-disable-the-new-outlook-toggle-in-outlook-desktop

Increased Support Requests
The transition to the new Outlook may lead to a spike in support requests from users who encounter issues or have questions about the new features, impacting IT support resources.
   - roles: IT Support Staff, Help Desk Personnel
   - references: https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-on-the-web/enable-disable-employee-access-new-outlookuse-the-registry-to-enable-or-disable-the-new-outlook-toggle-in-outlook-desktop

Configutation Options**

XXXXXXX ... paid membership only

** AI generated content. This information must be reviewed before use.

a free basic plan is required to see more details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.



change history

DatePropertyoldnew
2024-09-05MC MessageTagNamesNew feature, User impact, Admin impactUpdated message, New feature, User impact, Admin impact
2024-09-05MC SummaryMicrosoft is introducing an 'Admin-Controlled Migration to New Outlook' policy, enabling IT admins to migrate users from classic to new Outlook for Windows. The migration involves three steps, with prompts and messages guiding users through the process. The policy includes settings for re-initiating migration if users revert to classic Outlook.Microsoft has updated the Admin-Controlled Migration to New Outlook policy, allowing IT admins to migrate users from classic to new Outlook for Windows. The migration involves a three-step process to encourage users to switch, with prerequisites and settings detailed for policy implementation. Rollout begins early August 2024, completing by mid-September 2024.
2024-09-05MC Last Updated08/08/2024 04:26:592024-09-05T00:25:34Z
2024-09-05MC MessagesMicrosoft 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 attempts
A 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-August 2024.
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 attempts
A 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).
2024-09-05MC TitleAdmin policy to migrate users from classic Outlook to new Outlook for Windows(Updated) Admin policy to migrate users from classic Outlook to new Outlook for Windows
2024-09-05MC End Time09/30/2024 09:00:002024-10-28T08:00:00Z

Last updated 1 month ago

Share to MS Teams

Login to your account

Welcome Back, We Missed You!