The trick is to read a template and ‘translate’ it into a. If an existing System Center Configuration Manager 2012 or newer infrastructure is available and the Endpoint Protection Point is enabled and used, then either existing configurations or the Endpoint Protection templates can be used.
This brings a new challenge: what configuration should be in the. json files can be used to provision a configuration for the extension. More information on this cmdlet is available at Īfter reading the article I noticed that. At his time of writing this portal is still in Preview though so it is not support.Īfter checking out the cmdlet reference for Azure, I found the Set-AzureVMMicrosoftAntimalwareExtension cmdlet. NOTE: More customization is also possible in the ‘new’ portal available at . It became clear that the only way to customize the configuration is using Azure PowerShell. This might work in most scenario’s but company policy may require customization when specified, this may be extended to customizing the extension for specific server roles or even desktops.
While enabling the Microsoft Antimalware extension can be enabled there, only the default settings will be applied. Recently, I was investigating in managing the Microsoft Antimalware extension on Azure virtual machines.Īs we all know, the Microsoft Antimalware extension can be enabled when creating a new Azure virtual machine in the Azure portal.
0 kommentar(er)
