Add support for Reserved IPs
At present API Management instance VIPs are static for the lifetime of that service instance with some exceptions, for example adding or removing a VNET (see http://aka.ms/apimfaq). Reserved IPs on the other hand are absolutely immutable and transcend service instance lifetime. They have an extra benefit of being used when accessing other Azure resources, e.g. storage, within the same region. See https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-public-ip/ for more information on Reserved IPs.
Thanks for the feedback – be great to get continued input on this. Keep the votes coming!
Adam Weigert commented
I'd also agree, if we could deploy an Azure Public IP as a reservation and then bind the service to that then we'd have further assurance that just redeploying or changing the networking wouldn't change the public IP.
I think this is less of an issue for internal vnets as I typically scope the entire subnet range for network ACLs.