Azure API Management update—September 2019

A regular Azure API Management service update was started on September 23, 2019, that included the following bug fixes, changes, and new features, along with other improvements. Please note that we deploy updates gradually and it takes over a week for every active API Management service instance to receive them.

New

1. Network status management API call returns status for SMTP Relay and Metrics and Health Monitoring, which can be used to check the connectivity of API Management services in Virtual Network.
2. The set-body policy also accepts byte array as body content.
3. API Management now supports dedicated schema in Azure Monitor logs. Documentation and sample queries are coming soon.

Fixed

1. API Management now offers better protection against cross-site scripting attacks.
2. The developer portal’s console now supports $$ strings in the request body (previously truncated to single $).
3. OpenAPI import and export has been improved.

Changed

1. Management API calls, which are throttled by the underlying database, now return a 429 “Too Many Requests” response with the body { "code" : "TooManyRequests" }. Previously, they were failing with the 500 “Internal Server Error” status code.
2. Consumption tier services now don’t allow for adding a custom domain without a CNAME record or with an invalid CNAME record. Previously, the service was failing with 400 “Bad Request” responses on runtime.
3. The client SDKs for API Management have been updated: PowerShell, .NET, Python, TypeScript, Go, Java, and Ruby.

New developer portal (in preview) follows an independent release lifecycle and the per-release changelog is available on GitHub.