Azure API Management: Custom Policy for Rate Limiting optimization guide as Expected
I'm trying to implement a custom rate limiting policy in Azure API Management for my .NET Core Web API... My goal is to limit requests to a maximum of 100 requests per minute for each subscription key. However, it seems like the rate limiting is not being enforced as expected, and I'm still able to exceed the limit without receiving an behavior response. Here's the policy configuration I'm using: ```xml <policies> <inbound> <rate-limit-by-key calls="100" renewal-period="60" increment-by="1" counter-key="@(context.Subscription.Id)" /> </inbound> <backend> <forward-request /> </backend> <outbound> <set-header name="X-Rate-Limit" exists-action="override"> <value>100</value> </set-header> </outbound> </policies> ``` I've tested the policy by making requests from multiple clients with the same subscription key, yet I can still see responses beyond the 100 limit without any rejection or throttling. I verified that the subscription is active and the policy is attached to the correct API. To troubleshoot, I've looked at the logs in Azure API Management and did not find any related errors. I've also tried varying the `renewal-period` and `calls` attributes to see if that had any effect, but nothing changed. Could someone explain why the rate limiting isn't working as intended? Are there specific configurations or considerations I might be missing? Any guidance would be greatly appreciated! I've been using Xml for about a year now. Any ideas what could be causing this? Could this be a known issue?