Defender for Endpoint and disconnected environments. Which proxy configuration wins?

aexlz - I tested last week and configured my test device to use accidentally use a static proxy it couldnt reach (blocked by firewall). The report showed that static proxy as the proxy method (as you have shown above) but that all the URLs were reachable which wasnt technically possible in my case.

I reviewed the static proxy log and couldnt see the traffic and realised it was blocked by the firewall so was confused as to why the report showed successful connections.?

When I reviewed the clientanalyzer.txt file I could see the URLs were reachable via WPAD proxy (which was reachable) and the tests using my static proxy failed, yet in the HTML report the static proxy was listed as the configured proxy and the results showed all URLs as accessible?

From my testing the report seems to show what's configured as the proxy config method but that the URL results in the section below are not necessarily the results of using that method. Instead, the results reflect the results of testing whether the URLs can be reached by any of the possible methods (Default Proxy, Named Proxy, WPAD , Command Line Proxy etc).