Microsoft Purview Endpoint DLP changes in macOS 27 overview (preview)

Microsoft Purview Endpoint Data Loss Prevention (Endpoint DLP) uses macOS permissions to identify websites, applications, files, and active content involved in user activities. This information helps Endpoint DLP evaluate policies and apply protection actions for activities such as uploading sensitive data to websites and cloud services or copying sensitive content to a browser.

Before macOS 27 (Golden Gate), Endpoint DLP relied on the Accessibility permission for browser and website visibility. In macOS 27, Device Control and Data Access manages this capability. Users can disable this permission after it's deployed through mobile device management (MDM), which can affect Endpoint DLP's ability to get browser and website context. To help maintain data protection coverage, administrators can configure protection modes, monitor permission status, and guide users to restore the required permission when needed.

This article describes the changes introduced in macOS 27, their impact on Endpoint DLP, and how administrators can prepare their organization. Administrators can configure protection modes, monitor affected devices, and validate deployment readiness.

Prerequisites

• Endpoint DLP client version 101.26072 or later.
• Familiarity with onboarding macOS devices into Microsoft Purview.

Permission changes in macOS 27

On macOS 27, Endpoint DLP uses Device Control and Data Access permission to support browser visibility, activity monitoring, and policy enforcement. The permission lets Endpoint DLP identify the active browser, website, application, and file associated with user activity. This context supports policies for activities such as uploading sensitive files and pasting sensitive content into browsers.

In macOS 27, the permission is under Settings > Privacy & Security > Device Control and Data Access. In earlier macOS versions, the permission is under Settings > Privacy & Security > Accessibility.

In some macOS interfaces, management profiles, and diagnostic logs, Microsoft Endpoint DLP might appear as com.microsoft.dlp.daemon.app or com.microsoft.dlp.daemon. These identifiers refer to the Endpoint DLP application.

Behavior when permission is turned off

When Endpoint DLP detects that a user turned off the Microsoft Purview Endpoint DLP permission under Device Control and Data Access, Endpoint DLP can no longer get URL and browser context for Safari, Chrome, and Firefox. Endpoint DLP responds by:

1. Displaying a notification that prompts the user to restore the permission (see the following screenshot).

2. Applying administrator-configured protection settings when browser URL context is unavailable.

Administrators can configure separate protection modes for:

• Uploading sensitive files to websites and cloud services
• Copying sensitive data to a browser

Protection modes

Endpoint DLP provides Enforce, Audit, and Off modes for cloud egress and paste-to-browser activities when the permission is unavailable. The default for both settings is Enforce.

Uploading sensitive files to websites and cloud services

Setting name: Restricted protection mode for cloud egress

This setting controls how Endpoint DLP handles uploads of sensitive files when browser and website context are unavailable.

• Enforce: Applies upload protection. Endpoint DLP treats supported non-Edge browsers, such as Safari, Chrome, and Firefox, as restricted destinations and enforces the most restrictive applicable policy action.
• Audit: Records and monitors the condition without enforcing upload restrictions.
• Off: Doesn't apply permission-related upload protection.

Copying sensitive data to a browser

Setting name: Restricted protection mode for paste to browse

This setting controls how Endpoint DLP handles copy-and-paste activities into browsers when browser and website context are unavailable.

• Enforce: Applies policy actions, such as block or warn.
• Audit: Records events without enforcing restrictions.
• Off: Doesn't apply permission-related browser copy-and-paste protection.

Permission notification

Setting name: Permission notification (notification)

Endpoint DLP can notify users when the permission is turned off. The notification explains why permission is required and prompts the user to restore access. Administrators can customize the notification message.

The profile settings map to the following configuration keys:

The following source fragment sets both protection modes to Enforce:

 <key>accessibility</key>
                    <dict>
                        <key>enforcement</key>
                        <dict>
                            <key>unallowedBrowserMode</key>
                            <string>enforce</string>
                            <key>pasteToBrowserMode</key>
                            <string>enforce</string>
                        </dict>
                        <key>notification</key>
                        <dict>
                            <key>Microsoft Endpoint DLP will report this device as non-compliant. Additional restrictions will be in effect until Accessibility has been re-enabled for Microsoft Endpoint DLP</key>
                            <string/>
                        </dict>
                    </dict>

MDM configuration options

Microsoft provides configuration samples for Microsoft Intune and Jamf Pro. These options configure the protection modes and the message that prompts users to turn on the permission.

• Microsoft Intune: Use the sample com.microsoft.wdav.mobileconfig configuration profile as the starting point for deployment.
• Jamf Pro with schema.json: Update the existing Microsoft Defender for Endpoint preferences configuration profile to use the latest schema.json. The configuration is under Data Loss Prevention > Accessibility.
• Jamf Pro with a property list: Use the sample com.microsoft.wdav.plist.

Audit mode

Audit mode lets administrators assess the effect of unavailable permissions before they enable enforcement. Endpoint DLP continues to detect when the permission is turned off and can notify users to restore access, but it doesn't apply the additional restricted protection behavior for cloud egress or paste-to-browser activities.

Audit mode can reduce user disruption while administrators identify affected devices. During this assessment, controls that would normally apply when browser context is unavailable aren't enforced. This condition can leave a temporary protection gap until the permission is restored or enforcement is enabled.

The following source fragment sets both protection modes to Audit:

<key>accessibility</key>
                    <dict>
                        <key>enforcement</key>
                        <dict>
                            <key>unallowedBrowserMode</key>
                            <string>audit</string>
                            <key>pasteToBrowserMode</key>
                            <string>audit</string>
                        </dict>
                        <key>notification</key>
                        <dict>
                            <key>Microsoft Endpoint DLP will report this device as non-compliant. Additional restrictions will be in effect until Accessibility has been re-enabled for Microsoft Endpoint DLP</key>
                            <string/>
                        </dict>
                    </dict>

Permission monitoring

Monitor Endpoint DLP permission status in Microsoft Purview. The device details pane shows the Accessibility configuration status for an onboarded macOS device. A status of Installed indicates the required permission is configured, while Not updated indicates the permission isn't available to Endpoint DLP and requires administrator attention. See the following screenshot examples.

Administrator readiness

Preparing Endpoint DLP for macOS 27 includes the following activities:

1. Review the updated macOS deployment guidance for Endpoint DLP.
2. Deploy or validate the required Endpoint DLP permission configuration on managed macOS devices.
3. Upgrade to Endpoint DLP client version 101.26072 or later.
4. Monitor the Device Onboarding page for devices that report the permission as off.
5. Configure user notifications and educate users to restore the permission if it's turned off.

Related content

• Onboard macOS devices into Microsoft 365 overview
• Get started with Endpoint data loss prevention
• Learn about Endpoint data loss prevention