Share via

GraphAPI for Purview Data Loss Prevention Policies

Nam Nguyen 20 Reputation points
2026-03-27T03:14:03.1033333+00:00

Hi everyone,

I am looking for the correct Microsoft Graph API endpoint to retrieve policies from Microsoft Purview Data Loss Prevention (DLP).

I previously used the following beta endpoint: GET https://graph.microsoft.com/beta/security/dataLossPrevention/policies

However, this no longer seems to be returning an error. Has this endpoint been deprecated, moved to a different path, or is there a new replacement?

Any guidance or updated documentation links would be greatly appreciated. Thanks!

Microsoft Security | Microsoft Defender | Microsoft Defender for Cloud Apps
0 comments No comments

Answer accepted by question author
  1. Catherine Kyalo 3,085 Reputation points Microsoft Employee
    2026-03-27T15:56:08.09+00:00

    Hi Nam Nguyen

    1. APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported.
    2. Based on my research, DLP policy management remains in the Purview portal, while supported APIs focus on policy evaluation and enforcement (for example, retrieving DLP audit events). Refer: https://learn.microsoft.com/en-us/graph/api/resources/security-api-overview?view=graph-rest-beta#audit-logs-query-preview

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-27T03:14:25.3+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The Microsoft Graph endpoint GET https://graph.microsoft.com/beta/security/dataLossPrevention/policies is not documented in the current Microsoft Graph security or Microsoft Purview data security and governance API surface and should be treated as deprecated/unsupported.

    For working with Microsoft Purview Data Loss Prevention (DLP) today, the supported approach is:

    1. Use Microsoft Purview itself (via the Microsoft Purview compliance/administration portals) to define and manage DLP policies.
    2. For application integration, use the Microsoft Purview data security and governance APIs, which expose Purview’s policy evaluation engine rather than raw DLP policy objects.
      • These APIs allow applications to:
        • Retrieve the protection scope for a user or tenant.
        • Send user content to Microsoft Purview for processing.
        • Determine at runtime whether user activity should be allowed or restricted based on configured policies.
      • Policy enforcement depends on configured Collection Policies and Data Loss Prevention (DLP) Policies in Purview. If these are not configured for a user/tenant, the protection-scope and process-content APIs will return empty scopes or no DLP actions.

    Because the current documentation only describes policy evaluation and enforcement flows (for example, via userProtectionScopeContainer-compute and related process-content APIs) and does not expose a supported Graph resource for listing DLP policies, there is no documented replacement Graph endpoint for .../security/dataLossPrevention/policies in the provided material.

    For scenarios such as:

    • Determining what protections apply to a user or tenant: use the Compute protection scopes API as documented under Microsoft Purview data security and governance APIs.
    • Enforcing DLP decisions in custom apps: send content to Purview for processing and act on the returned DLP actions.

    Management of the DLP policies themselves remains in the Purview portals rather than through a documented Microsoft Graph policy-listing endpoint in the referenced documentation.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.