Re: I did it another way...
"Would you share please"
127.0.0.1 a-msedge.net
127.0.0.1 a.ads2.msads.net
127.0.0.1 adnexus.net
127.0.0.1 aidps.atdmt.com
127.0.0.1 az361816.vo.msecnd.net
127.0.0.1 az512334.vo.msecnd.net
127.0.0.1 b.ads1.msn.com
127.0.0.1 b.ads2.msads.net
127.0.0.1 c.atdmt.com
127.0.0.1 c.msn.com
127.0.0.1 cdn.atdmt.com
127.0.0.1 cds26.ams9.msecn.net
127.0.0.1 db3aqu.atdmt.com
127.0.0.1 ec.atdmt.com
127.0.0.1 feedback.microsoft-hohm.com
127.0.0.1 flex.msn.com
127.0.0.1 g.msn.com
127.0.0.1 h1.msn.com
127.0.0.1 lb1.www.ms.akadns.net
127.0.0.1 live.rads.msn.com
127.0.0.1 m.adnxs.com
127.0.0.1 msedge.net
127.0.0.1 msnbot-65-55-108-23.search.msn.com
127.0.0.1 msntest.serving-sys.com
127.0.0.1 preview.msn.com
127.0.0.1 reports.wes.df.telemetry.microsoft.com
127.0.0.1 sO.2mdn.net
127.0.0.1 schemas.microsoft.akadns.net
127.0.0.1 secure.flashtalking.com
127.0.0.1 settings-win.data.microsoft.com
127.0.0.1 statsfe2.ws.microsoft.com
127.0.0.1 telemetry.appex.bing.net
127.0.0.1 wes.df.telemetry.microsoft.com
plus probably others.
Also be aware that Slurp's "telemetry" bypasses the hosts file and talks direct to the relevant IPs, so you need to block in an external firewall or your router.
Another vote for Spybot Anti-Beacon here. Re-run after any updates. You'll see how Slurp resets all the privacy settings you've carefully and laboriously set.
Biting the hand that feeds IT
