05-29-2020 12:09 AM
05-29-2020 12:09 AM
Hello @all, I am currently facing an issue that I couldn't handle by myself.
We are having trouble to enable the (new) Microsoft Edge sync feature for all of our users, when they sign-in to a published desktop/app with Win10 1909 as OS, running on Azure (Windows Virtual Desktop).
When we try to enable the sync by "completing the sign"-in we receive the error "0" or "1067".
Outside of the Win10 machines in Azure the users can sign-in to Edge as expected, e.g. it works in macOS, iOS, Android. Unfortunately we do not have any Win10 Client OnPrem to test this.
Sorry, the screenshots are only available in German, but I think the behaviour should talk for itself.
Does anyone solved the problem or facing the same issue? Any idea?
Thanks in advance!
05-29-2020 12:28 AM
@Sandro Reiter Guten morgen Sandro,
How do users log on to the Windows 10 system? email@example.com?
My guess you have a support agreement with Microsoft because you use Azure, open a ticket!
05-29-2020 03:50 AM
@Henno_Keers Hi Henno, the users AAD Connect synced and sign in with their upn. Ticket at MS support is already created. I didn't know before that signin- and sync-internal URLs are existing :D
We have different issues for different users. But the most I have seen is
|Disable Reasons||Waiting for sync url|
|TokenService Load Status||Load credentials failed with no refresh token for signed in account|
05-29-2020 04:20 AM
@Sandro Reiter In advance of the contact of MS support you will get I suggest that separate "the different issues" and treat them as entirely separate, so gather all relevant data preferable via Kepner & Tregoe situation appraisal and noting everything down in a KT problemsolving template.
when did the issue started (date / time)
Is there a "IS Not"; what system do work but could in potential have the same deviation?
A domain joined real PC would be nice to have as a IS Not (working).