Internal Server and Bad Gateway Error for Defender APIs

Ravi Singh 0

Hi Team,

For one of our Customer, we are trying to pull Vulnerability using https://learn.microsoft.com/en-us/defender-endpoint/api/get-assessment-software-vulnerabilities?view=o365-worldwide and assets using https://learn.microsoft.com/en-us/defender-endpoint/api/get-machines.

Often we are getting

Response for Internal Server Error -

{"error":{"code":"InternalServerError","message":"Internal Server Error","target":"|7cf888a7-492ad658467ae2d1.1."}}

Response for Gateway Timeout -

<html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx</center> </body>

Any suggestion for the cause and we can do something to solve.

Thanks

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2025-11-24T23:38:35.1933333+00:00

Hello Ravi,
The errors (InternalServerError and 502 Bad Gateway) when calling Microsoft Defender for Endpoint APIs typically stem from transient service issues, throttling, oversized responses, or network timeouts. To resolve them, use the correct regional base URI, implement exponential backoff with jitter for retries, and respect rate limits. Reduce payload size by lowering pageSize and paginating properly, or switch to the “via files” export for large vulnerability data pulls. Ensure proper permissions and RBAC scoping, optimize OData filters, and increase client timeouts while checking proxy/TLS settings. These steps combined with concurrency control and delta exports significantly improve reliability and prevent gateway or internal server errors.

Your answer