Forum Discussion
Possible bug - unable to disable Sidebar/Discover in Edge 111.0.1661.44
Hello, I am evaluating the new features in Edge 111 Stable for deployment. I have the HubsSidebarEnabled policy set to 0 (Recommended). However, the Discover icon still shows prominently at the to...
Kelly_Y
Microsoft
MicrosoftAndrewSAIF Hi! In Microsoft Edge v111, Admins do not have the ability to disable Discover and keep the Sidebar.
I've spoken to the team and they have confirmed your findings. In v111, if the HubsSidebarEnabled policy is set as disabled with Recommended level, the settings page shows gray out where users can not toggle on to show sidebar (this is same as previous Microsoft Edge version), users can still get back sidebar by hover/click the Bing icon in the toolbar.
If Admin disabled HubsSidebarEnabled policy with Mandatory level, both sidebar and the Bing icon in the toolbar will be invisible (users cannot get back sidebar).
There are additional improvements planned for v112, additional information can be found in Release Notes: Microsoft Edge release notes for Beta Channel | Microsoft Learn. Thanks!
-Kelly
Kelly_Y
Hi Kelly,
This slider seems to work as intended for me with the Recommended policy in Edge v110, which I have deployed currently -
It's only in 111 that I notice the slider is broken with this same policy.
In the description for beta 112, it mentions that admins will be able to disable Sidebar and Discover separately, but it doesn't appear to mention any new policies that would allow this. Will there be new policies added to Stable to independently control Discover?
Not sure if my feedback is important here, but I would rather disable the sidebar/discover features entirely than have them behave in an unpredictable manner when I disable them as recommended. My goal is to avoid unnecessary calls to the service desk. I'd like to leave these features accessible to users, and I'm sure you'd like users to adopt these new features as well. But if this is how it is implemented, I'm probably going to disable it as mandatory and only revisit this policy if I get an overwhelming number of user requests.
Thanks for the response,
Andrew