Forum Discussion
gilblumberg
May 21, 2023Iron Contributor
Updating the MDE.Windows extension
We have multiple servers running in Azure Arc onboarded into MDE using the MDE.Windows extension. Just our luck to discover that Microsoft's documentation shows that that automatic extension upgr...
gilblumberg
Jun 08, 2023Iron Contributor
Microsoft support that updating it serves no purpose whatsoever.
Jonhed
Jun 10, 2023Iron Contributor
>When deleting the MDE.Windows/MDE.Linux extension, there is no impact to the Sensor software on the server
The point about deletion not having any effect on the sensor is covered below, but yes I do agree the relation between the extension and the MDE software in general is not covered much.
https://learn.microsoft.com/en-us/azure/defender-for-cloud/integration-defender-for-endpoint
>If integration with Microsoft Defender for Endpoint is enabled, and the extension is deleted, it will be promptly installed again.
If you check that box for MDE integration, this is indeed true.
The defender for servers plan will charge you for any server present anyways though.
Onboarding scope can be managed with Azure Policy if you uncheck that box, but you would still be charged.
Hoping to see some scoping for the actual Defender for Servers plan some time.
The point about deletion not having any effect on the sensor is covered below, but yes I do agree the relation between the extension and the MDE software in general is not covered much.
https://learn.microsoft.com/en-us/azure/defender-for-cloud/integration-defender-for-endpoint
>If integration with Microsoft Defender for Endpoint is enabled, and the extension is deleted, it will be promptly installed again.
If you check that box for MDE integration, this is indeed true.
The defender for servers plan will charge you for any server present anyways though.
Onboarding scope can be managed with Azure Policy if you uncheck that box, but you would still be charged.
Hoping to see some scoping for the actual Defender for Servers plan some time.