Azure

How to fix rate limiting and throttling issues in Azure API Management

Understanding API Management Rate Limiting

Azure API Management (APIM) provides rate limiting and throttling policies to protect backend APIs from overload and enforce usage quotas. When these policies are misconfigured, legitimate requests get rejected with HTTP 429 (Too Many Requests) errors, or conversely, insufficient limits allow backends to be overwhelmed. This guide covers every aspect of APIM rate limiting.

Diagnostic Context

When encountering rate limiting and throttling issues in Azure API Management, the first step is understanding what changed. In most production environments, errors do not appear spontaneously. They are triggered by a change in configuration, code, traffic patterns, or the platform itself. Review your deployment history, recent configuration changes, and Azure Service Health notifications to identify potential triggers.

Azure maintains detailed activity logs for every resource operation. These logs capture who made a change, what was changed, when it happened, and from which IP address. Cross-reference the timeline of your error reports with the activity log entries to establish a causal relationship. Often, the fix is simply reverting the most recent change that correlates with the error onset.

If no recent changes are apparent, consider external factors. Azure platform updates, regional capacity changes, and dependent service modifications can all affect your resources. Check the Azure Status page and your subscription’s Service Health blade for any ongoing incidents or planned maintenance that coincides with your issue timeline.

Common Pitfalls to Avoid

When fixing Azure service errors under pressure, engineers sometimes make the situation worse by applying changes too broadly or too quickly. Here are critical pitfalls to avoid during your remediation process.

First, avoid making multiple changes simultaneously. If you change the firewall rules, the connection string, and the service tier all at once, you cannot determine which change actually resolved the issue. Apply one change at a time, verify the result, and document what worked. This disciplined approach builds reliable operational knowledge for your team.

Second, do not disable security controls to bypass errors. Opening all firewall rules, granting overly broad RBAC permissions, or disabling SSL enforcement might eliminate the error message, but it creates security vulnerabilities that are far more dangerous than the original issue. Always find the targeted fix that resolves the error while maintaining your security posture.

Third, test your fix in a non-production environment first when possible. Azure resource configurations can be exported as ARM or Bicep templates and deployed to a test resource group for validation. This extra step takes minutes but can prevent a failed fix from escalating the production incident.

Fourth, document the error message exactly as it appears, including correlation IDs, timestamps, and request IDs. If you need to open a support case with Microsoft, this information dramatically speeds up the investigation. Azure support engineers can use correlation IDs to trace the exact request through Microsoft’s internal logging systems.

Rate Limiting vs Quota Policies

Policy Purpose Reset Counter
rate-limit Limit calls per time window Sliding window Per subscription key
rate-limit-by-key Limit calls by custom key Sliding window Per custom expression
quota Limit total calls per period Fixed period (daily/weekly/monthly) Per subscription
quota-by-key Limit total calls by custom key Fixed period Per custom expression

Basic Rate Limiting

<!-- rate-limit: Fixed limit per subscription -->
<policies>
    <inbound>
        <!-- 100 calls per 60 seconds per subscription -->
        <rate-limit calls="100" renewal-period="60" />
        <base />
    </inbound>
</policies>

Common Mistake: Policy Placement

<!-- WRONG: rate-limit in outbound section has no effect -->
<policies>
    <outbound>
        <rate-limit calls="100" renewal-period="60" />
    </outbound>
</policies>

<!-- CORRECT: rate-limit must be in inbound section -->
<policies>
    <inbound>
        <rate-limit calls="100" renewal-period="60" />
        <base />
    </inbound>
</policies>

Rate Limiting by Custom Key

<!-- Rate limit per IP address -->
<inbound>
    <rate-limit-by-key 
        calls="50" 
        renewal-period="60" 
        counter-key="@(context.Request.IpAddress)" />
    <base />
</inbound>

