While we do integrate with Windows Defender, Huntress Product Support still has a limited scope when it comes to troubleshooting Microsoft's products.
If you are having issues with Defender not being enabled even after attempting the steps found in the following Huntress and Microsoft articles, please reach out to Microsoft Support as they will be best equipped to help you:
Huntress Managed AV is designed to manage policy settings, including exclusions. If you are having trouble with exclusions, please verify that you have the correct exclusions in place inside of Huntress, and then please verify that the exclusions exist on the host. If the exclusions exist on the host and inside of Huntress and they are still not working, then please reach out to the Vendor you are setting the exclusions for or to reach out to Microsoft Support. Huntress Support does not have the visibility or access to be able to determine why a Defender exclusion is not working after being correctly set on a host.
Defender Having High System Resource Utilization
If you notice, Defender has unusually high resource utilization (CPU, RAM), and it is bogging the system down. Please look for the Antimalware Service Executable. This has been known for high CPU in particular and can really bog down a system. There is a forum post with many solutions here. In general first things to check are that the OS is up to date and reboot the host to see if the utilization calms down. If neither of those work and the suggestions in the forum don't work please reach out to Microsoft Support as Huntress support does not have the visibility to troubleshoot and fix this.