Deploy Sensor V3
In brief
The page updates the Microsoft Defender portal navigation to Settings > Identities > Manage action accounts and revises terminology for identity security and automatic auditing guidance. The page date was also updated.
What Defender admins need to know
Administrators preparing sensor v2.x-to-v3.x migrations should use the revised portal navigation when following the documented 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.
The v3.x sensor uses the local system identity of the server for both purposes. It doesn't use Directory Service Accounts (DSA) or group Managed Service Accounts (gMSA). LocalSystem is the only supported identity for v3.x.
Before migrating from sensor v2.x, select Automatically use the sensor's local system account in the Microsoft Defender portal (Settings > Identities > Microsoft Defender for Identity > Manage action accounts). Migration doesn't change this action account setting automatically. The v3.x sensors don't use gMSA accounts configured for v2.x sensors.
Important
DSA and gMSA health alerts in environments with both v2.x and v3.x sensors
If your workspace still has a Directory Service Account (DSA) or group Managed Service Account (gMSA) configured because v2.x sensors on AD FS, AD CS, or Entra Connect servers still require it, DSA and gMSA credentials continue to be validated on all sensors in the workspace, including v3.x sensors. If DSA or gMSA credential validation fails, the Directory services user credentials are incorrect health alert appears. Workspace-level validation of DSA and gMSA credentials on all sensors is by design. Microsoft Defender for Identity validates DSA and gMSA credentials at the workspace level for all sensors as long as those accounts exist, regardless of whether individual sensors use them for auditing or response actions.
Defender for Identity v3.x sensors ignore the DSA and gMSA for auditing and response actions, but they're still included in workspace-level credential validation. Migration doesn't remove the workspace-level DSA or gMSA configuration automatically. To stop receiving this health alert on v3.x sensors, manually remove the configuration after all sensors are fully migrated to v3.x and no v2.x sensors require it. Removing the workspace configuration doesn't delete the gMSA account in Active Directory.
Configure Windows event auditing
Identity security in Microsoft Defender for Identity relies on Windows event logs for many detections. For v3.x sensors, enable automatic auditing to configure supported auditing settings. Complete the additional steps for AD FS or AD CS, as applicable.
If automatic auditing isn't available or you opted out, configure auditing manually or configure Windows event collection using PowerShell.
@@ -13,7 +13,7 @@ ms.service: microsoft-defender-for-identity uhfHeaderId: MSDocsHeader-MicrosoftDefender ms.suite: ems description: Learn the requirements and configuration steps to deploy the Defender for Identity sensor v3.x on eligible identity-role servers.-ms.date: 2026-10-19T00:00:00.0000000Z+ms.date: 2026-11-11T00:00:00.0000000Z ms.topic: how-to ms.custom: msecd-doc-authoring-1016 ms.reviewer: rlitinsky@@ -146,7 +146,7 @@ The Defender for Identity sensor interacts with Active Directory in two ways:
The v3.x sensor uses the local system identity of the server for both purposes. It doesn't use Directory Service Accounts (DSA) or group Managed Service Accounts (gMSA). LocalSystem is the only supported identity for v3.x.
-Before migrating from sensor v2.x, select **Automatically use the sensor's local system account** in the Microsoft Defender portal (**Settings** > **Identities** > **Microsoft Defender for Identity** > **Manage action accounts**). Migration doesn't change this [action account setting](manage-action-accounts) automatically. The v3.x sensors don't use gMSA accounts configured for v2.x sensors.
+Before migrating from sensor v2.x, select **Automatically use the sensor's local system account** in the Microsoft Defender portal (**Settings** > **Identities** > **Manage action accounts**). Migration doesn't change this [action account setting](manage-action-accounts) automatically. The v3.x sensors don't use gMSA accounts configured for v2.x sensors.
Important
@@ -154,7 +154,7 @@ If any of your sensors are v3.x, select **Automatically use the sensor's local s
#### DSA and gMSA health alerts in environments with both v2.x and v3.x sensors
-If your workspace still has a Directory Service Account (DSA) or group Managed Service Account (gMSA) configured because v2.x sensors on AD FS, AD CS, or Entra Connect servers still require it, DSA and gMSA credentials continue to be validated on all sensors in the workspace, including v3.x sensors. If DSA or gMSA credential validation fails, the **Directory services user credentials are incorrect** health alert appears. Workspace-level validation of DSA and gMSA credentials on all sensors is by design. Defender for Identity validates DSA and gMSA credentials at the workspace level for all sensors as long as those accounts exist, regardless of whether individual sensors use them for auditing or response actions.
+If your workspace still has a Directory Service Account (DSA) or group Managed Service Account (gMSA) configured because v2.x sensors on AD FS, AD CS, or Entra Connect servers still require it, DSA and gMSA credentials continue to be validated on all sensors in the workspace, including v3.x sensors. If DSA or gMSA credential validation fails, the **Directory services user credentials are incorrect** health alert appears. Workspace-level validation of DSA and gMSA credentials on all sensors is by design. Microsoft Defender validates DSA and gMSA credentials at the workspace level for all sensors as long as those accounts exist, regardless of whether individual sensors use them for auditing or response actions.
Defender for Identity v3.x sensors ignore the DSA and gMSA for auditing and response actions, but they're still included in workspace-level credential validation. Migration doesn't remove the workspace-level DSA or gMSA configuration automatically. To stop receiving this health alert on v3.x sensors, manually remove the configuration after all sensors are fully migrated to v3.x and no v2.x sensors require it. Removing the workspace configuration doesn't delete the gMSA account in Active Directory.
@@ -174,7 +174,7 @@ Complete these configuration steps after the sensor is activated and running.
### Configure Windows event auditing
-Defender for Identity relies on Windows event logs for many detections. For v3.x sensors, [enable automatic auditing](configure-windows-event-collection#configure-defender-for-identity-to-collect-windows-events-automatically) to configure supported auditing settings. Complete the additional steps for [AD FS](configure-windows-event-collection#configure-auditing-on-an-ad-fs-server) or [AD CS](configure-windows-event-collection#configure-auditing-on-an-ad-cs-server), as applicable.
+Identity security in Microsoft Defender relies on Windows event logs for many detections. For v3.x sensors, [enable automatic auditing](configure-windows-event-collection#configure-defender-for-identity-to-collect-windows-events-automatically) to configure supported auditing settings. Complete the additional steps for [AD FS](configure-windows-event-collection#configure-auditing-on-an-ad-fs-server) or [AD CS](configure-windows-event-collection#configure-auditing-on-an-ad-cs-server), as applicable.
If automatic auditing isn't available or you opted out, [configure auditing manually](configure-windows-event-collection#configure-windows-event-collection-manually) or [configure Windows event collection using PowerShell](configure-windows-event-collection#configure-windows-event-collection-using-powershell).
