Forum Discussion
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
This situation is unacceptable, and I've already pushed out a rollback to 115.0.1901.203 through group policy. Edge must respect all policy settings for all profiles.
Can I / we have some confirmation whether this is a bug or an intended feature? If it's the latter, I would suggest that Microsoft needs to reassess ASAP.
This situation is unacceptable, and I've already pushed out a rollback to 115.0.1901.203 through group policy. Edge must respect all policy settings for all profiles.
Can I / we have some confirmation whether this is a bug or an intended feature? If it's the latter, I would suggest that Microsoft needs to reassess ASAP.
We've been getting a ton of help desk tickets on this issue. We use Compatibility Mode for a few critical internal applications, and this update has prevented most of my customers from accessing those sites. We've been signing users out as mentioned above and that worked for some, but most of the customers we've had to remove the profile. We didn't realize at the time, but this also removed the customer's Favorites. So now we have upset customers on top of it.
- Kelly_Y
Microsoft
meveritt Just to confirm, this thread is specifically about policy filter issues when a user does not have Microsoft Entra ID login (AAD profile), only a MSA profile. Is this also your scenario?
JayJayDoubleU The team has mentioned they made an update and IE mode policies should start being applied to the MSA profile. This fix should be included in the next Microsoft Edge Stable v116 update.
-Kelly
- Kelly_Y Thank you for your response. Yes, this is about certain administrator-defined policies not being applied on any profile that has a signed-in non-corporate Microsoft account, as described by Gunnar-Haslinger. It actually affects any domain-joined computer, not just AAD-joined.
The upshot is that Edge 116 is pushing consumer-level features at our users, when we have specifically set those to be disabled in group policy. I hope it's obvious that this is unacceptable, and untrustworthy behaviour.
We've already rolled back to 115.0.1901.203, and need to know - actually quite urgently - whether this is a bug or an intended change. As I said previously, if it IS an intended change, I think a) Microsoft ought to reconsider ASAP, and at the very least provide an option to override it; and b) Microsoft ought to be honest about it, because the current assumption in chatter across the Internet at the moment is that it's a bug.
Edge has no future in our organisation if it's going to start ignoring specified policy in order to push consumer features at our users. Hey,
I posted yesterday that it appeared to have been resolved - this appears to only be for Windows 10 devices, not Windows 11
My sample size is pretty small, maybe others can confirm