Azure API Management

Inside scoop from the API Management team

Release notes – August 10, 2016

On Wednesday, August 10, 2016, we started deploying a regular service update. Note that service instances are updated in batches and it will take a take a few days for the rollout to complete.

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

New features

Trace policy
Trace policy is simple but useful in debugging. It allows you to output arbitrary information into the API Inspector output. You can use it in any section as many times as you need to. Trace policies will execute only when tracing is triggered, i.e. Ocp-Apim-Trace header is present and set to true and Ocp-Apim-Subscription-Key header holds a valid key associated with administrative account. Here is what the policy looks like:

<trace source="source">output</trace>

Output could be a string literal or an expression of type string.

Updates and fixes

  • OData v4 filtering syntax support on all management API collections (e.g. /reports, /subscriptions) which leads to simpler looking URLs and ability to filter by enum valued fields (e.g. user state). Examples:

Before: /requests/byApi?$filter=timestamp ge datetime'2016-08-05T13:00:00Z' and timestamp le datetime'2016-08-05T14:00:00Z'

After: /requests/byApi?$filter=timestamp ge 2016-08-05T13:00:00Z and timestamp le 2016-08-05T14:00:00Z

Enum property filter: /users?api-Version=2014-02-14&$filter=state eq 'active'

  • 3x improvement in Git save and deploy operation performance
  • Message size limit in theLog to Event Hub policy is reduced to 200KB (from 256KB) to improve robustness of the feature
  • Policy validation logic now catches and properly deals with empty expressions, e.g. @() or @{}
  • Delegation key is not being saved to the Git repo anymore for obvious security reasons
  • Swagger/WADL download bug exposed by the recent Chrome update is fixed
  • We made improvements in gateway’s handling of client disconnects leading to improved stability and scalability