You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened? Provide a clear and concise description of the bug, including deployment details.
Microsoft support advised that the Session Hosts Antimalware Extension should not be deployed on Windows 11
The message from support is as follows:
"I would suggest you check the Image configurations and compatibility of IaaSAntimalware extensions with OS which you are using inside VM. Because, as per the collab case support engineer, the Antimalware extension is typically deployed on server 2008 r2 and server 2012 r2 to install Windows Defender. Server 2016 and up already have Defender pre-installed, so it is expected for the extension to fail on those server and desktop OSes"
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
What was the expected outcome?
sessionHostsAntimalwareExtension shouldn't be included, and should be removed from the template
Relevant log output
Randomly receiving the below error, but not consistently:
{
"code": "BadRequest",
"message": "Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'IaaSAntimalware' with handler 'Microsoft.Azure.Security.IaaSAntimalware' already added or specified in input."
}
The text was updated successfully, but these errors were encountered:
For me the extension works fine on W11 but it seems to interfere with other tools that manage defender like intune.
So I think there should be at least a parameter to disable the extension for both greenfield and brownfield deployments.
The Microsoft Antimalware for Azure solution includes the Microsoft Antimalware Client, and Service, Antimalware classic deployment model, Antimalware PowerShell cmdlets, and Azure Diagnostics Extension. The Microsoft Antimalware solution is supported on Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 operating system families. It isn't supported on the Windows Server 2008 operating system, and also isn't supported in Linux.
Windows Defender is the built-in Antimalware enabled in Windows Server 2016. The Windows Defender Interface is also enabled by default on some Windows Server 2016 SKUs. The Azure VM Antimalware extension can still be added to a Windows Server 2016 and above Azure VM with Windows Defender.
I would suggest we add a toggle to remove this extension, at a minimum
What happened? Provide a clear and concise description of the bug, including deployment details.
Microsoft support advised that the Session Hosts Antimalware Extension should not be deployed on Windows 11
The message from support is as follows:
"I would suggest you check the Image configurations and compatibility of IaaSAntimalware extensions with OS which you are using inside VM. Because, as per the collab case support engineer, the Antimalware extension is typically deployed on server 2008 r2 and server 2012 r2 to install Windows Defender. Server 2016 and up already have Defender pre-installed, so it is expected for the extension to fail on those server and desktop OSes"
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
What was the expected outcome?
sessionHostsAntimalwareExtension shouldn't be included, and should be removed from the template
Relevant log output
The text was updated successfully, but these errors were encountered: