Azure API Management: 429 Too Many Requests with Custom Rate Limiting Policies
I've looked through the documentation and I'm still confused about I'm currently running into issues with Azure API Management where I am receiving a `429 Too Many Requests` behavior despite my custom rate limiting policies being configured... My API is supposed to allow 100 requests per minute per user, but it seems to be throttling users even when they are within the limit. I've implemented a policy in the API Management that looks like this: ```xml <inbound> <rate-limit-by-key calls="100" renewal-period="60" counter-key="@(context.Request.Headers.GetValueOrDefault("x-user-id", "default"))" /> </inbound> <backend> <forward-request /> </backend> <outbound> <send-response> <status-code>200</status-code> </send-response> </outbound> ``` I've verified the `x-user-id` header is correctly populated in the requests. Additionally, I've tested the API using Postman with multiple simulated users, and while the first few requests go through, it quickly starts returning the 429 behavior for other users. I also checked the Azure portal for the API Management service, and there are no other policies that could interfere. I tried adjusting the `renewal-period` to 30 seconds, but it didn't change the behavior. I also made sure that the policies are properly applied to the correct operation and not limited by a higher-level policy. Is there something I might be missing? Are there any best practices for configuring rate limiting policies to avoid these issues? Any insights would be appreciated! I'm working on a web app that needs to handle this. Is there a better approach? Any examples would be super helpful.