@fool1241 Instead of creating operation-specific subscriptions and managing roles implicitly as such (illustrated in Idea B), I'd recommend that you implement your Idea A mainly because it uses the logical subscription-to-product concept built-in APIM for what they are for by design so it's more future-proof. Also, when leveraging policies, it wouldn't require duplicate API operations grouped by products as shown in the picture above. Did you have any specific concerns with Idea A?
In the following scenario, which unit is best to create a unit for an APIM product?
fool1241
81
Reputation points
In the following scenario, which unit is best to create a unit for an APIM product?
· Client system A and client system B outside Azure
Makes a request to the API via APIM.
-Users on client systems A and B have three roles: Admin, Writer, and Read.
In this case, which unit is best to create the product?
Accepted answer
-
Mike Urnun 9,811 Reputation points Microsoft Employee
2020-12-15T02:52:01.657+00:00