# Manage Defender for Identity sensor status, health, updates, and proxy settings together > Use Manage and update Microsoft Defender for Identity sensors to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/manage-sensor-status-health-updates-and-proxy-settings-together/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:12:49+00:00 - Modified: 2026-08-27T13:04:09+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, IT, Microsoft 365 & Identity - Reading time: 3 minutes ## What you need to know Use Manage and update Microsoft Defender for Identity sensors to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Manage and update Microsoft Defender for Identity sensors ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Manage Defender for Identity sensor status, health, updates, and proxy settings together. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Manage and update Microsoft Defender for Identity sensors](https://learn.microsoft.com/en-us/defender-for-identity/sensor-settings) from Microsoft supports the following bounded statements: - The Sensors experience covers sensor status and health, sensor details, updates for v2.x and v3.x, and proxy configuration. The research record locates this support at Opening scope statement. - A sensor details pane exposes health information and provides paths to manage configuration or reopen closed health issues. The research record locates this support at Sensor details description. The source support ends with the statements listed above. Use them to examine Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health in the applicable environment, not to imply a wider guarantee. ## What the source does not establish Portal status and update controls require documented permissions and do not replace server monitoring, change records, or rollback planning. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations before translating the source into an operational decision. ## Applicability questions - For source statement 1 at Opening scope statement, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Sensor details description, which observable configuration, record, or test can confirm applicability here? - Which deployed instance of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health will be compared with the source, and why that instance? - How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations? - Who approves the conclusion, exception, test window, and rollback threshold? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations before and after the test, and store only sanitized operational evidence. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening scope statement; Sensor details description. Favor sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, linked to stable identifiers, time, and operator. Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee. ## Official references - [Manage and update Microsoft Defender for Identity sensors](https://learn.microsoft.com/en-us/defender-for-identity/sensor-settings) — Microsoft ## Primary reference - Name: Manage and update Microsoft Defender for Identity sensors - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/defender-for-identity/sensor-settings - Source publication date: 2026-07-15 ## Citation and use Preferred citation: “Manage Defender for Identity sensor status, health, updates, and proxy settings together,” DSE Security, https://update.dsesecurity.com/updates/manage-sensor-status-health-updates-and-proxy-settings-together/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.