würde ich im netzwerk filtern, dann hat man das problem für alle clients gelöst und eine "zentrale verwaltung". entweder über eine firewall(pfsense, opnsense, foritnet etc) oder auch über pi-hole.
zb.
a-0001.a-msedge.net
a-0002.a-msedge.net
a-0003.a-msedge.net
a-0004.a-msedge.net
a-0005.a-msedge.net
a-0006.a-msedge.net
a-0007.a-msedge.net
a-0008.a-msedge.net
a-0009.a-msedge.net
a1621.g.akamai.net
a1856.g2.akamai.net
a1961.g.akamai.net
a978.i6g1.akamai.net
a.ads1.msn.com
a.ads2.msads.net
a.ads2.msn.com
ac3.msn.com
ad.doubleclick.net
adnexus.net
adnxs.com
ads1.msads.net
ads.msn.com
aidps.atdmt.com
aka-cdn-ns.adtech.de
any.edge.bing.com
a.rad.msn.com
az361816.vo.msecnd.net
az512334.vo.msecnd.net
b.ads1.msn.com
b.ads2.msads.net
bingads.microsoft.com
b.rad.msn.com
bs.serving-sys.com
c.atdmt.com
cdn.atdmt.com
cds26.ams9.msecn.net
choice.microsoft.com
choice.microsoft.com.nsatc.net
compatexchange.cloudapp.net
corpext.msitadfs.glbdns2.microsoft.com
corp.sts.microsoft.com
cs1.wpc.v0cdn.net
db3aqu.atdmt.com
df.telemetry.microsoft.com
diagnostics.support.microsoft.com
e2835.dspb.akamaiedge.net
e7341.g.akamaiedge.net
e7502.ce.akamaiedge.net
e8218.ce.akamaiedge.net
ec.atdmt.com
fe2.update.microsoft.com.akadns.net
feedback.microsoft-hohm.com
feedback.search.microsoft.com
feedback.windows.com
flex.msn.com
g.msn.com
h1.msn.com
h2.msn.com
hostedocsp.globalsign.com
i1.services.social.microsoft.com
i1.services.social.microsoft.com.nsatc.net
lb1.www.ms.akadns.net
live.rads.msn.com
m.adnxs.com
msnbot-65-55-108-23.search.msn.com
msntest.serving-sys.com
oca.telemetry.microsoft.com
oca.telemetry.microsoft.com.nsatc.net
onesettings-db5.metron.live.nsatc.net
pre.footprintpredict.com
preview.msn.com
rad.live.com
redir.metaservices.microsoft.com
reports.wes.df.telemetry.microsoft.com
schemas.microsoft.akadns.net
secure.adnxs.com
secure.flashtalking.com
services.wes.df.telemetry.microsoft.com
settings-sandbox.data.microsoft.com
settings-win.data.microsoft.com
sls.update.microsoft.com.akadns.net
sls.update.microsoft.com.nsatc.net
sqm.df.telemetry.microsoft.com
sqm.telemetry.microsoft.com
sqm.telemetry.microsoft.com.nsatc.net
ssw.live.com
static.2mdn.net
statsfe1.ws.microsoft.com
statsfe2.update.microsoft.com.akadns.net
statsfe2.ws.microsoft.com
survey.watson.microsoft.com
telecommand.telemetry.microsoft.com
telecommand.telemetry.microsoft.com.nsatc.net
telemetry.appex.bing.net
telemetry.urs.microsoft.com
vortex-bn2.metron.live.com.nsatc.net
vortex-cy2.metron.live.com.nsatc.net
vortex.data.microsoft.com
vortex-sandbox.data.microsoft.com
vortex-win.data.microsoft.com
cy2.vortex.data.microsoft.com.akadns.net
watson.live.com
watson.ppe.telemetry.microsoft.com
watson.telemetry.microsoft.com
watson.telemetry.microsoft.com.nsatc.net
win10.ipv6.microsoft.com
Microsoft Advertising | Suchmaschinen-Marketing (Search Engine Marketing, SEM) und mehr
http://www.go.microsoft.akadns.net
client.wns.windows.com
wdcp.microsoft.com
wdcpalt.microsoft.com
settings-ssl.xboxlive.com
settings-ssl.xboxlive.com-c.edgekey.net
settings-ssl.xboxlive.com-c.edgekey.net.globalredir.akadns.net
e87.dspb.akamaidege.net
insiderservice.microsoft.com
insiderservice.trafficmanager.net
e3843.g.akamaiedge.net
flightingserviceweurope.cloudapp.net
static.ads-twitter.com
www-google-analytics.l.google.com
p.static.ads-twitter.com
hubspot.net.edge.net
e9483.a.akamaiedge.net
stats.g.doubleclick.net
stats.l.doubleclick.net
adservice.google.de
adservice.google.com
googleads.g.doubleclick.net
pagead46.l.doubleclick.net
hubspot.net.edgekey.net
insiderppe.cloudapp.net
livetileedge.dsx.mp.microsoft.com
s0.2mdn.net
view.atdmt.com
geo.settings-win.data.microsoft.com.akadns.net
db5-eap.settings-win.data.microsoft.com.akadns.net
settings-win.data.microsoft.com
db5.settings-win.data.microsoft.com.akadns.net
asimov-win.settings.data.microsoft.com.akadns.net
db5.vortex.data.microsoft.com.akadns.net
v10-win.vortex.data.microsoft.com.akadns.net
geo.vortex.data.microsoft.com.akadns.net
v10.vortex-win.data.microsoft.com
v10.events.data.microsoft.com
v20.events.data.microsoft.com
us.vortex-win.data.microsoft.com
eu.vortex-win.data.microsoft.com
vortex-win-sandbox.data.microsoft.com
alpha.telemetry.microsoft.com
oca.telemetry.microsoft.com
ceuswatcab01.blob.core.windows.net
ceuswatcab02.blob.core.windows.net
eaus2watcab01.blob.core.windows.net
eaus2watcab02.blob.core.windows.net
weus2watcab01.blob.core.windows.net
weus2watcab02.blob.core.windows.net
ps. noch ein vorteil, eventuelle windows updates können eine netzwerkfilterung nicht zurücksetzen, die lokale datei am client schon(wenn von ms gewünscht).
das ist das selbe thema wie mit den registry "tweaks".