Azure API Management

Inside scoop from the API Management team

Release Notes – April 21, 2017

On Tuesday, April 21, 2017, we started deploying a regular service update. We upgrade production service instances in batches, and it usually takes about a week for the rollout to complete. Customers in the Central US EAUP region should have access shortly.

Below is the list of improvements and bug fixes in this release.

Updates and fixes

  • We improved the performance of the API documentation page
  • We improved the throughput of the log to Event Hub policy to up to 30 times
  • To comply with branding requirements, we replaced the word “Swagger” with “OpenAPI” in the download menu on Developer portal
  • We added an optional index attribute to the mocking policy to be used to identify a specific sample when more than one are provided for the same response code
  • We fixed the Facebook login problem caused by the retirement of v2.2 of the Facebook API
  • We fixed the Twitter login problem caused by the underlying ASP.NET library that used a wrong SSL certificate
  • We added requestId to request log entries, which uniquely identifies a request processed by API Management
  • We no longer send Content-Length header for HTTP methods that are not supposed to have a body, e.g. GET, HEAD
  • When updating the value of a property that is used in a policy, we now validate if the value is acceptable in the context of the policy
  • When the validate-jwt policy is configured to obtain signing keys from an Open ID Configuration endpoint, it will try to refresh the keys immediately if it gets a JWT signed by an unknown key
  • After evaluating the “condition” in the retry policy, the context.LastError property is reset to the value before entering the retry policy to prevent infinite loops