‼️ Breaking changes ‼️
- On June 14, 2024, we’re introducing breaking changes to the Workspaces feature. You may have to take action to continue using workspaces beyond June 14, 2024.
New features, improvements, and changes
- We’ve introduced several new features and improvements to workspaces:
- You can now create and manage certificates, backends, diagnostics, and loggers inside a workspace with the
2023-09-01-preview
management API version.Azure portal interface will be released soon. - You can now use
context.Workspace
in policy expressions. - "default-workspace" is now a reserved workspace resource name.
- You can now create and manage certificates, backends, diagnostics, and loggers inside a workspace with the
- We now preserve the
format
andschema
properties of the form-data parameters when importing OpenAPI APIs. - HTTP version information will now be included in the request trace.
- We’ve added support for HS512 and RS512 algorithms in the
validate-jwt
policy. client-application-ids
element is now optional invalidate-azure-ad-token
policy.- We've made a couple improvements to the GraphQL support:
- We've added support for Union Type in GraphQL resolvers
- Arrays can now be used within the
set-body
policy to project the data obtained by a resolver onto the list of primitive data types specified in the GraphQL schema
- An Azure Advisor notification will be sent to customers when they inadvertantly delete the FQDN property from the public IP resource assigned to API Management.
- We've made several improvements to the VNet integration in the Standard v2 tier:
- We will now detect if the prerequisites for VNet integration are not being met - i.e., subnet delegation and service association link, and fail the deployment faster.
- All traffic from the VNet-integrated Standard v2 service instances to the Internet will be now routed via the integrated VNet.
- The outbound IP will now be populated and shows its respective value.
Fixes
- We’ve resolved the issue where Azure API Management would incorrectly log requests that were rejected due to public network access is disabled. This fix ensures that logs and metrics in Azure Monitor now exclude these rejected requests when API Management is set up with a private endpoint.
- An attempt to create diagnostics in a workspace that doesn't exist will now return a
404 Not Found
error. Previously, API Management returned a500 Internal Server Error
response. - Workspace users can no longer override diagnostics settings defined for all APIs on the service level.
- Exporting APIs with empty or whitespace-only examples no longer produces an error.
- Optional string query parameters are no longer added to the API operation's URL template.
-$DevPortalUrl
variable in the developer welcome email template now returns a new developer portal URL. Previously, it returned a legacy developer portal URL. - The
authenticate-certificate
policy now performs a case-sensitive certificate ID validation. Previously, request processing would fail when the casing between the certificate ID in the policy and in the request didn’t match. - We've fixed an issue preventing recovery of the soft-deleted Basic v2 and Standard v2 service instances.