Outlook for Mac Purview DLP Policy Tips Are Disabled by Default: How Admins Enable Them

Microsoft’s roadmap record for feature 558689 lists the status as Launched, with November 2025 preview timing and May 2026 general availability for Worldwide Standard Multi-Tenant environments. Those are the record’s reported release months, not evidence of an October 2026 launch or a guaranteed activation date for every tenant. Microsoft cautions that roadmap dates are estimates and subject to change.

What changes for Mac users​

The roadmap describes inline warnings or pop-ups when sensitive content is detected, depending on administrator-configured rules. Microsoft’s Purview reference independently confirms that Outlook for macOS supports policy tips, advanced classifiers and override capabilities.

The useful distinction is between being warned and being permitted to proceed. An override is an organization-defined exception—not a universal “send anyway” button.

Microsoft’s general DLP guidance says override availability is configured per rule. A notification-only rule does not provide an override, even if override options were selected. The rule must combine blocking, notification and permission to override. Administrators can require a business justification or allow users to report a false positive; those responses are logged for reporting.

For employees, the sensible response is to read the warning and resolve the policy conflict where possible. Use an exception only when the displayed options and organizational policy permit it.

The administrator setting that makes tips visible​

Microsoft Learn documents the following enablement path:

1. Open the Microsoft 365 admin center.
2. Expand All Admin Centers and open the Microsoft 365 Apps admin center.
3. Go to Customization and Policy Management.
4. Enable “Enable Purview Data Loss Prevention (DLP) policy tips in Outlook”.
5. Target the policy to the intended individuals or groups.

That targeting supports a controlled pilot. Our deployment recommendation is to test representative messages with approved, nonproduction data before expanding the audience.

Treat the rollout as two separate checks: the Outlook interface must be enabled, and the applicable Purview rule must produce the intended notification and enforcement behavior. If a warning appears without an override, inspect the rule’s blocking and override configuration rather than assuming the client is malfunctioning.

Rule priority deserves attention​

There is another operational wrinkle. Microsoft says that when content matches multiple rules or policies, users see the tip from the most restrictive, highest-priority applicable rule—not a stack of warnings. If that displayed rule permits an override, overriding it also overrides other rules matched by the content.

The practical implication is to test overlapping rules, not merely each rule in isolation. A pilot should establish which warning wins and whether the resulting exception matches the organization’s intent.

Keep the platform boundaries clear​

The Mac reference does not specify a minimum Outlook build or a detailed Mac button sequence. Its separate oversharing-dialog instructions explicitly cover Android and iOS, so they should not be presented as a verified Mac workflow.

The bottom line: this update gives Mac users a supported warning-and-exception experience, but administrators still determine whether it appears and what users may do next. The best rollout is not simply to switch on another alert—it is to make that alert understandable, appropriately restrictive and tested against real organizational rules.