How can we improve Azure API Management?

Allow Specifying Scope for Properties

It's great that there's properties that can then be referenced within policies without hard coding them in. It should provide added flexibility when the properties are maintained in one place. However, as it currently stands, all of the properties are global which makes them inherently hard-coded anyway.

Being able to specify the scope of a property in the publisher portal should provide even more flexibility.

--------------------

Global Scoped Properties: As the properties currently are. I can as an admin go into the publisher portal and specify a global property value.

User Scoped Properties: A user could set the value in their own profile.

Subscription Scoped Properties: A subscriber could set the property value in their subscriptions list. Currently they can only change the subscription name.

--------------------

In the publisher portal, under Properties, there currently is Tags, Name and Value. We would need an additional column with a dropdown from which we could choose the Scope of the property. Which would default to the current "Global" scope to avoid breaking anything existing.

4 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Jani Hyytiäinen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
An error occurred while saving the comment
  • Jani Hyytiäinen commented  ·   ·  Flag as inappropriate

    Vladimir. I am referring to the developers who subscribe to products. They could set properties in their profile to configure their product. An example could be that someone makes a product in API Management for Visual Studio Team Services users who also use another system for project management. But when publishing the product, the publisher don't know which tenant the developers are going to be using. So the publisher could provide properties such as {{VstsTenant}} and {{BasecampTenant}} and the developer could set the properties to `myvso`and `mybasecamp` respectively without the publisher needing to overly complicate the APIs by having these parameters always present in the request.

Feedback and Knowledge Base