Hi @Eddie Vincent ,
Thanks for reaching out to Microsoft Q&A.
Yes, you can integrate Microsoft Entra Application Proxy with Azure APIM, and you can also combine APIM with Azure Application Gateway for secure and flexible API exposure.
Steps:
- Deploy APIM in Internal VNET mode.
- Deploy Application Gateway and add APIM to the backend pool.
- Configure routing rules, health probes, and optional SSL/TLS termination or path-based routing in the Application Gateway.
- Configure custom domains and DNS so the public App Gateway endpoint forwards traffic to APIM.
In APIM, configure the backend service using the Entra App Proxy external URL for your internal API.
Using this approach, internal APIs published through Entra App Proxy can be securely consumed via APIM, with the Application Gateway (WAF) providing the first security layer. This pattern is commonly used to protect internal services while enabling controlled external access.
>So I assume then if you have App gateway and WAF at the front end forwarding to APIM you would then simply set the App Proxy (Entra) external URL a backend service in APIM in this case?
Yes, correct. You would configure the Entra Application Proxy external URL as the backend service in APIM. This way, when a request comes through the App Gateway + WAF at the front end, it gets routed to APIM, which then forwards the request to the Application Proxy's published URL.
The Application Proxy will handle the connection to your on-premises applications, ensuring the traffic flow is secure and properly managed.
This setup allows you to expose internal APIs securely through APIM, while the Application Gateway provides the first layer of security with WAF.
Hope it helps!
Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you.