Microsoft Defender for Identity
Identity protection

Troubleshooting Known Issues

In brief

The troubleshooting page no longer includes the note that activating Defender for Identity v3.x sensors without Defender for Endpoint was temporarily unsupported in government cloud environments. The page date and authoring metadata were also updated.

What Defender admins need to know

Government-cloud administrators will no longer find this limitation in the known-issues guidance and should review the current page when planning sensor activation.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

uhfHeaderId: MSDocsHeader-MicrosoftDefender ms.suite: ems description: Describes how you can troubleshoot issues in Microsoft Defender for Identity. ms.date: 2026-10-28T00:11-19T00:00:00.0000000Z ms.topic: troubleshooting ms.reviewer: rlitinsky ms.custom:

  • msecd-doc-authoring-10151032
  • sfi-image-nochange
  • sfi-ropc-nochange locale: en-us

This article describes how to troubleshoot known issues in Microsoft Defender for Identity.

Sensor v3.x activation without Defender for Endpoint isn't supported in government clouds

Activating the Defender for Identity v3.x sensor on servers without Microsoft Defender for Endpoint deployment is temporarily not supported in government cloud environments.

Sensor migration isn't supported between different Microsoft tenants

Migration from sensor v2.x to sensor v3.x isn't supported when the Defender for Identity workspace and Defender for Endpoint onboarding for the same server are associated with different Microsoft tenants. The server might appear Ready for migration, but sensor v3.x activation fails. Sensor v2.x continues reporting, and the unsuccessful migration eventually rolls back.