This chapter covers Azure API Management, a service for managing and exposing APIs. AZ-900 tests this under objective 2.2.
Jump to a section
A simple way to picture Azure API Management
A receptionist controls access to offices: screening visitors, logging who enters, directing traffic. API Management works similarly: it sits in front of APIs, controlling access, monitoring usage, and managing how external users interact with them.
What API Management does
API Management provides a centralized way to publish APIs, control access, monitor usage, and manage versioning — sitting between API consumers and backend services.
Common capabilities
Throttling (rate limiting), authentication, request/response transformation, analytics — features that would otherwise need to be built into every API individually.
Gateway role
API Management acts as a gateway: external consumers call the API Management endpoint, not the backend service directly, providing a layer of control and protection.
Create an API Management instance
An API Management service is created.
Import APIs
Existing backend APIs are registered with API Management.
Apply policies
Policies (throttling, auth, transformation) are configured.
Publish to developers
APIs are exposed to consumers through the API Management portal.
A company publishes its backend APIs through API Management, controlling rate limits, requiring API keys, and tracking usage without modifying the APIs themselves.
Objective 2.2 expects understanding of API Management as a gateway and control layer for APIs.
Common wrong answer: treating API Management as an API itself — it's a management layer in front of APIs.
Stable terms: API Management, gateway. Memory trick: API Management = control and management layer for APIs.
API Management provides a gateway and management layer for APIs.
Enables throttling, authentication, analytics without modifying backend APIs.
Sits between consumers and backend services.
Mistake
API Management replaces a backend API.
Correct
It sits in front of APIs, providing control and management without replacing them.
It's a service that sits between API consumers and backend services, providing control (throttling, authentication), monitoring, and management capabilities.
You've just covered Azure API Management — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?