Microsoft is formally retiring the lightweight version of Outlook on the Web for on-premises Exchange Server, with removal planned for a future update around August 2026. The company’s Exchange Server team confirmed the timeline in a recent advisory, signaling the end of the simplified HTML client that has served as a fallback for low-bandwidth connections and basic accessibility needs for more than two decades.

The Announcement: What’s Changing and When

According to Microsoft’s advisory, OWA Light will be disabled and then removed in a forthcoming Exchange Server update—most likely a Cumulative Update (CU)—currently estimated to land in August 2026. No specific build number or KB article has been tied to the change yet, and Microsoft notes that the timeline is an estimate that could shift. Once the update installs, the /owa URL path will no longer offer the Light experience; users who attempt to access it will either be redirected to the standard Outlook on the Web interface or see an error, depending on how the retirement is implemented.

The move affects all supported versions of Exchange Server that still include OWA Light. At this point, that means Exchange Server 2019 and any successors Microsoft releases before the cutoff. Exchange Server 2016 fell out of mainstream support in 2021 and is already in extended support, so administrators running it should already be planning a migration for other reasons—but they, too, will lose OWA Light if they still have it enabled.

Who’s Affected? Checking Your Dependencies

OWA Light isn’t a separate product; it’s a rendering mode of Outlook on the Web that kicks in automatically for very old browsers or when users explicitly choose the “Use the light version” option on the login screen. The interface is a minimal HTML table-based layout with no JavaScript, no drag-and-drop, and severely limited feature parity with the full OWA. It was designed for Internet Explorer 6-era browsers, slow dial-up connections, and screen readers that struggled with rich web applications.

If your organization still has any of the following, you may have users who depend on OWA Light:

  • Thin clients or locked-down workstations running outdated browsers that cannot be upgraded.
  • Users on extremely low-bandwidth connections—satellite links, marine vessels, remote field offices—where the full OWA’s payload is too heavy.
  • Employees who rely on specific assistive technologies that worked better with the Light interface.
  • Legacy web applications or scripts that automate tasks by scraping OWA Light’s simple HTML.

Microsoft has steadily improved the accessibility and performance of standard Outlook on the Web over the years. Modern screen readers work well with the full interface, and the performance gap on moderate connections has narrowed significantly. But the only way to know if your organization will feel the loss is to check your own usage data.

Administrators can gauge OWA Light adoption by reviewing Internet Information Services (IIS) logs on Exchange Client Access servers. Look for HTTP GET requests to paths containing “/owa/” with query string parameters like ?layout=light or ?explicitLogonReason=light. Exchange also logs the client type in the msExchClientType field of mailbox audit logs. If you see a non-trivial volume of Light sessions, you have work to do.

Why Now? The Long Decline of a Legacy Interface

OWA Light has been on life support for years. Microsoft discontinued support for the feature in Exchange Online back in 2019, effectively drawing a line under it for cloud customers. The on-premises version stuck around largely because of the slower upgrade cadence of on-prem deployments and a desire not to break workflows for organizations with hard-to-replace legacy hardware.

But the writing has been on the wall. Exchange Server’s web client architecture has been rebuilt multiple times since the Light version was introduced in Exchange 2000. The modern Outlook on the Web is a single-page application built on React that shares code with the Outlook.com consumer service. Maintaining a second, completely separate rendering pipeline creates technical debt, increases the attack surface, and consumes engineering resources that could go toward security hardening or new features.

The removal also aligns with broader industry shifts. All major browsers now support the modern web standards that the full OWA requires. Internet Explorer, the original target for OWA Light, was retired by Microsoft in 2022. Even in bandwidth-constrained environments, HTTP/2 and compression make the full OWA feasible on links above 256 Kbps—speeds that are increasingly common even in remote areas.

Action Plan for Administrators

The August 2026 deadline gives administrators roughly two years from now to prepare. Here’s a concrete plan to start executing today:

  1. Inventory your client landscape. Identify every device, browser version, and assistive technology stack used to access webmail. Focus on machines that cannot run a modern evergreen browser (Chrome, Edge, Firefox) or that are locked behind strict group policies.
  2. Audit OWA Light usage. Use the IIS log and mailbox audit methods described above to quantify how many users actually invoke the Light interface over a typical month. Often, the number is far smaller than administrators fear.
  3. Communicate early. Draft an internal notice explaining that OWA Light will disappear in mid-2026 and that users still relying on it should contact IT. Emphasize that the change is driven by Microsoft and that your team is proactively preparing.
  4. Test alternatives. For most users, the fix is simply to start using the full Outlook on the Web. Instruct pilot users to visit the /owa URL, deselect “Use the light version” if they’ve previously checked it, and verify that the rich interface works acceptably on their connection and hardware.
  5. Address accessibility gaps. If you have employees who specifically require the Light experience for assistive technology, work with your accessibility team to evaluate modern screen readers (JAWS, NVDA, Narrator) against the full OWA. In many cases, the built-in accessibility features now match or exceed what the Light version offered. If gaps remain, file a support ticket with Microsoft and consider interim workarounds like Outlook desktop or the Outlook mobile app.
  6. Plan for browser upgrades. For machines stuck on legacy browsers, prioritize upgrading to an evergreen browser. If that’s impossible due to a line-of-business dependency, investigate application virtualization or Remote Desktop Services as a bridge to run a modern browser in a sandbox.
  7. Keep an eye on Exchange updates. Microsoft will presumably give additional notices as the August 2026 update approaches. Monitor the Exchange Team Blog and the Microsoft 365 admin center for formal KB articles and any adjustments to the timeline.

Outlook: More Legacy Features on the Chopping Block?

The retirement of OWA Light follows a pattern Microsoft has established: strip away legacy components from on-premises Exchange to reduce complexity and align with the cloud. The same logic has already claimed Exchange Unified Messaging (replaced by cloud voicemail), the classic Exchange admin center (already deprecated), and MAPI-over-HTTP legacy protocols. Each removal forces administrators to modernize a small part of their infrastructure.

What comes next? The Exchange team hasn’t announced further retirements, but logical candidates include the offline address book (OAB) download over HTTP, which has been supplanted by Autodiscover-based downloads, and the Exchange Management Console remnants that still linger in some environments. The bigger takeaway is that any Exchange feature that has a modern equivalent in Office 365 is a candidate for removal in an upcoming CU.

For now, the priority is OWA Light. Two years feels like a long time, but for large, distributed organizations with thousands of endpoints, the clock is already ticking. Start the audit now, communicate clearly, and treat this as an opportunity to jettison a 25-year-old relic once and for all.