SOLVED

Sync isn’t available for this account

%3CLINGO-SUB%20id%3D%22lingo-sub-1175942%22%20slang%3D%22en-US%22%3ESync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1175942%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20I%20have%20a%20strange%20issue%20with%20Microsoft%20Edge%26nbsp%3B%3CSPAN%3E80.0.361.54.%20I%20get%20an%20error%2C%20%22Sync%20isn%E2%80%99t%20available%20for%20this%20account.%22%20when%20using%20my%20work%20account%20on%20my%20Windows%20Server%202019%20servers%2C%20but%20using%20the%20same%20account%20on%20my%20Windows%20Server%202016%20servers%20sync%20is%20available.%20So%20what%20is%20it%3F%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2C%3CBR%20%2F%3EDennis.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1175956%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1175956%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3Ewhat%20you%20are%20experiencing%20is%20normal.%3CBR%20%2F%3ESync%20is%20only%20available%20for%20free%20Microsoft%20accounts%20and%20Azure%20active%20directory%20accounts%20which%20include%20Office%20365%20and%20Microsoft%20365%20subscriptions.%3CBR%20%2F%3EWindows%20Server%20on-premise%20Can't%20provide%20syncing%20functionality%20for%20the%20Chromium%20based%20Edge.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1175990%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1175990%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BBut%20it%20DOES%20work%20on%20Windows%20Server%202016%20while%20it%20does%20not%20on%20Windows%20Server%202019%3F%20(and%20an%20Office%20365%20subscription%20has%20been%20added%20to%20the%20account)%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2C%3CBR%20%2F%3EDennis.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1175993%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1175993%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F401014%22%20target%3D%22_blank%22%3E%40dmutsaers%3C%2FA%3E%26nbsp%3BOK%2C%20I%20found%20the%20culprit.%20Somehow%20the%20account%20being%20used%20on%20Windows%20Server%202019%20in%20the%20automatically%20created%20profile%20in%20Microsoft%20Edge%20is%20in%20the%20format%20%22DOMAIN%5CUsername%22%2C%20and%20not%20the%20UPN%20%22username%40domain.net%22.%20When%20creating%20a%20new%20profile%20with%20an%20username%20in%20the%20UPN%20format%2C%26nbsp%3B%22username%40domain.net%22%2C%20and%20renaming%20the%20default%20Microsoft%20Edge%20profile%20to%20%22Default.old%22%20and%20the%20newly%20created%20%22Profile%201%22%20to%20%22Default%22%2C%20it%20works.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2C%3CBR%20%2F%3EDennis%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1176044%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1176044%22%20slang%3D%22en-US%22%3EYes%20that%20is%20also%20expected.%3CBR%20%2F%3Ewhat%20is%20your%20config%20on%20Windows%20server%202016%3F%20is%20it%20an%20Azure%20Active%20directory%20or%20Hybrid%20config%3F%3CBR%20%2F%3E%3CBR%20%2F%3EEdge%20Chromium%2C%20Chrome%2C%20Firefox%2C%20Opera%20etc%20etc%2C%20none%20of%20the%20browsers%20available%20in%20the%20market%20have%20the%20ability%20to%20use%20the%20local%20on-premise%20Active%20Directory%20to%20sync%20data.%3CBR%20%2F%3E%3CBR%20%2F%3Eyou%20must%20be%20using%20an%20online%20account%20to%20get%20sync%20and%20that%20online%20account%20should%20be%20either%20Free%20Microsoft%20account%20OR%20a%20work%20Microsoft%20account%20with%20Enterprise%20State%20Roaming%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fenterprise-state-roaming-enable%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fenterprise-state-roaming-enable%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177358%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177358%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BSame%20domain%2C%20same%20(hybrid)%20account%2C%20different%20OS.%20The%20problem%20is%20that%20the%20Microsoft%20Edge%20First-run%20Wizard%20uses%20the%20wrong%20username%20(SAM)%20on%20Windows%20Server%202019%2C%20where%20as%20the%20same%20wizard%20on%20Windows%20Server%202016%20uses%20the%20correct%20user%20name%20(UPN).%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2C%3CBR%20%2F%3EDennis.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177653%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177653%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F401014%22%20target%3D%22_blank%22%3E%40dmutsaers%3C%2FA%3E%26nbsp%3Bwe%20have%20found%20a%20kind%20of%20same%20experience%20on%20clients%3A%3C%2FP%3E%3CP%3E*%20Windows%207%20login%20with%20staff%5Cuser%20will%20translate%20to%20login%20in%20with%20upn%3B%20%3CA%20href%3D%22mailto%3Auser%40han.nl%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser%40han.nl.%3C%2FA%3E%3C%2FP%3E%3CP%3E*%20Windows%2010%201803%20with%20upn%20will%20translate%20to%20login%20in%20staff%5Cuser%20and%20failure%20to%20sync.%3C%2FP%3E%3CP%3E*%20Windows%20server%202016%20with%20login%20staff%5Cuser%20logs%20on%20automatically%20with%20%3CA%20href%3D%22mailto%3Auser%40han.nl%2C%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser%40han.nl%2C%3C%2FA%3E%26nbsp%3Bonly%20enabling%20sync%20is%20needed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ereg%2C%20Henno.%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1181688%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1181688%22%20slang%3D%22en-US%22%3EThanks%2C%3CBR%20%2F%3Eso%20the%20problem%20only%20happens%20on%20Hybrid%20environments%20where%20Edge%20doesn't%20use%20(fails%20to%20recognize)%20the%20UPN%20and%20instead%20uses%20the%20old%20fashioned%20down-level%20logon%20name%20(pre-Win%202000%20era%20style).%3CBR%20%2F%3E%3CBR%20%2F%3EIrony%20is%20that%20Edge%20on%20Windows%20Server%202019%20which%20is%20newer%20uses%20the%20old%20style%20and%20on%20Windows%20server%202016%20which%20is%20older%20uses%20the%20new%20UPN%20style.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1202554%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1202554%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F401014%22%20target%3D%22_blank%22%3E%40dmutsaers%3C%2FA%3E%2C%20if%20I%20may%20ask.%20Where%20would%20you%20make%20those%20profile%20changes%20at%20for%20Microsoft%20Edge.%20I%20am%20trying%20to%20give%20the%20new%20MS%20Edge%20a%20shot%2C%20since%20it%20is%20now%20built%20on%20the%20same%20framework%20as%20Chrome.%20I%20too%20am%20experiencing%20the%20same%20issue.%20DOMAIN%5CUser%20configured%20automatically%20against%20our%20MS%20Server%202019%20Standard%20domain%20controller.%20Even%20though%20we%20have%20an%20active%20Office365%20licence%20and%20Azure%20AD%20Sync%20enabled%2C%20I%20can't%20get%20the%20default%20%22Work%22%20user%20at%20DOMAIN%5CUser%20to%20sync.%20I%20can%20add%20a%20%3CA%20href%3D%22mailto%3Auser%40domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser%40domain.com%3C%2FA%3E%26nbsp%3Bprofile%20just%20fine%2C%20however%20now%20I%20have%20two%20profiles%2C%20the%20%22Work%22%20one%20is%20the%20default%2C%20and%20I%20can%20not%20find%20a%20way%20to%20delete%20that%20profile.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1226264%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1226264%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20updates%20on%20this%3F%26nbsp%3B%20I%20want%20to%20start%20rolling%20out%20Edge%20for%20my%20Windows%2010%20clients%20in%20our%20hybrid%20environment%2C%20but%20this%20annoying%20UPN%20issue%20is%20preventing%20this.%26nbsp%3B%20Any%20workarounds%20known%3F%20(without%20creating%2Fdeleting%20profiles)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262124%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262124%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F571334%22%20target%3D%22_blank%22%3E%40lexlodon%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ECreate%20a%20new%20profile%20in%20Microsoft%20Edge%20with%20the%20correct%20UPN%2C%20i.e.%20%3CA%20href%3D%22mailto%3Auser%40domain.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Euser%40domain.com%3C%2FA%3E.%20A%20new%20profile%20directory%20will%20be%20created%20at%20%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CProfile%201%22.%20Close%20Microsoft%20Edge.%20Rename%20%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault%22%20to%20something%20else%2C%20like%20%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault.OLD%22.%20Rename%20%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CProfile%201%22%20to%20%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault%22.%20Start%20Microsoft%20edge%20and%20verify%20that%20Microsoft%20Edge%20now%20uses%20the%20correct%20username%2FUPN.%20Close%20Microsoft%20Edge.%20Delete%26nbsp%3B%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault.OLD%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262131%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262131%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F571334%22%20target%3D%22_blank%22%3E%40lexlodon%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ECreate%20a%20new%20profile%20in%20Microsoft%20Edge%2C%20using%20the%20correct%20username%20in%20UPN%20format%2C%20i.e.%20user%40domain.com.%20A%20new%20profile%20directory%20will%20be%20created%20at%26nbsp%3B%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CProfile%201%22.%20Close%20Microsoft%20Edge.%20Rename%20%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault%22%20to%20something%20else%2C%20like%26nbsp%3B%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault.OLD%22.%20Rename%26nbsp%3B%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CProfile%201%22%20to%26nbsp%3B%22%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault%22.%20Open%20Microsoft%20Edge%20and%20verify%20the%20correct%20username%2FUPN%20is%20being%20used%20now.%20Close%20Microsoft%20Edge%20and%20delete%26nbsp%3B%25LOCALAPPDATA%25%5CMicrosoft%5CEdge%5CUser%20Data%5CDefault.OLD%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1266297%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20isn%E2%80%99t%20available%20for%20this%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1266297%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3Bis%20there%20any%20way%20to%20modify%20an%20existing%26nbsp%3BDOMAIN%5CUser%20profile%20to%20a%26nbsp%3Bcorrect%20UPN%2C%20i.e.%20%3CA%20href%3D%22mailto%3Auser%40domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser%40domain.com%3C%2FA%3E%26nbsp%3Bprofile%3F%20Adding%20a%20new%20profile%2C%20renaming%20the%20old%20profile%2C%20and%20replacing%20the%20new%20profile%20with%20the%20old%20one%20as%20suggested%20below%20does%20not%20help%20that%20fact%20that%20I%20have%20setup%20my%20local%20Edge%20profile%20on%20my%20laptop%20with%20both%20my%20existing%20Chrome%20and%20Firefox%20favorites%20already.%20I%20was%20hoping%20to%20not%20have%20to%20start%20from%20scratch%20again.%20It%20would%20also%20be%20a%20great%20feature%20to%20simply%20export%20the%20data%20from%20a%20profile%20to%20make%20future%20issues%20like%20this%20easier%20to%20resolve.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I think I have a strange issue with Microsoft Edge 80.0.361.54. I get an error, "Sync isn’t available for this account." when using my work account on my Windows Server 2019 servers, but using the same account on my Windows Server 2016 servers sync is available. So what is it? :)

