Azure API Management update—February 2020

An Azure API Management service update was started on February 20^th, 2020, and included the following new features, bug fixes, and changes, along with other improvements.

New

• You can use the new logClientIp property in Diagnostics (global and API-level) to hide the client IP address in logs. IP addresses will be replaced with 0.0.0.0.
• You can now use the disableGateway property to disable API traffic in regional API gateways. For example:
  • After adding a new region, you can initially keep it disabled to first configure and test the regional backend service.
  • When a regional backend is impacted by a failure, you can disable the region to automatically redirect API requests to a healthy region.

This property is supported in 2019-12-01-preview API version and greater and it’s not supported in services deployed in internal virtual networks. You can’t disable all regions.
In the example below, the location “East US” has been disabled, but the primary location “West US” is still active.

• You can now monitor new GCS endpoint gcs.prod.monitoring.core.windows.net with the Network Status API to ensure connectivity if your service is deployed in a virtual network. Access to this endpoint is required for monitoring and logging features to work.
  The endpoint prod.warmpath.msftcloudes.com is going to be deprecated soon.

Fixed

• Client latency is no longer erroneously attributed to API Management latency in Azure Monitor logs.
• Consumption tier services no longer surface internal server error details to clients.

Changed

• Trace policy message and metadata fields can now return only strings – not any object type.
• Custom domain binding will be automatically removed from Consumption tier services on their activation if the attached certificate is expired.
• The subscriptionRequired property of an API object is now always returned in payload. Before, it could have been omitted if its value was true.

The developer portal follows an independent release lifecycle and the per-release changelog is available on GitHub.

Learn more