[RESOLVED] Microsoft Edge Sync Endpoints Blocked

[gyCfjSnO]

These endpoints manage the reading and writing of synced data, rights management for secure data, and notifying the browser when new sync data is available.

Edge sync service endpoints:

https://edge-enterprise.activity.windows.com https://edge.activity.windows.com

These need to be removed from block list or else the above cannot function correctly.

Source: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-security-endpoints Source 2: My Edge browser has stopped Syncing since adding this blocklist as the domains are on your blocklist.

[bongochong]

Thank you for bringing this to my attention! I checked the documentation you referenced, and have remedied this issue across the board via commit 94bfd52. The two domains will be excluded from all other lists in a matter of minutes.

[bongochong]

P.S. I should also note that I have found neither of those domains (nor the other service-related ones mentioned in the documentation) on any of my block lists, so it is possible that you are using a very old version of one of my lists, or the blocks are coming from another source. Either way, they've been whitelisted across the board as of 16 minutes ago.

[gyCfjSnO]

P.S. I should also note that I have found neither of those domains (nor the other service-related ones mentioned in the documentation) on any of my block lists, so it is possible that you are using a very old version of one of my lists, or the blocks are coming from another source. Either way, they've been whitelisted across the board as of 16 minutes ago.

I checked AdGuard Home and the URL is https://raw.githubusercontent.com/bongochong/CombinedPrivacyBlockLists/master/cpbl-abp-list.txt and the last update time listed against it is 21 October 2021, 22:41

Screenshot of the domain and filter list it is blocked on:

[bongochong]

OK, I see. That's a different story. I try to stay on top of compatibility with AdGuard Home, though my ABP/uBO filter lists (as opposed to my hosts lists and others) are mostly meant for in-browser ad-blocking extensions, as they're compressed in a sense, to take advantage of wildcard matching in many popular ad-blocking extensions, AdGuard included. What I will do shortly though, is add exceptions for edge.activity.windows.com in particular, to those lists from now. Give me a few minutes.

[bongochong]

Alright, this should be completely resolved for users of AdGuard Home (and other system/network-wide AdGuard solutions) with this commit ed29b7a. Please update and let me know how it goes!

By the way, I used app identifier and domain exceptions instead, as follows: ||activity.windows.com^$domain=~microsoft.com|~windows.com,app=~MicrosoftEdge.exe|~MicrosoftEdgeCP.exe|~MicrosoftEdgeSH.exe|~com.microsoft.emmx|~com.microsoft.emmx.dev|~com.microsoft.emmx.beta|~com.microsoft.emmx.canary|~com.microsoft.msedge

[bongochong]

See this commit as well d18eba8.

[gyCfjSnO]

Thank you so much that worked :)

[bongochong]

No problemo. AdGuard's system and network-wide solutions are quite powerful, so I occasionally have to play catch-up with them.