<!-- Rate limit per user (from JWT claim) -->
<inbound>
    <rate-limit-by-key 
        calls="100" 
        renewal-period="60" 
        counter-key="@(context.Request.Headers.GetValueOrDefault("Authorization","").AsJwt()?.Claims["sub"].FirstOrDefault())" />
    <base />
</inbound>

<!-- Rate limit per API key header -->
<inbound>
    <rate-limit-by-key 
        calls="200" 
        renewal-period="60" 
        counter-key="@(context.Request.Headers.GetValueOrDefault("X-Api-Key","anonymous"))" />
    <base />
</inbound>

Quota Policies

<!-- Monthly quota per subscription -->
<inbound>
    <quota calls="10000" bandwidth="1073741824" renewal-period="2592000" />
    <base />
</inbound>

<!-- Daily quota by custom key -->
<inbound>
    <quota-by-key 
        calls="1000" 
        renewal-period="86400" 
        counter-key="@(context.Subscription.Id)" />
    <base />
</inbound>

The 429 Response

When rate limits are exceeded, APIM returns:

HTTP/1.1 429 Too Many Requests
Retry-After: 42
Content-Type: application/json

{
    "statusCode": 429,
    "message": "Rate limit is exceeded. Try again in 42 seconds."
}

Customizing the 429 Response

<!-- Custom error response for rate limiting -->
<inbound>
    <rate-limit-by-key 
        calls="100" 
        renewal-period="60" 
        counter-key="@(context.Request.IpAddress)"
        remaining-calls-header-name="X-RateLimit-Remaining"
        total-calls-header-name="X-RateLimit-Limit"
        retry-after-header-name="Retry-After" />
    <base />
</inbound>
<on-error>
    <choose>
        <when condition="@(context.Response.StatusCode == 429)">
            <return-response>
                <set-status code="429" reason="Too Many Requests" />
                <set-header name="Content-Type">
                    <value>application/json</value>
                </set-header>
                <set-body>@{
                    return new JObject(
                        new JProperty("error", "rate_limit_exceeded"),
                        new JProperty("message", "You have exceeded the rate limit. Please try again later."),
                        new JProperty("retry_after_seconds", context.Response.Headers.GetValueOrDefault("Retry-After", "60"))
                    ).ToString();
                }</set-body>
            </return-response>
        </when>
    </choose>
</on-error>

Root Cause Analysis Framework

After applying the immediate fix, invest time in a structured root cause analysis. The Five Whys technique is a simple but effective method: start with the error symptom and ask “why” five times to drill down from the surface-level cause to the fundamental issue.

For example, considering rate limiting and throttling issues in Azure API Management: Why did the service fail? Because the connection timed out. Why did the connection timeout? Because the DNS lookup returned a stale record. Why was the DNS record stale? Because the TTL was set to 24 hours during a migration and never reduced. Why was it not reduced? Because there was no checklist for post-migration cleanup. Why was there no checklist? Because the migration process was ad hoc rather than documented.

This analysis reveals that the root cause is not a technical configuration issue but a process gap that allowed undocumented changes. The preventive action is creating a migration checklist and review process, not just fixing the DNS TTL. Without this depth of analysis, the team will continue to encounter similar issues from different undocumented changes.

Categorize your root causes into buckets: configuration errors, capacity limits, code defects, external dependencies, and process gaps. Track the distribution over time. If most of your incidents fall into the configuration error bucket, invest in infrastructure-as-code validation and policy enforcement. If they fall into capacity limits, improve your monitoring and forecasting. This data-driven approach focuses your improvement efforts where they will have the most impact.

Backend Throttling (Downstream 429)

When your backend API returns 429, implement retry logic in APIM:

<!-- Retry on backend 429 responses -->
<backend>
    <retry condition="@(context.Response.StatusCode == 429)" 
           count="3" 
           interval="@{
               var retryAfter = context.Response.Headers.GetValueOrDefault("Retry-After", "1");
               return int.TryParse(retryAfter, out int seconds) ? seconds : 1;
           }"
           first-fast-retry="false">
        <forward-request />
    </retry>
