Better pricing structure for API Management
We currently use 4 instances of APIM for duplicating our environments (Dev/UAT/Pre Prod and Production)
We went with APIM as a solution for fronting some azure services and some internal services. Due to the VPN access only being available on Premium we are paying for over 32 Millions calls a day when we will barely generate a 1 Million. So we have 4 Premium APIM instances costing us £6000 a month purely for the VPN access. Forcing us to pay for a level we do not require just for a feature of the environment, it would be better if the VPN option was addon rather than forcing customers to pay up front for massive usage they don't require
We are working on adding VNET capability to the developer tier and it looks like this should solve your problem since you will be able to use developer tier instances for non-production environments.
David GROSPELIER commented
This topic is in the status "started" for 4 years... is it really started?
As mentioned in all comments here, customers are wondering to have more features in the Standard tier, in particular the VNet support and the Self-Hosted API Gateway.
Manish Jain commented
Need consumption plan with all features enabled. And/Or need to be able to start/stop APIM.
Markus Konrad commented
Pushing this topic again.
Yes, VNET and AD in Dev plan is nice (we are using it) but still not an attractive solution for most customers. It gives the customer the impression that the Azure offering pricing model is extremely strange and kind of unfair (yes, start with it, like it but pay 4-5 times the price if you figure out it fits your needs).
We also dont need many requests/minute but we want to use the Policy stuff and Backend communication via AD etc...
Stefan Sipola commented
Vnet in the dev tier does not solve the problems with the production environments. The cost from Standard to Premium is 4x as high and the cost from Basic to Premium is 20x as high. For what? To allow us to integrate with our other paid Azure services?
Consumption didn't solve these issues either since it still doesn't allow us the AAD integration nor the Vnet integration that we need.
We don't need to make 1 billion requests, we need to be able to secure our solutions within our private environment.
This is by far the one of the best but most frustrating of Azure product offerings. I just cannot get my clients to pay for the 1 feature that they require, being Vnet integration at the premium cost. This pricing structure is something that is quite weird compared to other product offerings where the performance and scale drives up the cost, not so much features.
We utilize API management a lot as a way into a back-end but always have to come up with alternatives when the cost hits the fan
Any update ?
How much cost to Get Azure API?
Large scale dev commented
We dropped API management due to costs. It ate a significant amount of our operating profit from our e-commerce business site.
Simon Blandford commented
Having VNET and AAD integration on the Development tier is a dangerous resolution since it sets up a nasty trap for infrastructure design. Moving from development to production become extremely painful for anyone that didn't anticipate the pricing difference between Dev and Premium in advance.
I agree with many others that the VNET and AAD integration should be available to standard tier as well. Why should we pay for large scale instances like those of premium if we don't have the traffic needs at all. Shouldn't all APIs have option for maximum security.
It would be great to see a "per 1M requests" pricing or something similar
Joost Farla commented
VNet support should definitely be available for all subscription plans. I don't see why this is considered a premium feature. The price for premium is just crazy if you just want to publish an API with low usage rates in a secure manner.
Mikael Glentoft commented
I totally agree with previous people - paying for premium tier just cause we need the VPN and AAD feature is crazy! We just want to secure access to our API's, and having approx 5 requests / second we don't want to pay for a billion requests / second.
Oh Yan Ming commented
Are there any plans to introduce a new tier or make standard more flexible? I like the standard tier but it doesnt support VNET integration which should come off as a basic feature.
Mathias Nilsson commented
Would much rather pay for number of requests being made and features we use. Premium is too expensive, standard lacks functionality and developer is not an option in production.
Ian Bennett commented
The APIM pricing model feels more like a third party add-on than an integrated Azure offering. Vnet and AAD integration should be standard with pricing based just on scaling.
Henrik Åberg commented
Agreed. The pricing model for APIM with three fixed levels is way too blunt and not very cloud oriented. AWS and Google charges $3-$3.50 per 1M API calls which is way more flexible.
Muhammad Haroon - ZehnLabs commented
I agree. The APIM pricing is not very well thought out and a bit too restrictive, especially at the Developer level. For a company that's just starting out in the web service space, the Developer level makes most economical sense, however, no SLA whatsoever and restrictions on number of calls and data transfer are too prohibitive. I think the current Developer level should be offered at half the price for testing purposes, and a Standard level should be introduced at the $49 price point with at least some SLA and better data transfer and calls rate.
Darren Kay commented