Support
 
PhoneGet Quote
 
Support
 
US Sales: +1 888 720 9500
US Support: +1 844 245 1108
Intl: +1 925 924 9500
Aus: +1 800 631 268
UK: 0800 028 6590
CN: +86 400 660 8680

Direct Inward Dialing: +1 408 916 9890

 
 
Banner Image
Best Practices

What is an OWA mailbox policy?

Posted on Feb 27, 2026
Written by Ashwin Kumar
 
On this page
  • How an Outlook web app mailbox policy is used in the real world
  • What OWA policies actually control
  • How to manage Outlook web app policies using Exchange Online PowerShell
  • OWA policy best practices
  • Manage your Exchange Online protocols and more

Microsoft 365 makes email accessible from anywhere. That convenience is useful, but it is also one of the easiest ways organizations lose control over sensitive data. This demands a level of control that needs to be exercised so only those who need access to sensitive data or high-level features can have them, without impacting the workflow of other employees.

An Outlook web app (OWA) mailbox policy (previously known as an OWA mailbox policy) functions as a configuration template that determines which features are available to users when they access their email via the web, without installing the Outlook app on their devices. These policies exist to control what users can do with email when they access it through a browser.

This page focuses on how OWA policies are used in organizations, what you can control with them, and how you can get your policies up and running.

How an Outlook web app mailbox policy is used in the real world

Organizations typically deploy OWA policies to solve these specific business challenges:

1. Frontline workers

For employees who share workstations or work in retail/manufacturing, admins create a "Light" policy.

  • Goal: Keep the interface simple, fast, and strictly limited to business communication.
  • Action: Disable Premium features, LinkedIn integrations, and the ability to add personal accounts.

2. Remote access governance

When users access email from unmanaged or public devices, data leakage is a massive risk.

  • Goal: Ensure that sensitive company data never leaves the secure Microsoft 365 cloud environment to stay on a public hard drive.
  • Action: Disable Direct File Access (downloading) and force WebReady Document Viewing (preview only).

3. Corporate branding and compliance

Large enterprises often need to prevent certain configurations such as adding personal Gmail or Outlook accounts.

  • Goal: Force the use of server-side signatures for legal branding and prevent users from accidentally sharing their full calendars with external vendors.
  • Action: Disable the Email Signature and Calendar Sharing settings. Configure AllowedOrganizationAccountDomains to only include your company domain.

What OWA policies actually control

OWA policies define what users can and cannot do inside a browser-based mailbox in Exchange Online.

In practical terms, they control whether Outlook on the web is available at all, which mailbox features appear in the browser, and how much functionality is exposed on unmanaged systems.

OWA policies do not replace Conditional Access, data loss prevention (DLP), or endpoint management. They complement them by controlling behavior inside the email client after Conditional Access has already vetted the entry.

When you create or edit an Outlook on the web policy in the Exchange admin center, settings are grouped into clear functional sections. The following sections determine how rich or restricted the browser experience is for end users:

Communication management

This controls how users communicate and sync data through the Outlook client. This includes the following protocols that can be toggled:

  • Instant messaging: Controls the integration of the Chat functionality from Teams within the OWA interface. Disabling this keeps the mailbox strictly for email.
  • Text messaging: Allows or restricts the ability to send SMS messages via the mailbox (this is less common now but is still a legacy integration point).
  • Exchange ActiveSync: Disabling Exchange ActiveSync prevents the user from using the ActiveSync protocol to synchronize OWA data with third-party mail apps.
  • Contacts and contact sync: Determines whether the People module is visible and whether users can sync those contacts to external devices.
  • All address lists: If disabled, users can only see their own contacts and the Global Address List (GAL), but not custom address lists or departmental groupings.

Information management

This controls how users organize, automate, and recover mailbox data, by controlling the availability of the following actions:

  • Journaling: Enables or disables the older Journal folder features to record actions such as meetings and tasks.
  • Notes: Toggles the Notes folder (requires an integration with Outlook Notes).
  • Inbox rules: Prevents users from creating automated forwarding or filing rules when disabled.
  • Recover deleted items: Toggles the ability for users to recover items after they have been deleted from the Deleted Items folder (accessing the Recoverable Items partition).

This area is frequently tightened in regulated environments to reduce automation-based data risks.

Security

This determines whether a user can change their own password from the Outlook client.

Many organizations disable browser-based password changes and instead route them through centralized self-service portals.

User experience

Controls how full-featured or minimal the Outlook on the web experience is. This controls the availability of the following options in their Outlook client:

  • Themes: Allows or prevents users from changing the color scheme and background of their OWA interface.
  • Premium client: If disabled, users are forced into the "Light" version of Outlook, which is a basic HTML interface for low-bandwidth consumption.
  • Email signature: Allows or prevents users to create a local signature in the browser.
  • Weather, Places, Local events: Shows local forecasts or map data by having OWA reach out to external services. Disabling these options remove the respective widgets.
  • Interesting calendars: Allows or prevents adding public calendars such as sports calendars.

