You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
Azure API Management (APIM) is a fully managed service for publishing, securing, transforming, and monitoring APIs. In a serverless architecture, APIM sits in front of your Azure Functions, Logic Apps, and other backend services, providing a unified API gateway with security policies, rate limiting, caching, and a developer portal.
Without an API gateway, each backend service exposes its own endpoint with its own authentication, rate limiting, and documentation. This leads to:
APIM solves these problems by providing a single entry point that applies consistent policies to all backend APIs.
APIM consists of three main components:
The runtime component that processes API calls:
The administrative interface for configuring APIs:
A customisable website for API consumers:
| Tier | Use Case | Gateway | Developer Portal | SLA |
|---|---|---|---|---|
| Consumption | Serverless, pay-per-call | Shared | No | 99.95% |
| Developer | Dev/test | Dedicated | Yes | No SLA |
| Basic | Small production | Dedicated | Yes | 99.95% |
| Standard | Medium production | Dedicated | Yes | 99.95% |
| Premium | Enterprise, multi-region | Dedicated | Yes | 99.99% |
The Consumption tier is the natural fit for serverless architectures — it scales automatically, charges per API call, and requires no infrastructure management.
An API in APIM is a collection of operations (endpoints). You can import APIs from:
A product is a package of one or more APIs offered to developers:
Subscriptions grant access to APIs through subscription keys:
# API call with subscription key in header
curl -H "Ocp-Apim-Subscription-Key: abc123..." \
https://my-apim.azure-api.net/api/users
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.