HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
Outlook for Windows display name change
Starting July 2024, the Outlook for Windows app name will change to “Outlook (classic)” to distinguish it from the new Outlook. This will be reflected in version 2407 and higher. The change aligns with support documentation and does not affect the app’s status or support. No action is required from administrators. Rollout will begin late July 2024 and complete by January 2025 across different channels.
Starting in July 2024, Microsoft will change the app name of the current Outlook for Windows for all customers as it appears in the Start menu now from “Outlook” to “Outlook (classic)”. This is not a change in status or support for the classic Outlook app. Please continue to refer to our blog post timeline for product support and availability. https://aka.ms/newOutlookTimeline. This change is intended to differentiate it from the new Outlook for Windows. Users will see this update in classic Outlook version 2407 and higher.
This naming convention now also aligns with how it is referred to in support documentation. For instance, at the top of articles like this one on using favorites, there are tabs for different instructions in new Outlook and classic Outlook so users can find the instructions appropriate for the version they are on.
When this will happen:
Users will see the new app name in the Start menu after they install version 2407 or later.
- Current Channel: We will begin rolling out late July 2024 and expect to complete by early August 2024.
- Monthly Enterprise Channel will get this update September 2024
- Semi-annual channel will get this update January 2025
How this will affect your organization:
This change will only affect the app name as it appears in the Start menu installed apps list and Start pinned apps. The app icon and the executable file name will remain the same.
What you need to do to prepare:
There is no action required for administrators to prepare for this change. This change also cannot be configured differently per organization.
Message ID: MC803006
