Workspaces in Azure API Management let platform teams hand off API ownership to individual API teams while keeping centralized governance. Until now, using them meant deploying a dedicated workspace gateway on the Premium tier — adding cost, operational overhead, and limiting regional availability.
That requirement is going away. Workspaces can now be associated directly with the built-in gateway, and this capability is generally available.
What changes
- Available in more tiers. Use workspaces on the built-in gateway in any API Management tier except Consumption.
- Available in every region. Create workspaces in any region where API Management is supported.
- All built-in gateway capabilities apply. Workspaces deployed with the built-in gateway inherit features that dedicated workspace gateways don't offer today, including multi-region deployments, custom hostnames, and Private Link connectivity.
Availability
Rolling out now to v2 tiers, with Azure portal UI support expected around July. Rollout to classic tiers (Developer, Basic, Standard, Premium) will begin by August and may take up to a few months to complete.
Get started
Learn more about workspaces and how to deploy them on the built-in gateway.
Updated Jun 02, 2026
Version 1.0budzynski
Microsoft
Joined October 13, 2021
Azure Integration Services Blog
Follow this blog board to get notified when there's new activity