Azure APIM adds multi-provider model routing

Summary

Eliminates vendor lock-in at the API layer and collapses governance overhead. Teams mixing models across providers no longer need separate rate-limiting, content safety, and token accounting per backend.

Why it matters

Eliminates vendor lock-in at the API layer and collapses governance overhead. Teams mixing models across providers no longer need separate rate-limiting, content safety, and token accounting per backend.

Sources

1. 1.Unified Model API lets clients standardize on a single format, currently OpenAI Chat Completions, while APIM transparently transforms requests to the backend provider's native format
2. 2.every governance policy, rate limit, content safety check, and token metric applies consistently, regardless of which provider handles inference
3. 3.the policy buffers events in a sliding window and simply stops forwarding further events to the client without returning an error
4. 4.APIM now logs reasoning tokens, cached tokens, and audio tokens to Application Insights