Releases: Azure/API-Management
Release - API Management service: January, 2021
A regular Azure API Management service update was started on January 21, 2021, and included the following new features and bug fixes, along other improvements. It may take several weeks for your API Management service to receive the update.
New
- You can now use the
cache-responseattribute in thecache-storepolicy to specify when to cache the outgoing HTTP response. For example,<cache-store cache-response="@{return true}" />will cache all API responses. If thecache-responseattribute isn't specified, only HTTP responses with the status code200 OKwill be cached. Documentation will be updated soon. - You can now view service summary, explore service recommendations, and access additional resources in the redesigned overview page in the Azure portal.

- You can now use the
isKeyVaultRefreshFailed=truequery parameter in the list certificates by service and list named values by service API calls in the API version 2020-06-01 or later to find the entities, for which the refresh from Azure Key Vault action failed. Documentation will be updated soon. - You can now monitor connectivity to Azure Key Vault using the network status endpoint in the API version 2020-06-01-preview or later.
Fixed
- We fixed an error, which could cause named values and certificates stored in Azure Key Vault to not be refreshed.
Release - developer portal: 2.6.0
A new developer portal version has just been released.
If you're using the built-in (managed) developer portal, your portal will be automatically upgraded within two weeks. Make sure to republish it to upgrade the published portal.
If you're using a self-hosted developer portal, you need to merge the source code changes and republish and redeploy your portal manually.
Detailed release notes are available in the developer portal repository.
Release - self-hosted gateway: 1.1.2
New stable version of the self-hosted gateway is now available. Full list of container versions can be found here.
New
None
Bug fixes
- Rate limit policy throttling at a lower than configured rate.
Breaking changes
None
Release - developer portal: 2.5.7
A new developer portal version has just been released.
If you're using the built-in (managed) developer portal, your portal will be automatically upgraded within two weeks. Make sure to republish it to upgrade the published portal.
If you're using a self-hosted developer portal, you need to merge the source code changes and republish and redeploy your portal manually.
Detailed release notes are available in the developer portal repository.
Release - API Management service: December, 2020
A regular Azure API Management service update was started on December 7, 2020, and included the following new features and bug fixes, along other improvements. It may take several weeks for your API Management service to receive the update.
New
- You can now create and manage API backends in the Azure portal.

- You can now log API inspector traces to Application Insights and Azure Monitor by setting the
verbosityproperty of theservice/diagnosticsresource todebug. Azure portal interface for this feature will be released in early 2021. - You can now mask or hide sensitive query parameters and headers in diagnostic logs. The
hidesetting will remove an entity, whilemasksetting will replace it with the word "hidden". Refer to theservice/diagnosticsAPI endpoint documentation for more details. Azure portal interface for this feature will be released in early 2021. - You can now monitor database connectivity in secondary regions in the
Network Statuspage in the Azure portal as well as via the respective API call, if your API Management service is deployed in multiple regions. - New management API version
2020-06-01-previewis now available for testing.
Fixed
- Elements of collections in responses from the
Content TypesandContent Itemsmanagement API endpoints no longer overlap between pages.
Release - developer portal: 2.5.6
A new developer portal version has just been released.
If you're using the built-in (managed) developer portal, your portal will be automatically upgraded within two weeks. Make sure to republish it to upgrade the published portal.
If you're using a self-hosted developer portal, you need to merge the source code changes and republish and redeploy your portal manually.
Detailed release notes are available in the developer portal repository.
Release - self-hosted gateway: 1.1.1
New stable version of the self-hosted gateway is now available. Full list of container versions can be found here.
New
None
Bug fixes
- TLS connection to upstream is unexpectedly terminated under certain conditions.
Breaking changes
None
Release - developer portal: 2.5.5
A new developer portal version has just been released.
If you're using the built-in (managed) developer portal, your portal will be automatically upgraded within two weeks. Make sure to republish it to upgrade the published portal.
If you're using a self-hosted developer portal, you need to merge the source code changes and republish and redeploy your portal manually.
Detailed release notes are available in the developer portal repository.
Release - developer portal: 2.5.4
A new developer portal version has just been released.
If you're using the built-in (managed) developer portal, your portal will be automatically upgraded within two weeks. Make sure to republish it to upgrade the published portal.
If you're using a self-hosted developer portal, you need to merge the source code changes and republish and redeploy your portal manually.
Detailed release notes are available in the developer portal repository.
Release - developer portal: 2.5.3
A new developer portal version has just been released.
If you're using the built-in (managed) developer portal, your portal will be automatically upgraded within two weeks. Make sure to republish it to upgrade the published portal.
If you're using a self-hosted developer portal, you need to merge the source code changes and republish and redeploy your portal manually.
Detailed release notes are available in the developer portal repository.