A regular Azure API Management service update was started on September 7, 2022. It may take several weeks for your API Management service to receive the update.
Highlights
- Custom widget support in managed developer portal is now generally available.
- Expanded support for Azure Policy definitions for Azure API Management is now generally available.
- Support for OAuth 2.0 authorization code flow using PKCE for developer portal user sign-in and sign-up is now generally available.
New features, fixes, and improvements
- The new
allow-additional-propertiesattribute of thevalidate-contentpolicy lets you implement a runtime override of theadditionalPropertiesvalue configured in the JSON schemas - for example, to always prevent requests or responses with undefined schema properties, regardless of the JSON configuration. Documentation will be released soon in thevalidate-contentpolicy reference. - Account confirmation links in the account registration email notifications sent to developer portal users no longer include user ID and identity in the URL.
- We fixed an issue, where request and response validation policies would skip the
on-errorpolicy section if multiple validations failed. - Azure API Management no longer depends on the SMTP endpoints for sending email notifications and those endpoints can now be removed from the VNet configuration for allowed network traffic.
- We optimized performance of synthetic GraphQL APIs resolving multiple fields from the same endpoint.
- We fixed an issue, where using the developer portal test console configured with authorization code grant flow and OpenID Connect resulted in an error.
- We fixed an issue, where several properties in the "APIs - List By Service" management API response weren't propagated with values. The contract now follows the documented schema.
- We fixed an issue where an invalid request to create an API Schema could result in an
500 Internal Server Errorresponse. API Management now returns400 Bad Requestin such cases. - We fixed an issue, where an unsuccessful management operation on a policy fragment could result in failure of future management operations on that policy fragment.
- We fixed an issue, where built-in git repository export could fail.