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!
649 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.
14 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?
Is it possible to get an update with regards to this feature?
When I update an API and add release notes I want all subscribers to a product containing that API to receive an email notification.
10 votesJeroen de Sitter shared this idea ·
I apologize about the delay but Custom RBAC Support is now available in Production. You are able to to create role definitions at the MG scope and assign them to inherited MGs and Subs.
There is a bug that is in the portal where the new custom role is not showing when you are trying to do a role assignment on an inherited child MG/Sub. This should be resolved soon and PowerShell, CLI, and API are all working. I will not do any announcements yet on the availability of the feature until the portal bug is fixed. Once that is fixed we will do blog announcements and I will mark the feature complete here.