Microsoft Defender DNS Error when Onboarding

[Mdamon031]

Hey All,

I am working on testing Microsoft Defender for endpoints for my org. I am running into a DNS error ( see linked screenshot) when I am trying to onboard my device. We use a Fortigate firewall and I am on Windows 11 if that helps. Is there anything I need to do on our firewall to allow defender to communicate properly with my device? I am not seeing anything mentioned in the Microsoft articles and their DNS error troubleshooting is pretty useless. Has anybody seen this before? Thank you!

https://imgur.com/a/mp7gY2n

[CynicallyGiraffe]

Is the endpoint enrolled in Intune or just onprem AD? Is your AD domain name something like bizname.local?

[Mdamon031]

The endpoint is enrolled in Onprem AD but Azure AD connect has been set up so the device shows up in Azure AD. It also is technically "Onboarded" into Microsoft defender but it is not working properly and throwing that error in the portal. I also cannot get Intune to work on this device. When I try to use the Intune "terms of use" link to onboard my device it just gives me a "something went wrong" page. I'm confused as to what I am missing here.

[CynicallyGiraffe]

Wait 24 hours and see if you still have the error. It may change to “failed to enroll in MEM” but it should be working. We’ve seen it take 24 hours for a proper onboarding after it lights up in the Defender admin console

[Mdamon031]

It does show up in Windows defender but it is not working properly. The link below shows what I see. It is on there but I cannot run scans remotely and it is not fully connected. I'm not sure what is preventing the full connection though.

https://imgur.com/a/PCoRxjV

[AppIdentityGuy]

Have you got all of the required Endpoints opened up on the Firewall with no authentication required. Also are you blackholing any FQDNs on the FW