Apr 24 2019 11:27 AM
When using Edge Dev Beta in a work environment, if a computer is Azure AD Joined and has Conditional Access policies in place, Edge Dev Beta does not seem to register with the CA system and results in a "not compliant Browser" within the CA system.
Conditional Access Documentation
(https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/)
I'm sure this is related to the fact that it's in Dev Beta but i wanted to point it out early on in the development lifecycle. Just be sure at time of release this is working.
Jun 21 2019 10:37 AM
These Earlier builds might not support some of the more locked down environments. I will pass your concerns to the product team.
Gabriel
Jul 08 2019 07:45 AM
I too have this issue. We just started enabling conditional access for managed devices and laptops. It works great in Chrome with the Chrome extension "Windows 7 Accounts". So I added the extension to Edge. It logs me in without prompts but still prevents me from actions based on the CA rules.
Aug 29 2019 05:43 PM
Aug 30 2019 06:34 AM
@Arunesh_ChandraPlease clarify? Are you saying you have it working and are trying to help us troubleshoot?
I'm on Windows build 18362 and Edge Dev build 78.0.249.1
I'm in a special pilot group testing Conditional Accessing that includes the rules for managed devices, so I'm guessing it's a CA profile. I don't admin the CA's but just work with the team that does.
Remove me from the group testing CA+Managed Devices, New Edge works. Put me back in it, and I get authentication to pass through, but I get the OneDrive and SharePoint warnings there is no download/print options when I'm on certain screens that use it.
Sep 11 2019 03:42 PM
@PeteFromDenver Yes...the NEW Edge supports Conditional Access. You'll need to add your corporate Azure Active Directory (AAD) account to the Edge local profile by going into Edge settings for it to work.