Forum Discussion
Copilot or Discover browser extension not working as expected for managed Edge browser
Thanks for your sum up, Peter!
The policy DiscoverPageContextEnabled is being deprecated and will be obsoleted in Edge 127. and two new Edge Policies are taking its place.
Those policies are
CopilotPageContext (Control Copilot access to page contents for AAD profiles), and
CopilotCDPPageContext (Control Copilot with Commerical Data Protection access to page contents for AAD profiles).
The current policy doesn't allow for separate control of Copilot and Copilot with Commercial Data Protection. The new policies allow separate control of these versions of Copilot. The new policies will also allow admins to force-enable Copilot access to Edge page contents by enabling the policy, whereas DiscoverPageContextEnabled only allows force-disabling of Copilot page access.
Hi There, very interesting read up and we are facing exactly this issue as we are currently testing policies and baseline through inune and have noted the copilot is now disabled. I have added the 2 extensions to the allow list but can you describe the process you have used to force the install of these extensions ?
Hi there, apologies for missing this comment. If you still need assistance with the force install process let me know. I'm getting ready to revisit Copilot related settings in Intune to see if we can update the process, we use to deploy Copilot in the browser!
Hi pjv4tx
No thanks, we did eventually managed to solve this issue 👍 thanks for responding 😁
Sure thing. I'm curious if your team ended up using the extension IDs or if you found a cleaner method with more visibility for enforcing/controlling the Copilot related settings. We are still using the extension IDs at my org but I'm revisiting the topic to see if there is a better more modern way to do it now. 😄