Power Automate – “Get insider risk management case” action failing with 502 BadGateway (Azure Front Door DNSNameNotResolved)
Summary：
We are experiencing a recurring failure in a Power Automate cloud flow when calling the Get insider risk management case action.
The flow was previously working reliably and no configuration, permission, or input changes were made on our side.
The failure consistently returns 502 BadGateway, and the raw output shows an Azure Front Door HTML error page with DNSNameNotResolved, indicating the backend service cannot be reached.
Error Details (Critical for Investigation)
Action name:
Get_insider_risk_management_case
Status code:
502 BadGateway
Power Automate error message:
The response is not in a JSON format.
Source (from raw outputs):
flow-apim-msmanaged-na-centralus-01.azure-apim.net
Inner error (raw output – HTML response):
- Azure Front Door error page returned instead of JSON
- Message:
“The service behind this page isn't responding to Azure Front Door.”
“Azure Front Door wasn't able to connect to the origin.”
Error Info:
DNSNameNotResolved
Client Request ID:
ba5c500f-a157-4c5b-a291-6ca022b915e0
Azure Front Door reference (x-azure-ref):
20260421T001812Z-1749fb74d86vxj5khC1SJCmt380000000p3g00000000dmrv
Environment ID:
default-94c3e67c-9e2d-4800-a6b7-635d97882165
Tenant ID:
94c3e67c-9e2d-4800-a6b7-635d97882165
Why We Believe This Is a Service-Side Issue
- The connector returns HTML content from Azure Front Door, not a structured JSON error.
- The error explicitly references DNSNameNotResolved and origin not responding, which indicates:
- A backend resolution/availability issue.
- Not an authentication, authorization, or request format issue.
- The flow was working before with the same configuration and inputs.
- Extensive retries over several hours did not recover.
Requested Action from Microsoft Support
We kindly request Microsoft to:
- Investigate backend logs for the provided
clientRequestId and x-azure-ref.
- Confirm whether there was:
- A regional outage,
- A service degradation, or
- A backend routing/DNS change affecting Insider Risk Management APIs.
- Advise whether this is:
- A known issue, or
- An isolated tenant/region problem.
- Provide guidance on:
- Expected recovery behavior, and
- Whether additional retry/backoff handling is recommended for this connector.
