Outlook Build 16.58 (February 2022 update) will default to the New Outlook experience
Page Last Updated: January 28, 2022 @ 12:05pm Pacific Time

Heads-up!

When Outlook 16.58 is released to the Current Channel on February 15, 2022 both existing and new users will be automatically opted-in to the 'New Outlook' experience.
Users will be able to switch back to Classic Outlook (aka Legacy Outlook) through the Help menu.

NOTE: The Outlook 16.58 database schema will move forward to revision 38.0 (was 37.0 in 16.57) which means that it won't be possible to downgrade to 16.57 and earlier (unless you delete the Outlook profile).
This schema change will affect all users, regardless of settings and exceptions listed below.

Exceptions

The following users will continue to default to 'Classic' Outlook:

Message Center

Microsoft 365 tenant admins were notified about this change on January 18, 2022 through Message Center post MC315650

Rude Q&A

1. Does this mean that New Outlook now has feature parity with Classic Outlook?
No, there are still some gaps. Most notably:


2. Can I configure the settings ahead of time so that my users don't see any change when 16.58 rolls-out?
Yes. Your best option is to explicitly set the EnableNewOutlook preference to integer value 1. You can do this via the defaults command or through a Configuration Profile.
The defaults command is: defaults write com.microsoft.Outlook EnableNewOutlook -integer 1

With this setting in place, existing 'Classic' users will continue to run in 'Classic' mode, but they will see the New Outlook switch if they wish to try the 'New' experience.
Likewise, your existing 'New Outlook' users will continue to run in that mode - and they'll still see the option to revert to 'Classic' mode.

3. Do you have a table that shows the different values of the EnableNewOutlook preference, and how the result differs between builds of Outlook?

Preference Value (integer)Builds 16.57 and earlierBuilds 16.58 and later
Not set (default)Defaults to Classic Outlook. Users may switch to New OutlookDefaults to New Outlook. Users may revert to Classic Outlook
0Classic Outlook only - no ability to switch to New OutlookClassic Outlook only - no ability to switch to New Outlook
1Defaults to Classic Outlook. Users may switch to New OutlookDefaults to Classic Outlook. Users may switch to New Outlook
2Defaults to New Outlook. Users may revert to Classic OutlookDefaults to New Outlook. Users may revert to Classic Outlook
3New Outlook only - no ability to switch to Classic OutlookNew Outlook only - no ability to switch to Classic Outlook


4. You mention that the Outlook database schema changes in 16.58. What will happen if I upgrade, but then downgrade to 16.57?
Your users will see this error message when launching Outlook 16.57 and earlier:

You have two options at this point a) upgrade to 16.58 or later b) use the Outlook Data Removal tool to remove the existing profile.
The second option should be used with caution as it will remove any 'On my computer' folders that exist, plus the user will need to wait for their mailbox to resync from the server.

5. Okay, I have my settings in place. Is there any way I can do a realistic test with an early 16.58 build before it hits the streets on 2/15?
Yes! Download and install the early release package from the Office CDN.
This package can be used to update an existing version of Outlook, or to install Outlook 16.58 on a new machine.

6. Some of my users run in 'New Outlook' mode, and some run 'Classic'. Is there any way to run a report across my fleet to see this data?
Yes, if you use Jamf Pro for Mac management, you can add this Extension Attribute.

7. Help! 16.58 just rolled out and I'm reading this article for the first time. Users are calling the helpdesk saying that Outlook looks different. What should I do?
Some users may actually enjoy all the new features - but we get it - others just might not be ready. Helpdesk can tell them to click the 'Help' menu and choose 'Revert to Legacy Outlook'