Forum Discussion
MS Edge Enterprise Account Syncing
Jordan Paris So it appears that the issue is that it requires AD Premium, in particular - Enterprise State Roaming. I had two tenants, one with, one without. One worked, one didn't. I lit up AD Premium on the onr that didn't and after a little while, I was able to get it going.
We also have some users reporting the sync issue. For example for it looks as follows in edge://sync-internals :
Disable Reasons: Feature not supported.
Sync Client ID: Uninitialized
Invalidator Client ID: Uninitialized
Username: mailto:user@cantonso.com
Requested Toke: n/a
Has token: false
Error Type: DISABLED_BY_ADMIN
Action: STOP_SYNC_FOR_DISABLED_ACCOUNT
Error: Description Microsoft Information Protection service is disabled
Is there any news how to fix it? If there is a fix, is it needed to be fixed per account or per tenant?
Best regards
Johannes
In short, no fix you can do. You have to open a case with MS and they will fix. Two things of importance:
-It's a pain to get through to the right "department" to fix this, and you will have to jump through lots of "restart your router" type troubleshooting.
-You will lose your Edge profile, so make sure you back it up first.
I had a previous Azure AD / AIP subscription and could not get DISABLED_BY_ADMIN to go away, even after a ticket with M365 Support. I was directed to Edge Beta Support, which prompted for a fee. I did a bit more searching and made it to this post and Johannes Goerlich had the answer that solved the problem! I created an account just to like it and to say thank you!
Johannes Goerlich, Thanks, enterprise sync is working with Edge with my account now. I followed the instructions: Sign out, sign in, Sync > reset synced with resume. Rinse and repeat because the first time it failed. Syncing started after the second time, and now syncs to my phone, other computers.
In the meantime we were told to ask the users to sign-out from their work profile on all their devices, sign-in on one device and reset the sync by selecting Settings and more > Sync > Reset sync with Resume sync after resetting to fix this issue.
It seems there is no possibility to determine proactively which users are effected. So we have to wait for every affected one to complain and raise a ticket at our IT support.
tw. it was mentioned by MS that the issue might be fixed with v88 stable, but i couldn't verify, yet.
