Forum Discussion
Solved
Edge 116 Beta: Policies are blocked if MDM-Managed & Userprofile-Sync personal Account
On most current Edge Beta & DEV Versions there is a NEW BUG regarding accepting the Configuration of "sensitive Policies" which need the device to be Enterprise Managed (AD-Join or MDM-Enrolled). [Ed...
Kelly_Y
Microsoft
MicrosoftGunnar-Haslinger Robert_Holcombe TairikuOkami Thank you for your feedback and reaching out! I've heard an update from the team. In scenarios where there is only a single MSA profile and no work profile configured, policies should not be filtered out. They just made this update, and the change should already be available in Stable 116.
Please test and let us know if you are still having issues. Thanks!
-Kelly
Kelly_Y I can now confirm, that in the "single MSA Profile Sync Szenario" the filtered Edge Policies are now working again on following Versions:
Edge Dev Version 117.0.2045.7
Edge Canary Version 118.0.2057.0
Still unchanged (not working) are those Versions which didn't get an Update so far:
Edge Beta Version 116.0.1938.54
Edge Stable Version 116.0.1938.54
Tested on both OSes: Windows 10 v22H2 as well as Windows 11 v22H2.
Hi there,
we are using w11 23H2 and still have the issue with edge which is not letting to see our portal homepage as default page in Edge, i used the correct policy settings, and when i look in edge it says that homepagelocation is our portal page.........but in Edge (120.0.2210.144) there is no homepage to be found (it didnt worked with the 116.xxx version also).
I've tried several settings according to mannuals, but all got the same result (no homepage in Edge)
any idea's???
- Currently there is no known Issue with Edge v120 regarding Policy HomePageLocation.
So I guess your issue is not related to this Thread.
I suggest to check out edge://Policy for debugging and check if the needed prerequisites (Windows Pro/Enterprise, Managed Device) are fulfilled.
- Kelly_Y
Robert_Holcombe Hey! I don't think there should be a difference between Windows 10 and Windows 11.
Gunnar-Haslinger First, thank you very much for your patience and all the detailed information you always provided! The latest update from the team is that the next Stable v116 release should also include the fix as well. Once it gets deployed, please keep us updated!
-Kelly
- Confirmed that this issue has been resolved in Edge 116.0.1938.62, which has now been released to the Stable channel.
