Feb 04 2020 10:21 AM - edited Feb 06 2020 11:00 AM
Hey all,
I am evaluating the API Management Consumption Tier plan to protect logic apps in a tenant. It looked very promising until it comes to the point of protecting the logic apps themselves and setting the restriction IP Addresses so that they can only be called via the API Management proxy.
The Consumption Tier does not include the ability to set static IP Addresses for the API Management service so it is not clear how to protect the logic app without adding actions to it. Yes, we could add actions to do a header check to each logic app, but I had hoped to avoid that.
Note that the published list of IP Address ranges for the API Management service in the given region does not include the client IP Address reported by the logic app. It was a generic "Azure cloud" IP address for that region. If we need to restrict based on that list, then the API Management service does us no good it just makes configuring the logic app harder.
Is there something else I'm missing, or is it not possible to use the Consumption tier to protect Logic Apps without adding some kind of check actions to the logic app itself?
Thanks,
Mary
Feb 07 2020 07:33 AM
So for anyone else researching this question, the "Consumption Tier" is a little bit "too good to be true". The IP Address will change (I have verified that). So there is no good way to protect the logic app via IP Address restriction to just the API Management instance without using at least the Developer tier.
Cheers,
Mary