New Outlook is getting better at one of the everyday tasks that users notice most: opening the message behind a Windows notification. According to Windows Latest testing, a recent July update appears to reduce the wait from roughly ten seconds to about five seconds when a user clicks a new-mail notification. That is meaningful progress, but it also underlines why many organizations still treat Classic Outlook as the more dependable desktop client.
For IT teams, this is not just a small annoyance. Notification handling sits directly in the flow of triage, incident response, help desk communication, sales follow-up, and executive scheduling. A five-second mailbox detour repeated dozens of times per day becomes a real productivity tax, especially when the older application performs the same action almost instantly.
What appears to have changed
Windows Latest reports that New Outlook version 1.2026.713.100 opens notification-linked messages faster than it did in earlier testing. The app still launches into the broader mailbox experience before showing the specific email, but the delay is now closer to five seconds instead of ten. Microsoft has not publicly promoted this as a named feature; the closest official wording appears to be a broad “functionality and performance” fix in the July update cycle.
That type of quiet improvement is common with modern Microsoft 365 apps. New Outlook updates continuously, and fixes often arrive without the clear release-note detail administrators would prefer. The practical takeaway is simple: if your users complained about notification clicks being unusually slow, retest the current build before assuming the behavior is unchanged.
Why Classic Outlook still feels faster
Classic Outlook remains difficult to beat because it is a mature native desktop application optimized over many years for local interaction, cached mailboxes, and immediate UI response. New Outlook, by contrast, is built around a web-based architecture using Microsoft Edge WebView2 components. That gives Microsoft a single modern code path across Windows, web, and other endpoints, but it can also make ordinary desktop actions feel less direct.
The difference shows up most clearly in small moments. Opening an email from a toast notification, switching views, or working with messages while the app is still loading may not look important on a roadmap slide, but those interactions shape user trust. If a notification click does not take a person directly to the message, the user starts to treat the app as unreliable even if the message eventually appears.
Windows Latest also points to broader resource differences previously observed between the two clients, with New Outlook using substantially more memory and processes than Classic Outlook. That is not automatically disqualifying on modern hardware, but it matters on shared devices, older laptops, virtual desktops, and environments where Teams, browsers, security agents, and line-of-business apps are already competing for resources.
The transition pressure is not going away
Microsoft still intends to move Outlook users toward the newer client, while Classic Outlook remains supported for a longer runway. That creates a planning challenge: organizations cannot simply ignore New Outlook, but they also do not need to pretend it has reached feature and performance parity in every workflow.
At the same time, Microsoft is shifting more productivity messaging toward Copilot. Classic Outlook is receiving Copilot-related surfaces and some legacy features are being retired or replaced by Copilot-linked experiences. New Outlook, meanwhile, continues to collect features that Classic users expect, including reusable text components, Planner integration, better offline capabilities, stale-reply warnings, drag-and-drop categorization improvements, and expanded archive support.
This is a familiar Microsoft migration pattern. The new app improves quickly, the old app remains more comfortable for power users, and administrators are left to decide when the balance changes enough to justify a default switch.
Practical advice for administrators
First, verify the version of New Outlook in your own tenant and test notification behavior on representative hardware. Do not rely only on a high-end test machine. Include a standard laptop, a device with a large mailbox, and any virtual desktop profile that runs Outlook heavily.
Second, segment users by workflow. Employees who mostly read and send simple mail may be ready for New Outlook sooner. Executive assistants, legal teams, finance users, support teams, and anyone who depends on advanced mailbox handling may still need Classic Outlook until the remaining gaps are closed.
Third, document the exact behaviors that block adoption. “Users do not like New Outlook” is hard to act on. “Notification clicks take five seconds and open the inbox before the selected message” is a measurable issue that can be tracked after each update.
Finally, keep communication honest. New Outlook is improving, and cutting a delay in half is a real fix. But Classic Outlook still wins the responsiveness test that matters most here: click a notification, see the email immediately. Until New Outlook can make that feel native, cautious rollout remains the right approach for many Windows environments.
Source: Windows Latest source