You'll find the antivirus policies under Manage in the Endpoint security node of the Microsoft Endpoint Manager admin center. Antivirus policies include the same settings as endpoint protection or device restriction profiles for device configuration policy.
However, those policy types include additional categories of settings that are unrelated to Antivirus. The additional settings can complicate the task of configuring Antivirus workload.
Additionally, the settings found in the Antivirus policy for macOS aren't available through the other policy types. The macOS Antivirus profile replaces the need to configure the settings by using. This new platform applies to both devices enrolled through Microsoft Intune as well as Microsoft Defender for Endpoint.
This scenario is in preview and requires use of Configuration Manager current branch version or later. Set up tenant attach for Configuration Manager devices - To support deploying antivirus policy to devices managed by Configuration Manager, configure tenant attach. Set up of tenant attach includes configuring Configuration Manager device collections to support endpoint security policies from Intune.
To set up tenant attach, see Configure tenant attach to support endpoint protection policies. You can use Intune to manage tamper protection on Windows devices as part of Antivirus policy. This includes both devices you manage with Intune, and devices you manage with Configuration Manager through the tenant attach scenario. Profiles for Antivirus policy that support tamper protection for devices managed by Microsoft Endpoint Manager :.
You can also use the Endpoint protection profile for Device configuration policy to configure tamper protection for devices managed by Intune. Profiles for Antivirus policy that support tamper protection for devices managed by Configuration Manager :. When you use Microsoft Defender for Endpoint for Mac , you can configure and deploy Antivirus settings to your managed macOS devices through Intune instead of configuring those settings by use of. Files that could be encrypted ca… GPL Branches Tags.
Could not load branches. Could not load tags. Latest commit. Git stats 10 commits. Failed to load latest commit information. View code. For information how to update or install the platform update, see Update for Windows Defender antimalware platform. Security intelligence update version: 1.
After a new package version is released, support for the previous two versions is reduced to technical support only. Versions older than that are listed in this section, and are provided for technical upgrade support only. Affected machines appear to the customer as having not updated to the latest antimalware platform.
When this update is installed, the device needs the jump package 4. Platform and engine updates are provided on a monthly cadence. To be fully supported, keep current with the latest platform updates. Our support structure is dynamic, evolving into two phases depending on the availability of the latest platform version:. Security and Critical Updates servicing phase - When running the latest platform version, you will be eligible to receive both Security and Critical updates to the anti-malware platform.
Technical Support Only phase - After a new platform version is released, support for older versions N-2 will reduce to technical support only. Platform versions older than N-2 will no longer be supported. If you are manually deploying Microsoft Defender Antivirus Platform Update, or if you are using a script or a non-Microsoft management product to deploy Microsoft Defender Antivirus Platform Update, make sure that version 4.
The below table provides the Microsoft Defender Antivirus platform and engine versions that are shipped with the latest Windows 10 releases:.
For Windows 10 release information, see the Windows lifecycle fact sheet. Sorry this didn't help. Thanks for your feedback. Hello friends. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question
0コメント