"OWA Light was an important compatibility experience when the web needed it. Today, the full Outlook on the web experience is the right place for us to focus," the Exchange Team said on Wednesday.
Why Microsoft is retiring OWA Light
Microsoft's Exchange Team announced this week that it will disable the Outlook Web Access (OWA) Light client in an upcoming Exchange Server update estimated for August 2026. The stated goals are straightforward: reduce legacy surface area, simplify ongoing engineering work, and concentrate development on the modern Outlook on the web experience. In Microsoft's words, "the web has changed significantly since OWA Light was introduced. Modern browsers are more capable and more consistent, network conditions have improved for many customers, and [the] security landscape has changed significantly."
What OWA Light was and what it lacked
Introduced roughly two decades ago, OWA Light provided a simplified web interface when full-featured web browsers and ubiquitous, modern browser capabilities were not a given. Microsoft originally positioned it as an alternative to OWA Premium for environments without Internet Explorer 6 or later and for locked-down browser modes such as kiosks. OWA Light delivered a cleaner look and faster logon times on low-bandwidth connections.
Those design trade-offs came with limitations. The OWA Light client omits several features available in the full Outlook on the web experience, including weekly or monthly calendar views, access to shared mailboxes or shared calendars, the ability to import or export messages or contacts, and the ability to create or modify tasks or notes.
Timeline: deprecation and planned removal
Microsoft deprecated OWA Light as of August 19, 2024. This week's announcement says the experience will likely be removed from on-premises Exchange Server in an upcoming update estimated for August 2026. After that change is introduced, "users will no longer be able to choose or be redirected to OWA Light and should use the modern Outlook on the web experience instead," the Exchange Team said.
Actions available to administrators today
Administrators who want to block OWA Light immediately do not need to wait for the server update. Microsoft published two Exchange Management Shell commands that will disable the client and remove the logon selection option:
- To block OWA Light at the mailbox policy level: Set-OwaMailboxPolicy -OwaLightEnabled $false
- To remove the OWA Light selection menu from the logon page: Set-OwaVirtualDirectory -LogonPageLightSelectionEnabled $false
Microsoft also points administrators to the Set-OwaMailboxPolicy and Set-OwaVirtualDirectory documentation for further guidance on disabling or blocking OWA Light.
What this means for administrators, end users, and security teams
- Administrators and IT operations: Expect to plan for migration of any users or locked-down environments still relying on OWA Light. Administrators can proactively enforce the change with the provided commands or prepare for the automatic removal in the Exchange Server update estimated for August 2026.
- End users: After the change is rolled out, users will no longer be able to select or be redirected to OWA Light and should use the modern Outlook on the web experience instead. Users who depended on OWA Light's simplified interface or lower-bandwidth behavior will need to be accommodated or retrained.
- Security teams: Microsoft frames the retirement as a reduction of legacy surface area and an engineering simplification that supports continued improvements to the modern client. Security teams that track legacy web-exposed surfaces may view the removal as narrowing of attack paths tied to older interfaces.
Microsoft's decision caps a long arc: a lightweight client built for an earlier web era is being retired as browsers, networks, and security models evolved. Administrators have concrete, supported steps to disable OWA Light today, and an Exchange Server update estimated for August 2026 will make that choice irreversible for on-premises environments. For organizations that still depend on the lighter client, the calendar is set — and the documentation Microsoft cites is the immediate place to begin planning.
