In order to invoke Management REST API endpoint (like ***.management.azure-api.net/apis?api-version=vvv) from browser's JS code, CORS headers should be enabled there. Moreover, full Management REST API endpoint configuration (thru Azure portal) is very welcomed addition.11 votes
Thanks for the feedback. Can you provide more details on the scenario, e.g., why do you need to call the management API from js code in browser.
Also, you can put the management API behind the gateway and add a CORS policy.
Could you support wildcard in the url of backend entity?
"url": "<a rel="nofollow noreferrer" href="https://abc.contoso.com/"">https://abc.contoso.com/"</a>,
What are you trying to achieve? Backend URL is used by the forward request policy and it will fail when presented with such a URL.
Ability to read certificates stored under secrets in APIM is required. If Certificate is created using App Service Certificate, certificate is getting stored under secrets. APIM in ability to read certificate under secrets of Key vault is becoming bottleneck for us.3 votes
Thank you for the feedback. Are you referring to custom domain certificates stored in Azure Key Vault? If so, APIM can already use them.
Currently the 'Capacity' metric for the Azure API Management service only supports an aggregation type of of 'Average'.
WIth the ability to calculate the capacity to a percentage, it would be very beneficial to have an alternate metric or second aggregation type for 'Maximum' for the capacity metric to show at a glance what remaining availability is.1 vote
Thank you for the feedback, Winter. It would help if you can explain how do you expect Maximum aggregation to work and be used for assessing remaining capacity.
- Don't see your idea?