MicrosoftGreat announcement and very interesting direction for governing models and MCP servers.
One question regarding adoption: for organizations that already have Azure API Management instances in production, is AI Gateway intended to be deployed as a separate resource, or is there a planned path to leverage existing APIM instances for AI Gateway workloads?
Understanding the recommended coexistence and migration model would help platform teams evaluate adoption strategies and operational ownership.
I doubt AI Gateway with it's limited capabilities in a position to warrant a migration, both going to be needed.
APIM has robust capabilities and i wish, many of them find their way to AI gateway so all combinations possible; APIM+/- AI Gateway .
MicrosoftThat's the plan. Thanks!
are there any timelines available when cost/policies (other than available now within the gatewya portal) etc are added to the AI Gateway so something like budgeting/limiting per team can be incorporated. The preview is limited in the sense that everybody having a key to the gateway can use all models available for that gateway.
So a bit what
From Multi-Model Chaos to a Governed AI Gateway: Cost Optimization on Azure | Microsoft Community Hub is trying to achieve.
