How to troubleshoot API Not Found errors (404) in Azure API Management

Hari Prathipati Thanks for posting your question in Microsoft Q&A. From the description above, you have found some Not Found errors in APIM logs for some operations, but these operations are not configured and looking for the cause. As described in the doc: https://zcusa.951200.xyz/en-us/azure/api-management/api-management-howto-api-inspector#verify-allow-tracing-setting, you can enable trace setting for Built-in all-access subscription, and get the key for this subscription. Then make a test call to any of the URLs from Postman with header Ocp-Apim-Trace as true and Ocp-Apim-Subscription-Key with that key (built-in all-access subscription) and response header Ocp-Apim-Trace-Location will contain URL for the full trace information. The trace can help in finding the cause of the failure.

For example, if you see Unable to identify Api or Operation for this request. Responding to the caller with 404 Resource Not Found., APIM is unable to identify the API or Operation with suffix (like / or /login etc.) provided and this is expected. We have some predefined errors documented here and also some troubleshooting scenarios covered here.

I hope this helps and let me know if you have any questions.

If you found the answer to your question helpful, please take a moment to mark it as Yes for others to benefit from your experience. Or simply add a comment tagging me and would be happy to answer your questions.