We will introduce a new version of the management API that would “hide” secrets from “reader” users. We will also introduce an explicit gesture to disable older versions of the API on a per API Management service instance basis.
any idea when you will introduce this?
Hi all – we could really use more information on the use cases you would like us to deliver with this feature. To quote Darrel’s post below:
Are you looking for some kind of UI in the portal to enable developers to subscribe to webhooks exposed by APIs?
Or are you looking for the additional security provided API Management to limit what events a user can subscribe to?
Do you want to correlate the API Management subscription ID with registered webhooks?
Any information you can give about the scenarios you would like help with would be great.
Thanks for the feedback!
658 votesplanned · 26 comments · API Management » API management experience · Flag idea as inappropriate… · Admin →
Any follow-up on this?
I want to be able to create a named value and store a secret that cannot be retreived by anyone. Right now these named values can be read by anyone in the portal. We want to make them completely invisible after they are filled out.
16 votes3 comments · Azure Active Directory » Role-based Access Control · Flag idea as inappropriate… · Admin →
Hi, thank you for your feedback. This is something we are discussing.
/Stuart and Balaji
any update on this?
When I update an API and add release notes I want all subscribers to a product containing that API to receive an email notification.
13 votesJeroen de Sitter shared this idea ·
Custom RBAC is supporting the management groups scope with a few limitations. The MG team and Identity teams are working on removing these limitations but no timeline is available yet.