Forum Discussion
MDE onboarding issues with proxy configuration
Hello Everyone, We're currently in the process of onboarding MDE via scripts on several Windows 10 and 11 PCs. These PCs have proxies configured in Settings > Network & internet > Proxy > Manual pro...
If you have web proxy configured, then you will need to bypass the relevant Defender urls using winhttp proxy as well. Refer to the Microsoft’s official link for MDE connectivity requirements to configure the urls for winhttp. Also, make sure that you don’t have SSL inspection enabled in the proxy or else CRL checks will fail.
Thank you for the response.
If i understand correctly, apart from configuring the proxy through Windows Settings, I will have to configure the proxy through either of the following as well,
Registry-based configuration
WinHTTP configured using netsh command: Suitable only for desktops in a stable topology (for example: a desktop in a corporate network behind the same proxy)
Reference link: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/configure-proxy-internet?view=o365-worldwide
Please guide if i am not correct or confirm.
Thanks,
- Spot on. I recently had similar requirements and chose to use the winhttp method as the devices were co-managed so it was easier to push the command using ConfigMgr. However, you should be able to achieve the same using GPO.
- rahuljindal
Thanks for your guidance.
Configuring the registry settings for the proxy helped to onboard the machines.
We noticed that the health status of the machines on the defender portal does not display the version info. Also the analyzer tool reported to update the defender/av plaform and version to a supported version.
While we are addressing the update part, can you guide whether configuration of WinHTTP proxy through netsh command is also a must alongwith registry? Or just registry configuration for the proxy is enough?
Please guide. Thanks,
