Forum Discussion
Edge 86.0.622.58 On-premises Sync Not Working Over VPN With Cached Local Login
Microsoftjdbst56 The team has investigated and can see from the feedback report submitted, on MS Edge launch, the user got signed in with the secondary AAD account on the machine.
ConfigureOnPremisesAccountAutoSignIn policy mentions that MS Edge will give preference to AAD accounts over on-premises account.
Enable the use of Active Directory accounts for automatic sign in if your users' machines are Domain Joined and your environment is not hybrid joined.
The behavior currently being experienced is to be expected and the change to use secondary account was made in MS Edge V86.
The current suggestion from the team is to consider removing the secondary AAD account from machine.
To provide a little more information, we are evaluating/investigating creating a new policy so users will not get implicit sign-in with secondary AAD account if ConfigureOnPremisesAccountAutoSignIn is configured.
bin_da - Please take a look at this post and see if it helps your situation as well.
Thanks!
-Kelly
Kelly_Y Do you have any timeframe for this:
"To provide a little more information, we are evaluating/investigating creating a new policy so users will not get implicit sign-in with secondary AAD account if ConfigureOnPremisesAccountAutoSignIn is configured."
- Kelly_Y
benhealy Hello! Sorry, no ETA yet. I can follow up here once we have updates to share.
Is this blocking the adoption or deployment of MS Edge in your organization?
-Kelly
Kelly_Y Yes it is stopping us deploying currently.
Our Windows 10 devices are hybrid joined and our Security/Architecture team are not endorsing cloud sync. As On-Premises sync doesn't work with this setup, if we roll out our users will be forced to export and import their bookmarks whenever they log into a new computer or get re-imaged. Not as user friendly as they are used to with Favourites and folder redirection.
