# Microsoft Defender for Identity sensor deployment is validated by reviewing the Health Issues page

Microsoft Defender for Identity sensor deployment is not a one-time event: domain controllers are added and decommissioned, network adapter configurations…

Source: https://maester.dev/docs/tests/ZTA.41020

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

## Overview

Microsoft Defender for Identity sensor deployment is not a one-time event: domain controllers are added and decommissioned, network adapter configurations change, certificates rotate, group memberships of the gMSA service account drift, and Microsoft Entra Connect is upgraded. A weekly review of the Health Issues page is the documented operational practice that catches these regressions before they create coverage gaps. When the review is skipped, accumulating health issues silently disable detection paths that the security operations team relies on to identify adversary activity across monitored domain controllers and network segments. The risk is not limited to the individual sensor that reports the issue: when a domain controller loses coverage, every authentication and directory operation that transits that controller becomes invisible to the platform, and an attacker who identifies the blind spot can stage activity there with reduced risk of detection. A regular review cadence ensures that health issues are triaged and resolved before they compound into broad coverage gaps that undermine the organization's investment in the platform.

## Remediation

- [Microsoft Defender for Identity health issues](https://learn.microsoft.com/en-us/defender-for-identity/health-alerts)
- [Troubleshoot Microsoft Defender for Identity known issues](https://learn.microsoft.com/en-us/defender-for-identity/troubleshooting-known-issues)
- [Microsoft Defender for Identity sensor settings](https://learn.microsoft.com/en-us/defender-for-identity/sensor-settings)

## Run it

The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:

```powershell
Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-Maester
Invoke-Maester -Pack ZTA -SkipBuiltIn
```

Leave out `-SkipBuiltIn` to run Maester's own checks in the same run.

<details>
<summary>About this check</summary>

| | |
| --- | --- |
| Severity | Medium |
| Effort to fix | Low |
| Impact on users | Low |
| Pillar | SecOps |
| Category | Identity threat protection |
| Product | [Defender](/docs/tests/products/defender) |
| Feature | Defender for Identity |
| Area | Logging and detection |
| Licence | ATA |
| Tenant | Workforce |

Product, feature, area and ATT&CK are Maester's: the assessment does not record them, so Maester keeps them in the pack's `taxonomy.json`.

</details>

<p class="mt-ms-note not-content"><svg class="mt-ms-note__logo" viewBox="0 0 21 21" aria-hidden="true"><rect width="10" height="10" fill="#f25022"/><rect x="11" width="10" height="10" fill="#7fba00"/><rect y="11" width="10" height="10" fill="#00a4ef"/><rect x="11" y="11" width="10" height="10" fill="#ffb900"/></svg><span>A Microsoft check, part of the <a href="/docs/tests/packs/zero-trust-assessment">Zero Trust Assessment</a> pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, <a href="/docs/tests/packs/zero-trust-assessment#licence">MIT licence</a>.</span></p>
