Azure API Management
Managed API gateway with policy-based throttling, auth and transformation.
- Provider
- azure
- Kind
- API gateway
- Category
- Edge
- Also known as
- APIM
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| auth | enum | none | api-key | jwt | oauth2 | mtls | no | none | inherited |
| concurrencyLimit | boolean | — | no | false | inherited |
| genAiGateway | boolean | — | no | false | inherited |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | inherited |
| rateLimiting | boolean | — | no | false | ▸ false |
| tier | enum | consumption | developer | basic | standard | premium | no | developer | inherited |
| tls | boolean | — | no | true | ▸ true |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
sync-chain-too-deep
Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.
- — all of these hold:
- — the design requirement `latency.p95Ms` has a value
- — the longest chain of synchronous calls starting at the node is more than 3 hops long
nodes:
- { id: "api-management", component: "azure-api-management" }API Gatewayalibaba-api-gatewayAmazon API Gatewayaws-api-gatewayAWS AppSync GraphQL APIaws-appsyncAI Gatewaycloudflare-ai-gatewayCloudflare API Shieldcloudflare-api-shieldMCP Server Portalcloudflare-mcp-portalCloudflare Privacy Gatewaycloudflare-privacy-gatewayGeneric API gatewayapi-gatewayApache APISIXapisixApollo GraphOSapollo-graphosEasegresseasegressEmissary-ingressemissaryEnvoy Gatewayenvoy-gatewayGloo GatewayglooHasurahasuraHelicone AI Gatewayhelicone-gatewayHigresshigressKong GatewaykongKong AI Gatewaykong-ai-gatewayKong Konnectkong-konnectKrakenDkrakendLiteLLM ProxylitellmMartian GatewaymartianNot Diamondnot-diamondPortkey AI GatewayportkeyRequestyrequestySpring Cloud Gatewayspring-cloud-gatewayTyk GatewaytykUnifyunify-aiVercel AI Gatewayvercel-ai-gatewayWSO2 API Managerwso2-api-managerZuulzuulApigeeapigeeAgent Gatewaygoogle-agent-gatewayAPI Gatewaygoogle-api-gatewayApigee hybridgoogle-apigee-hybridCloud Endpointsgoogle-cloud-endpointsFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Azure API Management: managed API gateway with policy pipeline. Rate limiting and auth are opt-in policies. # Per "AI gateway capabilities in Azure API Management", the GenAI gateway (token limits, semantic caching, # load balancing across model backends) is a set of policies you add, so genAiGateway starts off. schemaVersion: "1" type: "component" id: "azure-api-management" kind: "api-gateway" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/api-management/api-management-key-concepts" aliases: ["APIM"] defaults: managed: true tls: true rateLimiting: false properties: tier: type: "enum" values: ["consumption", "developer", "basic", "standard", "premium"] default: "developer" genAiGateway: type: "boolean" default: false