</backend>

Product-Level Rate Limits

# Create products with different rate limits
# Free tier
az apim product create \
  --resource-group myRG \
  --service-name myAPIM \
  --product-id free-tier \
  --title "Free Tier" \
  --subscription-required true \
  --approval-required false \
  --subscriptions-limit 1

# Premium tier  
az apim product create \
  --resource-group myRG \
  --service-name myAPIM \
  --product-id premium-tier \
  --title "Premium Tier" \
  --subscription-required true \
  --approval-required true
<!-- Apply different limits based on product -->
<inbound>
    <choose>
        <when condition="@(context.Product?.Id == "free-tier")">
            <rate-limit calls="10" renewal-period="60" />
            <quota calls="1000" renewal-period="2592000" />
        </when>
        <when condition="@(context.Product?.Id == "premium-tier")">
            <rate-limit calls="1000" renewal-period="60" />
            <quota calls="100000" renewal-period="2592000" />
        </when>
        <otherwise>
            <rate-limit calls="5" renewal-period="60" />
        </otherwise>
    </choose>
    <base />
</inbound>

Sliding Window vs Token Bucket

APIM supports different rate limiting algorithms (available in newer API versions):

<!-- Token bucket algorithm (smoother, allows bursts) -->
<rate-limit-by-key 
    calls="100"
    renewal-period="60"
    counter-key="@(context.Request.IpAddress)"
    increment-condition="@(context.Response.StatusCode >= 200 && context.Response.StatusCode < 400)" />

Error Classification and Severity Assessment

Not all errors require the same response urgency. Classify errors into severity levels based on their impact on users and business operations. A severity 1 error causes complete service unavailability for all users. A severity 2 error degrades functionality for a subset of users. A severity 3 error causes intermittent issues that affect individual operations. A severity 4 error is a cosmetic or minor issue with a known workaround.

For rate limiting and throttling issues in Azure API Management, map the specific error codes and messages to these severity levels. Create a classification matrix that your on-call team can reference when triaging incoming alerts. This prevents over-escalation of minor issues and under-escalation of critical ones. Include the expected resolution time for each severity level and the communication protocol (who to notify, how frequently to update stakeholders).

Track your error rates over time using Azure Monitor metrics and Log Analytics queries. Establish baseline error rates for healthy operation so you can distinguish between normal background error levels and genuine incidents. A service that normally experiences 0.1 percent error rate might not need investigation when errors spike to 0.2 percent, but a jump to 5 percent warrants immediate attention. Without this baseline context, every alert becomes equally urgent, leading to alert fatigue.

Implement error budgets as part of your SLO framework. An error budget defines the maximum amount of unreliability your service can tolerate over a measurement window (typically monthly or quarterly). When the error budget is exhausted, the team shifts focus from feature development to reliability improvements. This mechanism creates a structured trade-off between innovation velocity and operational stability.

Dependency Management and Service Health

Azure services depend on other Azure services internally, and your application adds additional dependency chains on top. When diagnosing rate limiting and throttling issues in Azure API Management, map out the complete dependency tree including network dependencies (DNS, load balancers, firewalls), identity dependencies (Azure AD, managed identity endpoints), and data dependencies (storage accounts, databases, key vaults).

Check Azure Service Health for any ongoing incidents or planned maintenance affecting the services in your dependency tree. Azure Service Health provides personalized notifications specific to the services and regions you use. Subscribe to Service Health alerts so your team is notified proactively when Microsoft identifies an issue that might affect your workload.

For each critical dependency, implement a health check endpoint that verifies connectivity and basic functionality. Your application’s readiness probe should verify not just that the application process is running, but that it can successfully reach all of its dependencies. When a dependency health check fails, the application should stop accepting new requests and return a 503 status until the dependency recovers. This prevents requests from queuing up and timing out, which would waste resources and degrade the user experience.

Monitoring Rate Limiting

