Activate Sensor
In brief
The page now uses updated Microsoft Defender and Microsoft Defender for Endpoint naming and refers to activating sensor v3.x. The publication date was also updated.
What Defender admins need to know
Administrators can follow the existing Advanced features toggle and Sensor management instructions; no action is required.
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.
Automatic sensor activation and automatic Windows auditing are available only after your organization has an active license that includes Microsoft Defender for Identity.
When Automatic sensor v3.x activation is enabled, Microsoft Defender for Identity automatically activates sensor v3.x on eligible domain controllers, AD FS, AD CS, or Microsoft Entra Connect servers that you onboard to Microsoft Defender for Endpoint. The servers must run Windows Server 2019 or later.
Automatic activation doesn't install a separate Defender for Identity sensor package. It activates the sensor capability on eligible servers that are already onboarded to Defender for Endpoint. Servers that already have a Defender for Identity sensor aren't targeted by this flow.
On the Advanced features page in the Microsoft Defender portal at https://security.microsoft.com/securitysettings/identities, use the Automatic sensor v3.x activation toggle to turn on automatic activation for eligible servers. Automatic activation applies only to eligible servers onboarded to Microsoft Defender for Endpoint.
- Turn on the setting to automatically activate eligible servers when they're discovered.
- Turn off the setting to stop future automatic activations.
To activate the Defender for Identity sensor v3.x on an eligible server, follow these steps:
On the Sensor management tab of the On-premises page in the Microsoft Defender portal, select the eligible server where you want to activate
Defender for Identity.the sensor v3.x.Select Activate, and confirm your selection when prompted.
When v3.x sensor activation for the selected server is complete, a green success banner appears. In the banner, select Click here to see the onboarded servers. The Sensor management tab opens, where you can check the sensor's health.
When prompted, enter the access key from the Microsoft Defender portal. The input is masked.
Servers onboarded to Microsoft Defender for Identity only appear as Can be onboarded in device inventory. This status is expected and refers to Microsoft Defender for Endpoint onboarding, not Defender for Identity protection.onboarding. To check the v3.x sensor's health, use the Sensor management tab.
Confirm sensor activation
@@ -13,7 +13,7 @@ ms.service: microsoft-defender-for-identity uhfHeaderId: MSDocsHeader-MicrosoftDefender ms.suite: ems description: Learn how to automatically or manually activate the Microsoft Defender for Identity sensor v3.x on eligible identity-role servers.-ms.date: 2026-11-05T00:00:00.0000000Z+ms.date: 2026-11-11T00:00:00.0000000Z ms.topic: how-to ms.reviewer: rlitinsky ms.custom: msecd-doc-authoring-1015@@ -62,11 +62,11 @@ Note
Automatic sensor activation and automatic Windows auditing are available only after your organization has an active license that includes Microsoft Defender for Identity.
-When **Automatic sensor v3.x activation** is enabled, Defender for Identity automatically activates sensor v3.x on eligible domain controllers, AD FS, AD CS, or Microsoft Entra Connect servers that you onboard to Defender for Endpoint. The servers must run Windows Server 2019 or later.
+When **Automatic sensor v3.x activation** is enabled, Microsoft Defender automatically activates sensor v3.x on eligible domain controllers, AD FS, AD CS, or Microsoft Entra Connect servers that you onboard to Microsoft Defender for Endpoint. The servers must run Windows Server 2019 or later.
Automatic activation doesn't install a separate Defender for Identity sensor package. It activates the sensor capability on eligible servers that are already onboarded to Defender for Endpoint. Servers that already have a Defender for Identity sensor aren't targeted by this flow.
-On the **Advanced features** page in the Microsoft Defender portal at https://security.microsoft.com/securitysettings/identities, use the **Automatic sensor v3.x activation** toggle to turn on automatic activation for eligible servers. Automatic activation applies only to eligible servers onboarded to Defender for Endpoint.
+On the **Advanced features** page in the Microsoft Defender portal at https://security.microsoft.com/securitysettings/identities, use the **Automatic sensor v3.x activation** toggle to turn on automatic activation for eligible servers. Automatic activation applies only to eligible servers onboarded to Microsoft Defender for Endpoint.
- Turn on the setting to automatically activate eligible servers when they're discovered.
- Turn off the setting to stop future automatic activations.
@@ -77,7 +77,7 @@ The **Advanced features** page also includes **Automatic Windows auditing config
To activate the Defender for Identity sensor v3.x on an eligible server, follow these steps:
-1. On the **Sensor management** tab of the **On-premises** page in the Microsoft Defender portal, select the eligible server where you want to activate Defender for Identity.
+1. On the **Sensor management** tab of the **On-premises** page in the Microsoft Defender portal, select the eligible server where you want to activate the sensor v3.x.
2. Select **Activate**, and confirm your selection when prompted.
3. When v3.x sensor activation for the selected server is complete, a green success banner appears. In the banner, select **Click here to see the onboarded servers**. The **Sensor management** tab opens, where you can check the sensor's health.
@@ -111,7 +111,7 @@ This onboarding method supports new Defender for Identity sensor v3.x deployment ```
8. When prompted, enter the access key from the Microsoft Defender portal. The input is masked.
-Servers onboarded to Defender for Identity only appear as **Can be onboarded** in device inventory. This status is expected and refers to Defender for Endpoint onboarding, not Defender for Identity protection. To check the v3.x sensor's health, use the **Sensor management** tab.
+Servers onboarded to Microsoft Defender for Identity only appear as **Can be onboarded** in device inventory. This status is expected and refers to Microsoft Defender for Endpoint onboarding. To check the v3.x sensor's health, use the **Sensor management** tab.
## Confirm sensor activation
