Breaking Changes to Azure API Management Workspaces

As part of our commitment to enhancing workspaces (in Public Preview) within Azure API Management, we are implementing several critical breaking changes effective June 14, 2024. These changes are designed to streamline functionality and improve overall performance.  

These breaking changes will be effective from June 14, 2024. We strongly advise making any necessary adjustments to your workspace configurations before this date to ensure uninterrupted service. 

Breaking Changes: 

Change to Supported Service Tiers: Workspaces will no longer be supported in the Standard and Developer tiers. They will be available exclusively in the Premium tier. For availability in the v2 tiers, see Azure API Management v2 tiers. 

Changes to Support for Assigning Service-Level Entities in Workspaces: Several assignments of workspace entities to service-level entities will no longer be supported, including: 

• Assigning workspace APIs to service-level products 

• Assigning workspace APIs to service-level tags 

• Assigning workspace products to service-level tags 

• Assigning service-level groups to workspace products for visibility controls 

Please note that the built-in Guests and Developer groups will continue to be accessible within workspaces. 

Changes to Supported Context Objects: The following context objects will no longer be supported in workspace policies or in the all-APIs policy at the service level: 

• context.Api.Workspace 

• context.Product.Workspace 

Instead, utilize the context.Workspace object. 

You can still reference users from the service level in the context object within workspace-level policies. 

Help and Support: If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, create a support request. Please refer to the documentation for up-to-date information.