Forum Discussion
Forward Request in API Management not working in Basic Tier but works in Consumption
Hoping this is the correct place to post this....
I am using the API Management police "Forward-Request" to extend the time out beyond 100 seconds. I have three environments - stage, train and live. In Stage and Train, the extended time out works by placing the policy appropriately in the "All Operations" section of the APIS. Both these environments are on the consumption tier.
Doing the same exact thing in our Live module, which is set to Basic Tier, the policy does not work. Has anyone else had this issue?
2 Replies
Refer here, please consider on Shorter Timeout and Buffer Seetings:
Azure API Management policy reference - forward-request | Microsoft Learn
The issue you're encountering is likely due to tier-specific limitations in Azure API Management. The Consumption tier allows for more flexible timeout settings (up to 180 seconds), whereas the Basic tier has stricter enforcement, with a default timeout of 240 seconds. This is likely why the forward-request policy works in your Consumption environments but not in Basic.
https://learn.microsoft.com/en-us/azure/api-management/api-management-features
Verify that the forward-request policy is correctly placed in the "All Operations" section.
<inbound> <base /> <forward-request timeout="300" /> </inbound>