Edge sync isn't available for this account - Error

Hasitha Wickramasinghe 20 Reputation points
2026-06-11T05:43:44.7266667+00:00

User's image

Hi everyone,

I’ve noticed that one user is experiencing issues with Microsoft Edge syncing. Other users within the company have sync enabled and are working correctly.

We tested the affected user account by signing in on a different device and re-registred MFA, but the same issue persists on the 2nd device. This indicates that the problem is not device-related or tenant-wide.

Please advise on the next steps to troubleshoot this user-specific issue.

Microsoft Edge | Profile, sync, and sign in | Windows 11
0 comments No comments

Answer accepted by question author

AI answer

2026-06-11T05:44:02.47+00:00

For a single Microsoft Entra user seeing “Sync isn’t available for this account” while others can sync, troubleshoot in this order as tenant admin:

  1. Confirm licenses
    1. Sign in to the Microsoft 365 admin portal and verify that this user has a valid, supported Microsoft 365/AIP license and that it isn’t expired.
    2. Sign in to the Azure portal and verify that the Azure subscription and user’s Azure license are valid.
  2. Verify Edge sync prerequisites for the tenant
    1. Confirm the tenant has one of the supported subscriptions for Edge enterprise sync as described in Configure Microsoft Edge enterprise sync.
    2. Verify Rights Management Service (RMS) is available and active for the tenant. If needed, activate it by following Activating the protection service from Azure Information Protection.
  3. Check for RMS scoping and IPCv3
    1. Run Get-AIPServiceOnboardingControlPolicy and verify that RMS isn’t scoped in a way that excludes this user. If scoping is enabled, either add the user to the scoped security group or remove the scope using Set-AIPServiceOnboardingControlPolicy.
    2. Run Get-AIPServiceConfiguration and confirm that IPCv3Service is enabled in the tenant.
  4. Enable (or temporarily enable) Enterprise State Roaming (ESR)
    1. If RMS is active and the user still can’t sync, enable Enterprise State Roaming for the tenant as described in Enable Enterprise State Roaming in Microsoft Entra ID.
    2. Test Edge sync for the affected user. If sync starts working, ESR can remain on or be turned off again after confirmation.
  5. Validate Edge and profile configuration on the user’s device
    1. Ensure Edge is at least version 98.0.1108.43.
    2. In Edge, go to Settings > Profiles > Sync and select Re-sync data to this device.
    3. If the issue persists, select Still having sync problems? Try another option and then Reset sync for this profile.
    4. Go to edge://sync-internals and verify in the Summary section that sync is enabled and that no identity error (such as EDGE_AUTH_ERROR) is shown under Credentials.
    5. Go to edge://policy and check whether any applied policy is blocking sync for this user.
  6. If still failing
    1. Confirm again in edge://sync-internals that the status shows DISABLED_BY_ADMIN or similar; if so, the cause is almost always tenant configuration (steps 1–4).
    2. If all checks are correct and the user still cannot sync while others can, collect logs from edge://sync-internals and open a case with Microsoft Edge support.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Hasitha Wickramasinghe 20 Reputation points
    2026-06-23T08:29:12.8933333+00:00

    I have exported all available data from Edeg and reset sync. it worked!!!!

    Was this answer helpful?

    0 comments No comments

  2. Hasitha Wickramasinghe 20 Reputation points
    2026-06-11T06:03:55.2033333+00:00

    Hi Team,

    also, User has Microsoft 365 Business Premium License, and all other users have no issues.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.