Microsoft has delayed the retirement of the Outlook for Windows Usage Report in the Exchange admin center, extending a timeline that organizations had been planning around. The report was originally scheduled to be retired by September, but the company has now pushed the date back, according to Neowin’s reporting on the change.
For now, the report remains available, giving IT teams more time to adjust their monitoring and reporting workflows before any final removal.
What the Outlook for Windows Usage Report does
The Outlook for Windows Usage Report lives inside the Exchange admin center (EAC), Microsoft’s web-based management interface for administering Exchange Online and on-premises Exchange deployments. It provides administrators with usage data tied to Outlook for Windows across their organization.
In practice, these reports are designed to help IT professionals understand adoption patterns—such as how many users are running Outlook for Windows, which versions are in play, and how engagement trends over time. That information has historically been useful for planning migrations, shaping support decisions, and tracking the shift toward newer client versions.
The report is one of several telemetry-driven views that Microsoft has layered into the Exchange admin center over the years as it moved toward more data-driven administration. It sits alongside other usage and adoption reports that give admins a window into how their tenants are actually using Microsoft 365 collaboration tools.
Why the retirement was delayed
Microsoft routinely announces deprecation timelines for features within the Exchange admin center, giving customers advance notice before a capability is removed. The Outlook for Windows Usage Report was on one such list, with September set as the target retirement date.
Rather than proceeding on that schedule, Microsoft has now delayed the removal. The specific new date has not been detailed in the reporting available so far, so organizations should treat the revised timeline as still being finalized.
This kind of adjustment is not unusual. Microsoft occasionally extends deprecation windows when it determines that customers need additional runway, or when internal review surfaces reasons to reconsider a removal date. Extending a deadline is often a pragmatic response to real-world adoption timelines that don’t match the original plan.
What this means for you
If you manage an Exchange environment and have been planning around the September deadline, the delay is a reprieve. You no longer need to rush to export data or build workarounds before the report disappears.
However, the underlying direction hasn’t changed. Microsoft’s broader effort to consolidate and modernize the Exchange admin center continues, and reports like this remain candidates for eventual retirement. The delay simply gives you more time to prepare rather than canceling the plan altogether.
For teams that rely on this report for regular usage tracking, it’s worth confirming whether a replacement or alternative data source exists in the newer admin center interfaces, so you aren’t caught off guard when the final date is set.
What to do while you wait
The practical move is to keep using the report as you normally would, but to treat the extended timeline as temporary rather than permanent. A few steps make sense:
- Document your current reporting workflow so knowledge isn’t lost if staff change.
- Check the Microsoft deprecation resources and the Exchange admin center changelog for an updated removal date.
- Identify any alternative data sources—such as telemetry in the newer admin center or Microsoft 365 analytics—that could replace the report when it eventually goes.
Because the revised date hasn’t been pinned down yet, it’s wise to build flexibility into any migration plans rather than treating the old September deadline as a hard stop.
The wider Exchange admin center transition
The delay sits within Microsoft’s larger push to modernize the Exchange admin center. The company has been consolidating management tools and migrating administrators toward a newer, more unified interface, retiring legacy features along the way as part of that effort.
From an administrative standpoint, the extended window is generally welcome. It reduces the risk of organizations losing visibility into Outlook for Windows usage mid-migration, and it avoids forcing rushed decisions under a tightening clock.
That said, the eventual retirement is still expected. Organizations should continue planning for a world where the Outlook for Windows Usage Report is no longer available, even if the calendar for that has slipped.
What this means for Exchange administration
Exchange admin center features have long followed a deprecation model in which capabilities are announced well in advance, then removed once customers have migrated. This delay fits that pattern, just on a shifted timeline.
The extra runway gives IT teams a chance to finalize their reporting strategy without the pressure of an imminent deadline. It also signals that Microsoft is willing to adjust its own schedules when adoption doesn’t keep pace with the plan.
For now, keep using the report, keep an eye on official deprecation updates, and plan for the day it eventually goes—just with a little more breathing room than before.
Source: Neowin
Over to you: Are you still relying on the Outlook for Windows Usage Report for your monthly adoption tracking, or have you already moved to an alternative data source?