# Check APIM metrics for throttled requests
az monitor metrics list \
  --resource $(az apim show --name myAPIM --resource-group myRG --query id -o tsv) \
  --metric "FailedRequests" \
  --filter "HttpStatusCodeCategory eq '4xx'" \
  --interval PT1H

# Set up alert for excessive 429 responses
az monitor metrics alert create \
  --name throttle-alert \
  --resource-group myRG \
  --resource $(az apim show --name myAPIM --resource-group myRG --query id -o tsv) \
  --condition "total FailedRequests > 100" \
  --window-size 5m \
  --evaluation-frequency 5m
-- KQL: Analyze throttled requests
ApiManagementGatewayLogs
| where ResponseCode == 429
| summarize 
    ThrottledCount = count(),
    UniqueClients = dcount(CallerIpAddress)
    by bin(TimeGenerated, 5m), ApiId
| order by TimeGenerated desc
| render timechart

Client-Side Handling

// JavaScript: Client-side retry with Retry-After header
async function callApiWithRetry(url, options = {}, maxRetries = 3) {
    for (let attempt = 0; attempt <= maxRetries; attempt++) {
        const response = await fetch(url, options);
        
        if (response.status === 429) {
            const retryAfter = parseInt(response.headers.get('Retry-After') || '5');
            console.log(`Rate limited. Retrying in ${retryAfter}s (attempt ${attempt + 1})`);
            await new Promise(resolve => setTimeout(resolve, retryAfter * 1000));
            continue;
        }
        
        return response;
    }
    throw new Error('Max retries exceeded');
}

Troubleshooting Checklist

  • Check policy scope — Rate limits at API level override product level
  • Verify counter key — Empty keys cause all requests to share one counter
  • Check policy inheritance — <base /> includes parent policies
  • Review Retry-After header — Tells clients when to retry
  • Monitor remaining calls header — Shows how close to the limit
  • Test in Developer Portal — Use try-it feature to verify limits
  • Check multi-region sync — In Premium tier, counters may not sync instantly across regions

Post-Resolution Validation and Hardening

After applying the fix, perform a structured validation to confirm the issue is fully resolved. Do not rely solely on the absence of error messages. Actively verify that the service is functioning correctly by running health checks, executing test transactions, and monitoring key metrics for at least 30 minutes after the change.

Validate from multiple perspectives. Check the Azure resource health status, run your application’s integration tests, verify that dependent services are receiving data correctly, and confirm that end users can complete their workflows. A fix that resolves the immediate error but breaks a downstream integration is not a complete resolution.

Implement defensive monitoring to detect if the issue recurs. Create an Azure Monitor alert rule that triggers on the specific error condition you just fixed. Set the alert to fire within minutes of recurrence so you can respond before the issue impacts users. Include the remediation steps in the alert’s action group notification so that any on-call engineer can apply the fix quickly.

Finally, conduct a brief post-incident review. Document the root cause, the fix applied, the time to detect, diagnose, and resolve the issue, and any preventive measures that should be implemented. Share this documentation with the broader engineering team through a blameless post-mortem process. This transparency transforms individual incidents into organizational learning that raises the entire team’s operational capability.

Consider adding the error scenario to your integration test suite. Automated tests that verify the service behaves correctly under the conditions that triggered the original error provide a safety net against regression. If a future change inadvertently reintroduces the problem, the test will catch it before it reaches production.

Summary

APIM rate limiting issues usually stem from misconfigured policies (wrong section placement, empty counter keys), overly restrictive limits for legitimate traffic, or missing client-side retry logic for 429 responses. Use rate-limit-by-key for per-client limiting, implement product-level tiers for different usage plans, add the remaining-calls-header-name attribute so clients can self-throttle, and always configure retry logic for both client-to-APIM and APIM-to-backend 429 responses.

For more details, refer to the official documentation: What is Azure API Management?, Policies in Azure API Management.

Leave a Reply