Release - API Management service: May, 2021

A regular Azure API Management service update was started on May 5, 2021, and included the following new features, bug fixes, and other improvements. It may take several weeks for your API Management service to receive the update.

Featured

1. Open-source API Portal is now generally available.
2. Azure API Management's support for Availability Zones is now generally available.
3. Request and response validation policies are now generally available.

New

1. You can now validate the client certificate with the new <validate-client-certificate> policy. Documentation and support in the Azure portal are coming soon.
2. The Visual Studio Code extension now supports policy debugging for self-hosted gateways running locally.
3. The Visual Studio Code extension now supports Dapr and validation policies.
4. The developer portal now supports resource owner password grant flow.
5. The new Ciphers + Protocols page in the Azure portal lets you manage API gateways' cipher and protocol configuration and displays a warning if a weak cipher or protocol is enabled.
6. The Locations page in the Azure portal lets you now configure Availability Zones.
7. You can now apply validation policies with the visual policy editors in the Azure portal, without writing any policy code.
8. The timeout attribute of the send-request policy now supports policy expressions.

Fixed

1. Caching issues, which might have resulted in a broken developer portal's administrative interface, are now resolved.

Changed

1. The client certificate renegotiation feature is now disabled for all new and existing API Management services, except for the services that relied on it in the last 30 days (services with at least one API call that resulted in a client certificate request from a policy, not as part of an initial TLS handshake). The API gateway will request a client certificate only if HostnameConfiguration's property negotiateClientCertificate is set to true. If the property is set to false, the client certificate won't be available in the context.Request.Certificate property.

Release - self-hosted gateway: 1.2.1

Release - self-hosted gateway: 1.2.1

April 22, 2021

New stable version of the self-hosted gateway is now available. Full list of container versions can be found here.

New

None

Bug fixes

• Plugged a memory leak in the backend response content processing logic.

Breaking changes

None

Release - developer portal: 2.9.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.2.0

Release - self-hosted gateway: 1.2.0

April 20, 2021

New stable version of the self-hosted gateway is now available. Full list of container versions can be found here.

New

1. Support for Kubernetes Ingress object - see https://github.com/Azure/api-management-self-hosted-gateway-ingress.

Bug fixes

None

Breaking changes

None

Release - API Management service: March, 2021

A regular Azure API Management service update was started on March 8, 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.

Featured

1. Integration of named values with Azure Key Vault is now generally available.
2. Integration of certificates with Azure Key Vault is now generally available.
3. Visual Studio Code extension is now generally available.
4. API Management diagnostics are now in public preview.

New

1. You can now add an Application Insights logger by specifying a connection string. Support for this feature in the Azure portal is coming soon.

Fixed

1. List, GET, PUT, and PATCH operations on named values managed in a key vault are no longer allowed in API versions prior to 2020-06-01-preview. Those named values will no longer be exported in ARM templates.
2. Recreating a user-assigned managed identity with the same Azure resource ID no longer results in an error.

Changed

1. Metrics and monitoring endpoints now use a new DNS service with higher availability. If you have been using the hostname to filter the traffic, make sure to change it to the new address. Otherwise, no action is required; the IP address of the resources has not changed.
   • https://global.metrics.nsatc.net/ has changed to https://global.prod.microsoftmetrics.com/.
   • https://prod3.metrics.nsatc.net:1886/RecoveryService has changed to https://prod3.prod.microsoftmetrics.com:1886/RecoveryService.
2. Managed identity no longer requires outbound access to Certificate Revocation List endpoints. If you have configured network connectivity to allow outbound traffic to CRL endpoints, you may now remove this dependency.

Release - developer portal: 2.8.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 - developer portal: 2.7.1

A new developer portal version has just been released. It addresses security vulnerabilities introduced in version 2.7.0.

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.3

Release - self-hosted gateway: 1.1.3

February 18, 2021

New stable version of the self-hosted gateway is now available. Full list of container versions can be found here.

New

1. Updated with support for Dapr 1.0 release.

Bug fixes

None

Breaking changes

None

Release - developer portal: 2.7.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 - 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

1. You can now use the cache-response attribute in the cache-store policy to specify when to cache the outgoing HTTP response. For example, <cache-store cache-response="@{return true}" /> will cache all API responses. If the cache-response attribute isn't specified, only HTTP responses with the status code 200 OK will be cached. Documentation will be updated soon.
2. You can now view service summary, explore service recommendations, and access additional resources in the redesigned overview page in the Azure portal.
   
3. You can now use the isKeyVaultRefreshFailed=true query 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.
4. 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

1. We fixed an error, which could cause named values and certificates stored in Azure Key Vault to not be refreshed.