Use this document to connect an official requirement or behavior to observable evidence: Migrate sensor v2 only after checking sensor v3 feature limits. Only the official source and traced locations below supply facts. Confirm applicability before acting.
\nThe official Migrate from Defender for Identity sensor v2 to sensor v3.x from Microsoft supports the following bounded statements:
\nOnly the traced statements above are asserted as source facts. Apply the review to Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health after confirming that the source and deployed context match.
\nConfirm every documented v3 limitation and recovery path; the stated automated behavior is not a substitute for local change validation. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.
\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. 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.
\nDo 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, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations. Handle credentials, keys, recovery data, and personal information through approved secure channels.
\nA reviewer should be able to retrace the decision from Opening overview; Pre-migration warning through sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests. Record what was collected, where, when, by whom, and which system or role it represents.
\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.
\n