Microsoft Purview Compliance Extension for Edge browser

Nancy Daniel 40 Reputation points
2026-10-12T13:04:12.2133333+00:00

Hello Microsoft Support,

As part of our Microsoft Purview DSPM for AI onboarding and readiness activities, we are currently validating the prerequisites related to the Microsoft Purview / Microsoft Compliance Extension for browser signal detection, Insider Risk Management, and DSPM for AI monitoring capabilities.

While reviewing the Microsoft Learn documentation, we identified the documented Microsoft Edge extension ID: lcmcgbabdcbngcbcfabdncmoppkajglo

However, when navigating to the corresponding Edge Add-ons page, we are presented with a warning message stating:

"This extension no longer meets Microsoft Edge standards and may be removed soon."

Could you please help us clarify the following:

  1. Is this warning expected for the extension currently documented in Microsoft Learn?
  2. Is the extension still supported and recommended for DSPM for AI, Insider Risk Management browser signal detection, and related Microsoft Purview scenarios?
  3. Has the extension been replaced by a newer extension, browser integration, or deployment method?
  4. Can you provide the current official Microsoft link for the supported Edge extension (if different from the one referenced in the documentation)?
  5. Are there any additional deployment considerations for customers implementing DSPM for AI browser signal detection in production environments?

Thank you for your assistance.

Kind regards,

Nancy Daniel

Microsoft Security | Microsoft Purview

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Maksood Ahmed 195 Reputation points Microsoft External Staff Moderator
    2026-10-13T14:56:13.0233333+00:00

    Hi @Nancy Daniel ,

    Thank you for clarifying your concern. Please find the answers to your questions below.

    1. Can the Edge warning be safely ignored?
      The current Microsoft documentation does not confirm that this warning can be safely ignored. Therefore, we cannot recommend ignoring it for a production deployment without confirmation from the product team.
    2. Is the Microsoft Compliance Extension still supported?
      The extension is still referenced in the current Microsoft Purview documentation for applicable browser signal detection scenarios. Microsoft documentation continues to describe its use for certain Insider Risk Management scenarios in Edge.
    3. Will DSPM for AI and Insider Risk Management telemetry continue through this extension?
      Currently, some Edge signals are handled natively, while other signals still depend on the extension. However, the public documentation does not provide a long-term commitment regarding future telemetry availability through this extension.
    4. Is there a replacement or successor for the extension?
      At this time, I could not find current Microsoft documentation identifying another extension as a complete replacement for all existing extension-based Insider Risk Management scenarios.

    Since you are planning a production deployment and need confirmation about long-term support, telemetry availability, and replacement plans, I recommend opening a Microsoft Support request so the appropriate Microsoft Purview/Edge product team can provide an authoritative confirmation.

    FYR:

    Insider Risk Management browser signal detection

    Microsoft Purview for other AI apps

    Regards,

    Maksood

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-10-12T13:04:32.7633333+00:00

    Based on the available documentation, the extension is still part of the supported prerequisites for Microsoft Purview scenarios, but the documentation provided here does not confirm the Edge Add-ons warning message or whether that specific Edge add-on entry has been replaced.

    Supported facts:

    1. For Insider Risk Management browser signal detection on Edge, devices must meet these requirements:
      • Windows only; browser signal detection is not currently supported on non-Windows devices.
      • Latest Windows 10 x64 is recommended, with minimum Windows 10 x64 build 1809.
      • A current Microsoft 365 subscription with Insider Risk Management support.
      • Devices must be onboarded to Microsoft Purview.
      • For policies based on the Risky browser usage template, at least one Browsing indicator must be selected in Insider Risk Management > Settings > Policy indicators.
    2. For DSPM for AI and related monitoring of third-party generative AI sites:
      • Devices must be onboarded to Microsoft Purview.
      • The Microsoft Purview browser extension is required to discover visits to third-party generative AI sites by using an Insider Risk Management policy.
      • The browser extension is also required for Endpoint DLP policies on Windows when using Chrome.
      • For monitoring interactions and applying DLP policies to other AI apps in Edge, an Edge configuration policy is required to activate the Microsoft Purview integration in Edge.
    3. For Risky AI usage in Insider Risk Management:
      • The documented guidance states that the Microsoft Insider risk extension on Microsoft Edge, or the Microsoft Purview extension on Chrome, must be configured on user devices.
    4. For production validation of Edge deployment:
      • In Edge, open edge://extensions and check whether the extension shows the briefcase logo, which indicates it is managed by organization policy.
      • Open edge://policy and review extension-related policies such as ExtensionSettings or ExtensionInstallForcelist.

    What cannot be confirmed from the available documentation:

    • Whether the warning "This extension no longer meets Microsoft Edge standards and may be removed soon" is expected for the currently documented extension.
    • Whether the documented Edge extension ID has been replaced by a newer extension.
    • A newer official Edge add-on link, if one exists.

    For the deployment considerations that are supported by the documentation, validate these items before production rollout:

    1. Confirm all in-scope devices are Windows and meet the minimum supported build.
    2. Confirm devices are onboarded to Microsoft Purview.
    3. For Edge scenarios, confirm the required Edge configuration policy is deployed to activate the Purview integration.
    4. For Insider Risk Management policies using browser signals, confirm the needed Browsing indicators are enabled.
    5. Verify on a client with edge://extensions and edge://policy that the extension and related policies are actually applied.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?