Update to Azure API Management Workspaces: Built-in Gateway and Tier Support Changes
budzynski announces changes to Azure API Management workspaces, focusing on updates to built-in gateway and tier support, and how these reversals affect existing and future deployment strategies.
Update to API Management Workspaces: Built-in Gateway & Tiers Support
Author: budzynski
Date: August 14, 2025
What’s Changing?
Azure is reintroducing support for workspaces on the built-in gateway in Azure API Management. This effectively rescinds some of the previously announced breaking changes. If your API Management service uses preview workspaces on the built-in gateway and meets the following tier-based limits, those workspaces will continue to function as-is and will automatically transition to general availability when the feature is announced.
Current workspace limits by API Management tier:
| API Management Tier | Max Workspaces on Built-in Gateway |
|---|---|
| Premium, Premium v2 | 30 |
| Standard, Standard v2 | 5 |
| Basic, Basic v2 | 1 |
| Developer | 1 |
Why This Change?
The workspace gateway requirement was introduced to increase reliability and scalability in large federated API environments. However, Microsoft recognizes that many customers have workflows depending on the preview workspaces model or need workspaces in non-Premium tiers. As a result, built-in gateway support is being kept available for these scenarios, within the stated limits.
What’s Not Changing?
Other workspace-related breaking changes remain. For example, service-level managed identities are still not available within workspaces. Premium and Premium v2 services continue to support deploying workspaces with dedicated workspace gateways.
Resources
For further discussion and official updates, follow the Azure Integration Services Blog.
This post appeared first on “Microsoft Tech Community”. Read the entire article here