Apply sensitive, Exchange, and honeytoken identity tags for their documented detections

Frame this document as a source-led configuration and assurance check: Apply sensitive, Exchange, and honeytoken identity tags for their documented detections. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Defender for Identity entity tags in Microsoft Defender from Microsoft supports the following bounded statements:

• Defender for Identity supports tagging accounts as sensitive or honeytokens and tagging devices as Exchange servers. The research record locates this support at Opening tag overview.
• Some detections depend on the sensitive tag, while any sign-in from a tagged honeytoken account triggers an alert. The research record locates this support at Sensitive and honeytoken tag descriptions.

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions and the conditions the source actually describes.

What the source does not establish

Tags affect investigation and detection context; validate ownership and avoid normal use of honeytoken accounts. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Opening tag overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sensitive and honeytoken tag descriptions, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Build a reproducible chain from Opening tag overview; Sensitive and honeytoken tag descriptions to the observed environment. Useful domain evidence includes sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes; label every item with scope, timestamp, collector, and stable identifier.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• Defender for Identity entity tags in Microsoft Defender — Microsoft