Time management

Controls whether additional features that involve calendars and event bookings can be accessed by the user.

This includes:

  • Calendar: Enables or disables the Calendar functionality. Disabling it removes any calendar-based notifications such as meeting invites. They will still receive email-based invites but without any calendar functionality such as the option to accept or decline them, or other users being alerted of their availability.
  • Tasks: Toggles access to Microsoft To-Do from within the browser.
  • Reminders and notifications: Controls the pop-ups and notification alerts for upcoming meetings or new mail without affecting other functionalities, like a DND toggle.

These features are commonly limited for temporary users or restricted access scenarios.

How to manage Outlook web app policies using Exchange Online PowerShell

You can create and apply your Outlook web app policies using the Exchange Admin Center (EAC) and Exchange Online PowerShell. In this page, we will look at how to create and apply your Outlook web app policies in one session using Exchange Online PowerShell.

Create a Outlook web app policy in Exchange Online

Use the following syntax to create a new Outlook web app mailbox policy:

New-OwaMailboxPolicy -Name "Test"

You can modify the Outlook web app mailbox policy using the Set-OWAMailboxPolicy cmdlet:

Set-OWAMailboxPolicy -Identity "Test" -AttachmentsOnSendEnabled $false -InstantMessagingEnabled $false -CalendarEnabled $false

Apply a Outlook web app policy in Exchange Online

Use the Set-CASMailbox cmdlet to assign a specific Outlook web app mailbox policy to a user:

Set-CASMailbox -Identity user@domain.com -OwaMailboxPolicy "Test"

You can check out the following pages for more information on Outlook Web App policies, how to manage them using EAC, and how to manage them in bulk using Exchange Online PowerShell.

OWA policy best practices

When an OWA policy is edited, it determines how the end user will use and perceive Outlook on their device. Whether the end user should be allowed to use all tools to get the maximum productivity, Outlook should be stripped to its bare essentials for maximum security, or there is a middle ground to find for a daily user depends on your organizational requirements. However, it is recommend you keep some pointers in mind when you customize OWA policies to your specifications so that you do not end up sacrificing the stability of your user experience for a specific goal.

Secure the default Outlook web app mailbox policy

When a new mailbox is created, the OwaMailboxPolicy-default mailbox policy is applied automatically unless you specify otherwise. Ensure this default policy is configured securely.

Audit Exchange Online features

Regularly review which users are assigned highly privileged OWA policies and which users have legacy protocols (such as Exchange ActiveSync enabled) in order to prevent data leakage via unmonitored features (like file sharing).

Control offline access

Manage offline access settings within the policy to prevent email data from being cached on devices that might not be secure.

Restrict off-boarders with tighter OWA policies

By applying a policy that disables everything (Calendar, Rules, File Access) the moment a departure is announced, you ensure that the user cannot export contacts or set up malicious forwarding rules—even if a session remains open.

Manage your Exchange Online protocols and more

While native admin centers and Graph PowerShell scripting can help you create OWA mailbox policies and apply them to your mailboxes, you either need a great deal of patience to make changes to mailboxes one by one or extensive knowledge of PowerShell scripting to carry out your complex and bulk operations. This is where ManageEngine M365 Manager Plus helps you simplify your Microsoft 365 administration.

M365 Manager Plus is a comprehensive administration and security solution for Microsoft 365. It is used for reporting on, managing, monitoring, auditing, and creating alerts for critical activities in your Microsoft 365 environments. Its mailbox management capabilities help you view, monitor, and modify not just your OWA mailbox policy settings, but also other Exchange Online mailbox properties like mailbox quotas, archive status, and inbox rules. You can carry out complex tasks like configuring retention policies, converting mailboxes, and more with just a series of clicks. Instead of juggling scripts or exporting raw data for manual filtering, M365 Manager Plus gives you ready-to-use reports and easy scheduling.

Bulk mailbox management

Handle large-scale mailbox actions—such as enabling features, updating settings, or modifying permissions—through simple, GUI-driven operations. No manual scripts, no repetitive tasks.

Reports on Microsoft 365 mailboxes

Access ready-made reports that cover mailbox size, activity, mailbox features, license usage, storage trends, permission assignments, and more. Get the insights you need without digging through multiple admin centers.

Real-time alerts on mailbox changes

Set up instant alerts for critical mailbox changes, including permission updates, forwarding rule modifications, and configuration changes. Stay aware of risky or unauthorized activity as it happens.

Eliminate PowerShell complexity

Perform mailbox audits, configuration checks, and bulk updates without relying on cmdlets or scripting expertise. One-click actions reduce errors and make mailbox administration far more manageable.

More blogs like this

Thumbnail Optimization

Azure AD management 101

 
Thumbnail Best practices

10 ways to level up your Entra ID management

 
Thumbnail Optimization

SharePoint alerts retiring in 2026

 
 
A holistic Microsoft 365 administration and security solution