Forum Discussion
Sync isn’t available for this account
- Thanks,
so the problem only happens on Hybrid environments where Edge doesn't use (fails to recognize) the UPN and instead uses the old fashioned down-level logon name (pre-Win 2000 era style).
Irony is that Edge on Windows Server 2019 which is newer uses the old style and on Windows server 2016 which is older uses the new UPN style.
dmutsaers OK, I found the culprit. Somehow the account being used on Windows Server 2019 in the automatically created profile in Microsoft Edge is in the format "DOMAIN\Username", and not the UPN "username@domain.net". When creating a new profile with an username in the UPN format, "username@domain.net", and renaming the default Microsoft Edge profile to "Default.old" and the newly created "Profile 1" to "Default", it works.
Best regards,
Dennis
dmutsaers, if I may ask. Where would you make those profile changes at for Microsoft Edge. I am trying to give the new MS Edge a shot, since it is now built on the same framework as Chrome. I too am experiencing the same issue. DOMAIN\User configured automatically against our MS Server 2019 Standard domain controller. Even though we have an active Office365 licence and Azure AD Sync enabled, I can't get the default "Work" user at DOMAIN\User to sync. I can add a mailto:user@domain.com profile just fine, however now I have two profiles, the "Work" one is the default, and I can not find a way to delete that profile.
lexlodon
Create a new profile in Microsoft Edge, using the correct username in UPN format, i.e. user@domain.com. A new profile directory will be created at "%LOCALAPPDATA%\Microsoft\Edge\User Data\Profile 1". Close Microsoft Edge. Rename "%LOCALAPPDATA%\Microsoft\Edge\User Data\Default" to something else, like "%LOCALAPPDATA%\Microsoft\Edge\User Data\Default.OLD". Rename "%LOCALAPPDATA%\Microsoft\Edge\User Data\Profile 1" to "%LOCALAPPDATA%\Microsoft\Edge\User Data\Default". Open Microsoft Edge and verify the correct username/UPN is being used now. Close Microsoft Edge and delete %LOCALAPPDATA%\Microsoft\Edge\User Data\Default.OLD".
- Yes that is also expected.
what is your config on Windows server 2016? is it an Azure Active directory or Hybrid config?
Edge Chromium, Chrome, Firefox, Opera etc etc, none of the browsers available in the market have the ability to use the local on-premise Active Directory to sync data.
you must be using an online account to get sync and that online account should be either Free Microsoft account OR a work Microsoft account with Enterprise State Roaming
https://docs.microsoft.com/en-us/azure/active-directory/devices/enterprise-state-roaming-enableHotCakeX Same domain, same (hybrid) account, different OS. The problem is that the Microsoft Edge First-run Wizard uses the wrong username (SAM) on Windows Server 2019, where as the same wizard on Windows Server 2016 uses the correct user name (UPN).
Best regards,
Dennis.- Thanks,
so the problem only happens on Hybrid environments where Edge doesn't use (fails to recognize) the UPN and instead uses the old fashioned down-level logon name (pre-Win 2000 era style).
Irony is that Edge on Windows Server 2019 which is newer uses the old style and on Windows server 2016 which is older uses the new UPN style.