Best regards,
Dennis.

11 Replies
Hi,
what you are experiencing is normal.
Sync is only available for free Microsoft accounts and Azure active directory accounts which include Office 365 and Microsoft 365 subscriptions.
Windows Server on-premise Can't provide syncing functionality for the Chromium based Edge.

@HotCakeX But it DOES work on Windows Server 2016 while it does not on Windows Server 2019? (and an Office 365 subscription has been added to the account)

Best regards,
Dennis.

@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

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-enable

@HotCakeX 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.

@dmutsaers we have found a kind of same experience on clients:

* Windows 7 login with staff\user will translate to login in with upn; user@han.nl.

* Windows 10 1803 with upn will translate to login in staff\user and failure to sync.

* Windows server 2016 with login staff\user logs on automatically with user@han.nl, only enabling sync is needed.

 

reg, Henno.

  

Best Response confirmed by dmutsaers (Contributor)
Solution
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, 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 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.

Any updates on this?  I want to start rolling out Edge for my Windows 10 clients in our hybrid environment, but this annoying UPN issue is preventing this.  Any workarounds known? (without creating/deleting profiles)

@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".

@HotCakeX is there any way to modify an existing DOMAIN\User profile to a correct UPN, i.e. user@domain.com profile? Adding a new profile, renaming the old profile, and replacing the new profile with the old one as suggested below does not help that fact that I have setup my local Edge profile on my laptop with both my existing Chrome and Firefox favorites already. I was hoping to not have to start from scratch again. It would also be a great feature to simply export the data from a profile to make future issues like this easier to resolve.