@karthik palani Thank you for reaching out to us, As I understand Microsoft Defender for Identity sensor is failing to register with the cloud instance.
Review the following steps if it helps to resolve this
- Check for schannel event 36874 in system event log,
- TLS hardening was applied to server ? if yes reset to default settings to resolve.
- Also worth checking the .Net registry: Enable TLS 1.2 on .Net by setting the registry keys to use the operating system defaults for SSL and TLS, as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319] SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319] " SchUseStrongCrypto"=dword:00000001
- if the above steps doesnt help, reviewing sensor deployment logs/capturing network trace will give some insights to this issue.
Reference: https://free.blessedness.top/en-us/defender-for-identity/troubleshooting-known-issues
Let me know if you have any further questions, feel free to post back.
Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.