A regular Azure API Management service update was started on October 31, 2022. It may take several weeks for your API Management service to receive the update.
Feature retirements
New features, fixes, and improvements
- You can now easily validate Azure Active Directory tokens on incoming requests with the new
validate-azure-ad-token
policy. Learn more in the documentation or blog post. - We fixed an issue, where API Management didn't allow clients to open new WebSocket connections even though they didn't exceed the connections limit.
- API Management updates are now rolled out to one Availability Zone at a time. Previously, updates were rolled out to multiple Availability Zones, reducing the service capacity by up to 50%.
- You can now use
cors
and caching policies (cache-store
andcache-lookup
) inside policy fragments. Previously thecors
policy inside policy fragments didn't correctly apply CORS configuration to the API; caching policies couldn't be configured due to an error. - API Management scale-out attempts that fail due to insufficient subnet capacity are now properly logged in Activity Logs.
- XML schema validation with
validate-content
policy no longer results in validation errors for elements with type "anyType". - The execution time of the
send-one-way-request
policy is no longer included in thebackendTime
metric in the diagnostic logs, since it's an asynchronous, non-blocking operation. Previously, it was included in thebackendTime
metric but excluded from thetotalTime
metric.