08-15-2017 09:14 AM
08-15-2017 09:14 AM
Is any work being done to suport Office 365 Passthrough Authentication SSO with Edge? It is still not supported while Chrome, IE and Firefox are. This is a bummer for Orgs deploying Win10.
08-15-2017 09:24 AM
08-15-2017 09:40 AM
08-16-2017 07:47 AM - edited 08-16-2017 07:49 AM
@Matthew McDermottit should work, you need to be Azure AD Joined, which is different than domain joined.
08-16-2017 08:00 AM
Right, my clients are Domain Joined...so it does not work. It appears in a recent update they tried to make it work, but, as the note says, Edge support has been removed while they investigate.
08-16-2017 08:28 AM
I must be blind, i'm not seeing any note about Edge support being removed.
Domain Joined devices can be Registered with Azure AD, see https://docs.microsoft.com/en-us/azure/active-directory/active-directory-azureadjoin-devices-group-p...
03-02-2018 06:13 AM
03-19-2018 05:17 AM
It appears to be working for me. I have AD Connect with SSO configured on an on-premise AD server (2012R2) and that is syncing with an Office 365 tenancy (Education). I have a Win10 Education (1709) virtual machine (VM) which is joined AND registered in the Azure AD of the Office 365 tenancy via AD Connect. The join appears to take place once the Win10 VM has joined the local AD domain, made some sort of connection (or attempted) to an Office 365 login URL, and an AD Connect sync cycle has run. No particular user needs to be logged in to the Win10 VM for that to happen. Registration appears to happen once the Win10 VM has made some sort of connection (or attempted) to an Office 365 login URL while a domain user is logged in that is having their account synced with Azure AD via AD Connect, and an AD Connect sync cycle has run. DSRegCmd.exe is a useful command to run on the Win10 client to check if join and registration is successful, besides seeing what has appeared in your Devices area in the Azure AD admin console. WamDefaultSet=Yes seems to be the value you need to see via DsRegCmd to know that registration is successful.
Once the Win10 client has registered successfully, I am finding that opening Edge and going to portal.office.com results in that user being signed in without the need to enter a username or password. I also see that the account is shown in the settings area in Edge. And once the registration has been successful for the Win10 client, any subsequent user logging on to that computer will also experience this Seamless Single Sign-on to Office 365, using Edge or IE. Chrome seems to always prompt for a username.
I'd be interested to know if anyone else is getting this to work, as my testing is fairly limited: a single tenancy and local AD, a couple of Win10 VMs and a few users. And I know it shouldn't work according to Microsoft.
03-21-2018 03:08 PM
Yours works because you have registered your workstations with Azure and your using ad connect not Azure AD Connect. They are two different software products.
03-26-2018 06:19 AM
Believe or not believe, still Microsoft did not solve this issue? Is from last year. I was interested in implement Seamless SSO but is not support Edge this is a problem.
06-06-2018 03:06 AM
no edge is not yet supported.
The first time you launch edge, it ask for login and password. For next time, maybe, edge can remeber but it is not supported like IE
11-29-2018 08:35 AM
Just confirming that for me at least, if the device is Azure AD Registered, you get SSO with Edge. If not, it will ask for password. I've also experienced that the device was Azure AD Registered but still no SSO and when starting Outlook it wanted me to confirm the Azure AD Registration so it could be that it suddenly lost the registration and therefore not giving SSO because once confirming the registration I got SSO again.
I also assume that Hybrid Azure AD joined will give an SSO experience with Edge. I will try this and report back here.
But of course, best would be to also let Edge have SSO support. Don't know what is taking... Even though we see most customers running hybrid with Azure AD Connect also have their devices Azure AD Registered or Hybrid Azure AD joined. Some problem for downlevel clients but we more or less say that you need Windows 10 for the best experience in Microsoft Cloud...
03-11-2019 02:40 AM
I find it incredible that its March 2019 and still no AAD Seamless SSO for Edge without having to have your Win 10 machine AAD joined!
Can anyone at Microsoft (or otherwise) shed any light on why this is the case?
Some further questions/comments:
- MS documentation talks about machines being AAD joined but also Hybrid AAD joined (where the win 10 machine is also AD joined). I can't immediately tell if a win 10 machine that is already AD joined can then be AAD joined WITHOUT it them being considered to be "Hybrid AAD joined". Hybrid AAD joined has some potential repercussions for us and it would be good to clearly understand if a machine can be AD and AAD joined simultaneously without it being Hybrid AAD joined (along with all the AAD Connect and computer object sync that goes with that concept).
- With respect to Edge moving to using the chromium engine: Is there any hint that AAD Seamless SSO may make an appearance with that change, to match the fact that Chrome can undertake AAD Seamless SSO? (something that seems "challenging" to MS for their own browser)
The lack of AAD Seamless SSO support for Edge is another nail in the coffin for Edge being considered by us as our default browser moving forward.....
05-24-2019 06:47 AM
Just want to leave a quick note for anyone looking at this thread and mistakenly thinks that the topic is applicable to Orgs that are using federated SSO with AD FS. SSO in Edge works for us, running AD FS v.3 on 2012R2. For a long time we thought that SSO was not supported with AD FS on Edge, especially when it failed after we added "Edge/12" to supported UA strings. Finally, after adding "Mozilla/5.0", the SSO for both Edge and Chrome started to work. This was a major improvement as our users were previously stuck with IE and its horrific SharePoint performance.