A regular Azure API Management service update was started on July 20, 2022. It may take several weeks for your API Management service to receive the update.
New features, fixes, and improvements
- We optimized the loading time of API schemas for management plane (including Azure portal) and developer portal operations.
- We increased the maximum length of each URL path segment from 520 to 1024 characters.
- We fixed an issue, where API Management allowed creation of multiple API versions with empty identifiers within one API version set.
- We fixed an issue, where API Management deserialized C-style hex strings in exported OpenAPI files as hex values.
- We fixed an issue, where API Management failed to export OpenAPI definitions if referenced schemas didn't have the
typename
property defined. - The
set-body
policy now supportsxsi-nil
attribute with two values ("blank"
and"null"
) for controlling how elements marked withxsi:nil="true"
are represented in XML payloads. If the value is set toblank
, API Management uses the prior behavior, where nil is represented as an empty string. If the value is set tonull
, nil is represented with a null value. - You can now monitor inbound connectivity to the API Management control plane in the "Network status" tab of the "Network" page in the Azure portal interface for your API Management service.
- Authorizations now support Salesforce, ServiceNow, Twitter, Stripe, and Zendesk identity providers.
- Authorizations now support PKCE authorization flow in the generic OAuth2 identity provider.
- Improvements to the GraphQL support:
- API Management now supports GraphQL requests with the content type
application/graphql
. Previously, such requests resulted in a400 Bad request
error. - GraphQL resolvers can now be configured in policy fragments for reuse in the
backend
policy section. - We fixed an issue, where creating a new GraphQL API using the property
format: graphql-format
resulted in failures in execution of the management API operations or ARM templates. This property worked only for existing GraphQL APIs. - We fixed an issue, where accessing
context.Request
in a synthetic GraphQL API'sset-graphql-resolver
policy would overwrite thecontext.Request
value. - We fixed an issue, where parsing of lists with scalar values resulted in runtime errors.
- API Management now supports GraphQL requests with the content type
Developer portal releases
Self-hosted gateway container image releases
Browse the recently added release notes for older images: