MicrosoftDefenderForEndpoint-PowerBI can't use

Hi Anonymous ，

The 400 Bad Request error is an HTTP [Hyper Text Transfer Protocol] status code that means that the request you sent to the website server (i.e. a request to load a web page) was somehow malformed therefore the server was unable to understand or process the request.

 

When troubleshooting an HTTP 400 condition, it is important to remember that the underlying problem is that the client has sent a request to IIS that breaks one or more rules that HTTP.sys is enforcing. You will want to see exactly what the client is sending to IIS; to do this, capture a network trace of the client sending the bad request. You can analyze the trace to see the raw data that the client sends to IIS, and to see the raw response data that IIS sends back to the client.  You can also use an HTTP sniffer tool called Fiddler; this is a great tool as it allows you to see the HTTP headers even if the client and server are communicating over SSL.

 

The next data item you will want to use is the httperr.log file.  Beginning in IIS 6.0, the HTTP.sys component handles incoming HTTP requests before they are passed along to IIS, and is the component responsible for blocking requests that don’t meet the IIS requirements.  When HTTP.sys blocks the request, it will log information to its httperr.log file concerning the bad request.

 

NOTE:  For more information on the HTTP API error logging that HTTP.sys provides, see the following article:

 

Get help with website error messages (HTTP errors)

What is HTTP error 400 and how do you fix it?

 

Did I answer your question? Mark my post as a solution!

Best Regards

Lucien