@@ -1,10 +1,10 @@ ----title: Manage and update sensors+title: Manage and Update Sensors description: Learn how to view, manage, and update Microsoft Defender for Identity sensors in the Microsoft Defender portal, including sensor health, migration state, and delayed updates.-ms.date: 07/15/2026+ms.date: 09/01/2026 ms.topic: how-to ms.reviewer: rlitinsky-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016   - msecd-doc-authoring-106   - sfi-image-nochange ai-usage: ai-assisted@@ -14,7 +14,7 @@ ai-usage: ai-assisted  # Manage and update Microsoft Defender for Identity sensors -This article explains how to view, manage, and update Defender for Identity sensors in the Microsoft Defender portal.+This article explains how to view, manage, and update Defender for Identity sensors in the Microsoft Defender portal. It covers sensor status and health monitoring, sensor property details, update processes for both v2.x and v3.x sensors, and proxy configuration. This guidance is intended for security administrators who manage Defender for Identity deployments. Some tasks described in this article require specific permissions or configuration prerequisites, such as proxy settings or sensor installation prerequisites, which are referenced in the relevant sections.  ## View sensor settings and status @@ -24,7 +24,6 @@ To view sensor settings and status in the Microsoft Defender portal, perform the 1. In the left sidebar, under **Deployment**, select **On-premises**. 1. Select the **Sensors** tab. - :::image type="content" source="media/sensor-settings/sensor-settings-page.png" alt-text="Screenshot that shows the Sensors tab on the On-premises page in the Microsoft Defender portal." lightbox="media/sensor-settings/sensor-settings-page.png":::  The **Sensors** tab shows all Defender for Identity sensors deployed in your environment. From this tab you can:@@ -43,15 +42,15 @@ Select a sensor row to open a details pane with information about the sensor and The **Sensors** tab shows the following columns. For columns with multiple possible values, see the tables below.  - **Sensor**: The sensor's NetBIOS computer name.-- **Type**: The sensor type. For possible values, see [Type](#type).+- **Type**: The sensor type. For possible values, see [Sensor type](#type). - **Domain**: The fully qualified domain name of the Active Directory domain where the sensor is installed.-- **Migration state**: Indicates if sensors are eligible for [migration from v2.x to v3.x](deploy/migrate-to-sensor-v3.md). For possible values, see [Migration state](#migration-state).-- **Service status**: The current state of the sensor service on the server. For possible values, see [Service status](#service-status).-- **Sensor status**: The current update and configuration state of the sensor software. For possible values, see [Sensor status](#sensor-status).+- **Migration state**: Indicates if sensors are eligible for [migration from v2.x to v3.x](deploy/migrate-to-sensor-v3.md). For possible values, see [Sensor migration state](#migration-state).+- **Service status**: The current state of the sensor service on the server. For possible values, see [Sensor service status](#service-status).+- **Sensor status**: The current update and configuration state of the sensor software. For possible values, see [Sensor status values](#sensor-status). - **Version**: The sensor version installed.-- **Delayed update**: Whether delayed updates are enabled or disabled. Delayed updates are supported by version 2 of the sensor. For more information, see [Delayed sensor update](#delayed-update-for-sensor-v2x). +- **Delayed update**: Whether delayed updates are enabled or disabled. Delayed updates are supported by version 2 of the sensor. For more information, see [Delayed update for sensor v2.x](#delayed-update-for-sensor-v2x).  - **Health issues**: The count of open health issues on the sensor.-- **Health status**: The overall health of the sensor based on the highest severity open health issue. For possible values, see [Health status](#health-status).+- **Health status**: The overall health of the sensor based on the highest severity open health issue. For possible values, see [Sensor health status](#health-status). - **Created**: The date the sensor was installed.  <a name="type"></a>@@ -70,11 +69,11 @@ The type column indicates the sensor type based on the server role where the sen <a name="migration-state"></a> ### Sensor migration state -The migration state column shows if the sensor is eligible for [migration from v2.x to v3.x](deploy/migrate-to-sensor-v3.md).+The migration state column indicates whether a Defender for Identity sensor running v2.x can be upgraded in place to v3.x. Possible values include **Ready for migration**, **Not ready for migration**, **Migrating**, **Up to date**, and **Migration failed**, as described in the table later in this section. For more information about the migration process, see [migration from v2.x to v3.x](deploy/migrate-to-sensor-v3.md).  For a server to be eligible for migration, it must be: -- A domain controller without additional identity roles (AD FS, AD CS, or Microsoft Entra Connect) running. Domain controllers with identity roles support v3.x for new deployments, but in-place migration isn't currently supported for these servers.+- A domain controller, including a domain controller that also runs AD FS, AD CS, or Microsoft Entra Connect. - Running a Defender for Identity sensor v2.x. - Running Windows Server 2019 or later. - Includes the July 2026 or later cumulative update.@@ -136,6 +135,9 @@ The health status column indicates the overall health of the sensor based on the  Defender for Identity sensor v3.x is delivered as a component of Microsoft Defender for Endpoint and is updated automatically through Windows Updates. No manual sensor update process is required for v3.x sensors. +> [!IMPORTANT]+> The v3.x sensor updates through Windows Update as part of the server's operating system update process. The per-sensor **Delayed update** option available for v2.x sensors doesn't apply to v3.x.+ The following sensor update information applies only to Defender for Identity sensor v2.x.  ### Defender for Identity sensor v2.x update types@@ -155,7 +157,6 @@ Defender for Identity sensors v2.x support two kinds of updates:   - Restarted: Defender for Identity sensor services    > [!NOTE]-> > Defender for Identity sensors v2.x always reserve at least 15% of the available memory and CPU on the domain controller where the sensor is installed. If the service consumes too much memory, it's automatically stopped and restarted by the sensor updater service.  ### Delayed update for sensor v2.x@@ -197,12 +198,11 @@ Every few minutes, v2.x sensors check whether a newer version is available. When      For any sensor that fails to complete the update process, a relevant [health alert](health-alerts.md) is triggered, and is sent as a notification. - ### Silently update the Defender for Identity v2.x sensor  Use the following command to silently update the Defender for Identity v2.x sensor: -**Syntax**:+#### Syntax  The following command shows the basic syntax for running the sensor installer silently or interactively: @@ -210,7 +210,7 @@ The following command shows the basic syntax for running the sensor installer si "Azure ATP sensor Setup.exe" [/quiet] [/Help] [NetFrameworkCommandLineArguments="/q"] ``` -**Installation options**:+#### Installation options  > [!div class="mx-tableFixed"] >@@ -220,7 +220,7 @@ The following command shows the basic syntax for running the sensor installer si > |Help|/help|No|Provides help and quick reference. Displays the correct use of the setup command including a list of all options and behaviors.| > |NetFrameworkCommandLineArguments="/q"|NetFrameworkCommandLineArguments="/q"|Yes|Specifies the parameters for the .Net Framework installation. Must be set to enforce the silent installation of .Net Framework.| -**Examples**:+#### Examples  The following example runs the sensor installer silently from the command line without user interaction: @@ -243,14 +243,15 @@ Learn more about [asset management rules](/defender-xdr/configure-asset-rules).  ## Configure proxy settings -We recommend that you configure initial proxy settings during silent installation [using command line switches](deploy/install-sensor.md#perform-a-defender-for-identity-silent-installation). If you need to update your proxy settings later on, use either the [CLI](deploy/configure-proxy.md#change-proxy-configuration-using-the-cli) or [PowerShell](deploy/configure-proxy.md#change-proxy-configuration-using-powershell).+We recommend that you configure initial proxy settings during silent installation [using command line switches](deploy/install-sensor.md#perform-a-defender-for-identity-silent-installation). If you need to update your proxy settings later on, use either the [CLI method](deploy/configure-proxy.md#change-proxy-configuration-using-the-cli) or [PowerShell method](deploy/configure-proxy.md#change-proxy-configuration-using-powershell).  If you'd previously configured your proxy settings via either WinINet or a registry key and need to update them, you'll need to [use the legacy proxy configuration method](deploy/configure-proxy.md#change-proxy-configuration-using-legacy-methods) you used originally.  For more information, see [Configure endpoint proxy and internet connectivity settings](deploy/configure-proxy.md). -## Next steps+## Related content -- [Defender for Identity sensor v2.x prerequisites](deploy/prerequisites-sensor-version-2.md) and [Defender for Identity sensor v3.x prerequisites](deploy/deploy-sensor-v3.md) -- [Configure event forwarding](deploy/configure-event-forwarding.md)+- [Microsoft Defender for Identity sensor v2.x prerequisites](deploy/prerequisites-sensor-version-2.md)+- [Deploy the Defender for Identity sensor v3.x](deploy/deploy-sensor-v3.md)+- [Configure Windows event forwarding to your Defender for Identity standalone sensor](deploy/configure-event-forwarding.md) - [Defender for Identity community forum](<https://aka.ms/MDIcommunity>)