Exempt Defender for Identity sensor traffic from SSL interception
Use Connect to the Defender for Identity service to review this narrow operational decision without extending the source beyond its stated scope.
Read the briefingDSE security knowledge hubIT
IT
Knowledge
Page 18 of the DSE IT knowledge center, with source-backed guidance and practical next steps.
DSE-authoredOfficial sourcesReviewed guidance
Explore this topic
Start with the cornerstone guide IT knowledge center
Production-minded guidance for endpoints, servers, updates, cloud services, administration, and supportable operations.
DSE post stream
429 articlesIT
Test Defender for Identity cloud connectivity before and after sensor deployment
Use Test Microsoft Defender for Identity connectivity to review this narrow operational decision without extending the source beyond its stated scope.
Read the checklist
Plan Defender for Identity operations around the unified portal and 30-day hunting retention
Use Microsoft Defender for Identity in the Microsoft Defender portal to review this narrow operational decision without extending the source beyond its stated scope.
Read the explainer
Finish Defender for Identity sensor settings before judging telemetry coverage
Use Configure Microsoft Defender for Identity sensor settings to review this narrow operational decision without extending the source beyond its stated scope.
Read the guide
Include non-domain and non-Windows devices in Defender for Identity monitoring scope
Use Microsoft Defender for Identity frequently asked questions to review this narrow operational decision without extending the source beyond its stated scope.
Read the playbook
Separate Defender for Identity directory reads from remediation permissions
Use Directory Service Accounts for Microsoft Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope.
Read the briefing
Use a gMSA only for Defender for Identity sensor v2 directory reads
Use Configure a gMSA directory service account for Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope.
Read the checklist
Scope Defender for Identity action accounts to remediation needs
Use Configure Microsoft Defender for Identity action accounts to review this narrow operational decision without extending the source beyond its stated scope.
Read the explainer
Treat standalone Defender for Identity sensor coverage as limited without ETW
Use Microsoft Defender for Identity standalone sensor prerequisites to review this narrow operational decision without extending the source beyond its stated scope.
Read the guide
Mirror every monitored domain controller to a standalone identity sensor
Use Configure port mirroring to review this narrow operational decision without extending the source beyond its stated scope.
Read the playbook