Edge Sync broken - is https://edge.microsoft.com down

Andrew Macaulay 211 Reputation points
2026-11-11T08:50:17.9633333+00:00

Edge sync when using a Microsoft Account is broken (including latest update 157.0.4341.46): when you close Edge and then go back in, the Profile Sync state gets stuck in "setting up sync" and never completes this stage and never sync's the data.

If you logoff from the account and then reconnect to the account, the sync gets setup correctly, but again fails the next time you close Edge.

This is an issue that has been happening across multiple machines running Windows 11 and multiple Microsoft accounts for probably around a month now. Not tested with Google or Apple accounts. Note that this issue is not occurring on Edge on Android (current version 157.0.4341.42).


I have done the following steps to try to address this issue (when correctly connected and sync'ing). Most of these I'd done previously, but following AI response, also checked a few other things:

  1. Re-sync data, did not help
  2. Reset sync data from Microsoft servers (have disconnected profile everywhere else), did not help
  3. Checked edge://sync-internals/ and sync is enabled, nothing obvious as error
  4. Checked edge://signin-internals/ and no apparent issues there either
  5. Checked edge://policy/ to confirm no policies stopping sync

Then checked the following endpoints, as suggested by the AI response:

  1. [https://edge.microsoft.com] which shows error
       <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mC/0agAAAACaaBKpf8m9TLHwwMctrDZRTE9OMjgxMTgxNzA5MDYwAEVkZ2U=
    
  2. AI also suggested testing the endpoints for https://.cloudmessaging.edge.microsoft.com and wss://.cloudmessaging.edge.microsoft.com but could not work out what exactly to test for these.

Reported through Edge feedback (multiple times) and also on Feedback Hub https://aka.ms/AA145lq8

Microsoft Edge | Profile, sync, and sign in | Windows 11

2 answers

Sort by: Most helpful
  1. TimJellinghaus-1702 0 Reputation points
    2026-11-14T13:37:36.96+00:00

    I'm experiencing the same Microsoft Edge sync issue and have been troubleshooting it extensively for several weeks.

    Affected systems:

    • Multiple Windows 11 PCs and laptops

    Ubuntu Linux

    Edge Stable 157.0.4341.57

    Edge Beta 158.0.4370.16

    Two independent personal Microsoft accounts

    Troubleshooting already performed:

    Recreated Edge profiles multiple times

    Reinstalled and updated Edge

    Tested Edge Beta 158 (same issue)

    Tested different computers and operating systems

    Changed DNS servers to Cloudflare and Google

    Verified DNS resolution, HTTPS connectivity and TCP port 443

    Tested using a separate mobile hotspot

    Disabled browser extensions

    Checked edge://policy (no active restrictions)

    Verified system date, time and time zone

    Confirmed that the correct Microsoft accounts are being used

    Results from edge://sync-internals:

    On the first Microsoft account, sync remains permanently stuck at "Setting up sync".

    Transport State: Initializing
    Auth Error: OK
    MainSyncToken: OK
    KeyDataToken: OK
    MSA Account Key: Success (HTTP 200)
    Sync Engine: ConfigureSyncShareFailed
    Syncer: SyncServerError
    Last Synced: Never
    

    The sync protocol log repeatedly shows:

    Initial GetUpdates (NEW_CLIENT)
    GetUpdates Response: HTTP error (503)
    
    Initial GetUpdates (NEW_CLIENT)
    GetUpdates Response:
    Protocol error (TRANSIENT_ERROR)
    Error description: Server Data Operation Error
    

    On the second Microsoft account, one PC reports that synchronization is active, but bookmark changes are not transferred. Its diagnostics show:

    Transport State: Active
    BlockReason: GlobalBackoff
    Syncer: ServerReturnTransientError
    Download Step Result: TRANSIENT_ERROR
    

    On another laptop using that same account, sync is stuck at "Setting up sync", with MSA Account Key: Fail and Sync Engine: NotStarted.

    Conclusion:

    This does not appear to be an isolated browser profile, device, account or local network issue. The repeated HTTP 503 responses and "Server Data Operation Error" strongly suggest a problem involving the Edge synchronization service, although the root cause has not been officially confirmed.

    I have already submitted a detailed diagnostic report to Microsoft using Edge's built-in Send feedback / Report a problem feature, including the relevant logs.

    As a temporary workaround, I backed up my Edge data locally and restored it on another PC without relying on cloud synchronization.

    Is Microsoft aware of this issue, and is there any confirmed fix or estimated resolution?

    I would appreciate any official update from the Edge team.I'm experiencing the same Microsoft Edge sync issue and have been troubleshooting it extensively for several weeks.

    Affected systems:

    Multiple Windows 11 PCs and laptops

    Ubuntu Linux

    Edge Stable 157.0.4341.57

    Edge Beta 158.0.4370.16

    Two independent personal Microsoft accounts

    Troubleshooting already performed:

    Recreated Edge profiles multiple times

    Reinstalled and updated Edge

    Tested Edge Beta 158 (same issue)

    Tested different computers and operating systems

    Changed DNS servers to Cloudflare and Google

    Verified DNS resolution, HTTPS connectivity and TCP port 443

    Tested using a separate mobile hotspot

    Disabled browser extensions

    Checked edge://policy (no active restrictions)

    Verified system date, time and time zone

    Confirmed that the correct Microsoft accounts are being used

    Results from edge://sync-internals:

    On the first Microsoft account, sync remains permanently stuck at "Setting up sync".

    Transport State: Initializing
    Auth Error: OK
    MainSyncToken: OK
    KeyDataToken: OK
    MSA Account Key: Success (HTTP 200)
    Sync Engine: ConfigureSyncShareFailed
    Syncer: SyncServerError
    Last Synced: Never
    

    The sync protocol log repeatedly shows:

    Initial GetUpdates (NEW_CLIENT)
    GetUpdates Response: HTTP error (503)
    
    Initial GetUpdates (NEW_CLIENT)
    GetUpdates Response:
    Protocol error (TRANSIENT_ERROR)
    Error description: Server Data Operation Error
    

    On the second Microsoft account, one PC reports that synchronization is active, but bookmark changes are not transferred. Its diagnostics show:

    Transport State: Active
    BlockReason: GlobalBackoff
    Syncer: ServerReturnTransientError
    Download Step Result: TRANSIENT_ERROR
    

    On another laptop using that same account, sync is stuck at "Setting up sync", with MSA Account Key: Fail and Sync Engine: NotStarted.

    Conclusion:

    This does not appear to be an isolated browser profile, device, account or local network issue. The repeated HTTP 503 responses and "Server Data Operation Error" strongly suggest a problem involving the Edge synchronization service, although the root cause has not been officially confirmed.

    I have already submitted a detailed diagnostic report to Microsoft using Edge's built-in Send feedback / Report a problem feature, including the relevant logs.

    As a temporary workaround, I backed up my Edge data locally and restored it on another PC without relying on cloud synchronization.

    Is Microsoft aware of this issue, and is there any confirmed fix or estimated resolution?

    I would appreciate any official update from the Edge team.

    Was this answer helpful?


  2. Carl-L 25,175 Reputation points Microsoft External Staff Moderator
    2026-11-12T06:45:35.9633333+00:00

    Hello Andrew Macaulay,

    Welcome to Microsoft Q&A forum.

    This doesn't seem like a normal syncing issue, before we proceed further, can you please try to sign out and sign back in, capture sync-internals at the time. And then close and restart Edge and compare the sync-internals when the issue appears?

    I'm waiting for your reply.

    Was this answer helpful?


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.