Forum Discussion
Windows 10 WIP rules and Chromium Edge cannot access Sharepoint Online ERR_BLOCKED_BY_ADMINISTRATOR
- Hi all,
Got an suggestion from Microsoft Support to change the corporate identity in WIP policy from tenant name to our AD name and it worked!
See below explanation from Microsoft Support.
Resolution: We made a change in the Edge 85-86 to check the domain of the profile's AAD identity instead of automatically treating all AAD identities as a work profile.
In your case, the corporate identity was contoso.onmicrosoft.com, and your Work profile was contoso.com. We confirmed by checking edge://edge-dlp-internals/#NetworkIsolation-policies and seeing EnterpriseNetworkDomainNames we blank. After making the change of the corporate identity to contoso.com, you can now access your SharePoint site.
Björn Lagerwall I seem to be having the same problem when I try to reach an internal resource all of a sudden as well. Could reach it without any issues before using Edge. Have to switch to chorme browser to continue operations.
I'm wondering if this could be caused by some group policy as we just updated the admx files in the central store.
Dadoks Hey,
I have the case up at engineering now and they want me to test more stuff. Hopefully I get time today toi test. I'll post my findings here.
BR
Björn
Björn Lagerwall Please let us know what you results are. I also noticed that the issue seems to be particular to systems that have recieved the Win10 20H2 update. Hope that helps you narrow down and simulate the cause.
Dadoks yeah will post here. Case is still ongoing. Apparently Edge Team and WIP Team now are looking into the issue.
Using an older version of Edge (ver 85 if I recall correctly) it started to work again. But the Edge auto-updated and it stopped once again.
Hopefully, they find it soon, granted complicated issue, bit still a long running case.
- Hi all,
Got an suggestion from Microsoft Support to change the corporate identity in WIP policy from tenant name to our AD name and it worked!
See below explanation from Microsoft Support.
Resolution: We made a change in the Edge 85-86 to check the domain of the profile's AAD identity instead of automatically treating all AAD identities as a work profile.
In your case, the corporate identity was contoso.onmicrosoft.com, and your Work profile was contoso.com. We confirmed by checking edge://edge-dlp-internals/#NetworkIsolation-policies and seeing EnterpriseNetworkDomainNames we blank. After making the change of the corporate identity to contoso.com, you can now access your SharePoint site.