Microsoft Defender for Cloud
Cloud and workloads

Enable Defender for Endpoint integration in Microsoft Defender for Cloud

In brief

The article now identifies previously disabled and legacy subscriptions as cases requiring manual opt-in, adds a clearer subscription heading and links, and explains that the PUT request enables the `WDATP` setting through `Microsoft.Security/settings`.

What Defender admins need to know

Administrators can more easily determine when manual enablement is needed and use the clarified script and resource-configuration guidance.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

  • When you enable the Defender for Servers plan in Defender for Cloud, Defender for Endpoint integration is enabled by default.
  • The integration automatically deploys the Defender for Endpoint agent on machines.

This article explains how to manually enable Defender for Endpoint integration when necessary.if it was previously turned off or if you have a legacy subscription that requires manual opt-in.

Prerequisites

Azure tenant | If you moved your subscription between Azure tenants, some manual preparatory steps are also required. Contact Microsoft support for details. Windows Server 2016, 2012 R2 | Unlike later versions of Windows Server, which come with the Defender for Endpoint sensor preinstalled, Defender for Cloud installs the sensor on machines running Windows Server 2016/2012 R2 using the unified Defender for Endpoint solution.

Enable Defender for Endpoint integration on a subscription

Defender for Endpoint integration is enabled by default when you enable a Defender for Servers plan. If you turn off integration on a subscription, you can manually turn it on again.

  1. Additionally, in the Azure portal, you can check that Linux machines have a new Azure extension called MDE.Linux.

Enable Defender for Endpoint unified solution on Windows Server 2016/2012 R2

Enable integration with PowerShell in multiple subscriptions

To enable Defender for Servers integration for Linux machines or Windows Server 2012 R2 and 2016 with MDE Unified solution on multiple subscriptions, you can use one of the PowerShell scripts in the Defender for Cloud GitHub repository

Enable Defender for Endpoint unified solution on Windows Server 2016/2012 R2

Enable integration with PowerShell in multiple subscriptions

To enable Defender for Servers integration for Linux machines or Windows Server 2012 R2 and 2016 with the Microsoft Defender for Endpoint (MDE) Unified solution on multiple subscriptions, you can use one of the PowerShell scripts in the Defender for Cloud GitHub repository.

You can enable the Defender for Endpoint integration at scale through the supplied REST API version 2022-05-01. For full details, see the API documentation.

The following example shows the request body for the PUT request that enables Defender for Endpoint integration:integration. This Microsoft.Security/settings resource configuration sets the WDATP setting to enabled, which activates the Defender for Endpoint integration programmatically for the specified subscription.

URI: https://management.azure.com/subscriptions/<subscriptionId>/providers/Microsoft.Security/settings/WDATP?api-version=2022-05-01