<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MAPS on Anything About IT</title><link>https://www.verboon.info/tags/maps/</link><description>Recent content in MAPS on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Jul 2019 22:33:36 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/maps/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing Windows Defender MAPS Connectivity with PowerShell</title><link>https://www.verboon.info/2019/07/testing-windows-defender-maps-connectivity-with-powershell/</link><pubDate>Mon, 08 Jul 2019 22:33:36 +0000</pubDate><guid>https://www.verboon.info/2019/07/testing-windows-defender-maps-connectivity-with-powershell/</guid><description>&lt;p&gt;Whenever I work with customers on Windows Defender or Microsoft Defender Advanced Threat Protection, one of the first things I usually review are the current Windows Defender settings. Having Windows Defender properly configured is key, because otherwise you might not be able to make use of all the capabilities Defender and Defender ATP provides. One of them is MAPS (Microsoft Active Protection Service) or also known as Windows Defender Antivirus cloud-delivered protection service. Quite often I notice that clients have no connection to MAPS, this can be validated by running the following command from an elevated command prompt:&lt;/p&gt;</description></item></channel></rss>