Issue in Deploying Microsoft Pureview Extension for Chrome from Intune

Question

Issue in Deploying Microsoft Pureview Extension for Chrome from Intune

Singh, Saurabh 0

I am trying to deploy Microsoft Pureview Extension from Intune , and it is going in & Out , although Policy shows that it is deployed but sometimes it is there, after that it is out,

Also one more thing that it is getting replaced by Microsoft Single Sign ON Extension.

The Extension Id that I am using , it is this- echcggldkblhodogklpincgchnpgcdco;https://clients2.google.com/service/update2/crx

When I check in Chrome://policy, it says this- ppnbnpeolgkicgegkbkbjmhlideopiji;https://clients2.google.com/service/update2/crx

although I tried to include both the Extension Ids but nothing worked, any suggetion on this

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2025-10-07T08:49:03.3933333+00:00

Hello Singh,
Just to understand your request, kindly do let me know if this is the correct breakdown.
You're trying to deploy the Microsoft Purview Extension for Chrome via Intune, but it's intermittently disappearing and appears to be replaced by the Microsoft Single Sign-On (SSO) Extension. You’ve also noticed a mismatch between the extension ID you configured (echcggldkblhodogklpincgchnpgcdco) and what shows up in chrome://policy (ppnbnpeolgkicgegkbkbjmhlideopiji).

If this is the Case, it might indicate a Policy Conflict. There may be more than one Configuration Profile Targeting the same Setting. Kindly check this.

Your answer

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2025-10-07T08:49:03.3933333+00:00

Hello Singh,
Just to understand your request, kindly do let me know if this is the correct breakdown.
You're trying to deploy the Microsoft Purview Extension for Chrome via Intune, but it's intermittently disappearing and appears to be replaced by the Microsoft Single Sign-On (SSO) Extension. You’ve also noticed a mismatch between the extension ID you configured (echcggldkblhodogklpincgchnpgcdco) and what shows up in chrome://policy (ppnbnpeolgkicgegkbkbjmhlideopiji).

If this is the Case, it might indicate a Policy Conflict. There may be more than one Configuration Profile Targeting the same Setting. Kindly check this.