Azure API Management update—May 2020
Published date: May 07, 2020
A regular Azure API Management service update was started on May 5, 2020, and included the following new features, bug fixes, and changes, along with other improvements. It may take more than a week for your API Management service to receive the update.
- API-scoped subscriptions are now also included in the API reports and, consequently, in the Analytics section of your API Management service in the Azure portal.
- The ability to publish the developer portal and check and apply CORS policy from the Portal overview section of your API Management service in the Azure portal is now available.
- If your API Management service is deployed in a virtual network, you can now explore the network connectivity status in the dedicated Network connectivity status section of your service in the Azure portal.
- Logging out of the developer portal cleans the browser’s cookie with the authentication token.
- Self-hosted API gateway hostnames are now included in the servers field of OpenAPI v3 definition when exporting an API.
- The developer portal loading time has been reduced thanks to additional caching.
- The ability to restore developer portal administrative session in a new browser’s tab is now available.
- The legacy developer portal now displays a message if the captcha service can't be reached (for example, if virtual network is misconfigured).
- Application Insights now always shows the correct number of errors if logging is enabled in API Management. Previously, the number was misreported when sampling was lower than 100 percent and the "Always log errors" flag was selected.
- You now have the ability to specify the subscription key header or query parameter name when importing an API using an ARM template. For example:
"name": "[concat(parameters('ApiManagement.Name'),'/', variables('ApiManagement.Api.Name'))]",
The developer portal follows an independent release lifecycle and the per-release changelog is available on GitHub.