Support VNET for Basic Tier of APIM
Our APIs are deployed to Service Fabric cluster in a VNET. If we want to expose our APIs through APIM, we have to use the Premium Tier of APIM since that's the only tier where VNET support is included.
Premium Tier of APIM has bunch of other features like AD authentication, Multi-region support, 4000 reqs/sec etc., which we don't need and don't care.
Why are all those features clubbed together and provided as an all or nothing solution?
Basic Tier fits our use case perfectly, if only we can deploy it in a VNET.
Service Fabric integration with APIM is one of it's coolest features and can help in it's adoption. But Microsoft strategy of artificially inflating the pricing and forcing customers to pay for features they don't need isn't going to work well.
Right now, the only way to use Service Fabric in production with APIM is to pay $7000 per cluster. Think about it for a minute.Yes, there are other ways to implement APIM but any advantage Service Fabric has over Kubernetes or Docker swarm is being thrown away. The pricing level will deter most customers from even trying the platform.
It's a cool integration but out of reach of most people!
Jorge Galrito commented
I agree. I really would like to use API Management but Premium is very expensive and I can't justify that cost.
Asif Ali commented
Any update on this?
This is under review from May 2018, this means they don't consider this. Nobody should be surprised by this. Well done Microsoft !!!
This is one the biggest concern with respect to having security but unable to achieve it because of expense plan cost by azure.
What is the use of VNET on developer mode if it not available on standard plan. Not everyone will use premium plan.
At least make it available for standard plan.
The following requirement is pending from past 2 years from azure.
Nathan Becker commented
Add us to the list of people that would definitely use this if it were not restricted to the premium tier. We simply cannot justify $2400/month for our volume.
Any update on this ?
At least allow Virtual network on the standard Tier.
Any news ? In reality seems there is no other option than use developer tier in production if soultion is not very critical, because of VNET integration. Such VNET integraion pricing for production tiers may keep away from even starting to think about some service moving into Azure.
Any updates? We use Azure Service Fabric Cluster and need VNET. We also don't need 1 billion requests, but a secure gateway to private clusters....
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 one of those really dumb decisions. We need the VNET integration, but are not going to pay for Premium since we don't need it. We would rather have multiple APIM's at a basic or standard tier. Guess we will stick with the dev tier for now.
We faced BackendCoonectionFailure intermittent issues. Only solution we found from Microsoft support help team is to use VPN. But this requires upscalling each APIM instance to Premium tier which cost £2000 as compare to £100 per month just for one instance. We have three instances.
Please either add VNET option in Basic or Standard tier or make it addon service and bill separately instead of upscaling to premium tier.
At least standard tier should have vNET support if not Basic.
Jarimba, Rui commented
Any updates on this?
Been under review for over a year any updates?
steve l commented
Service Fabric is by far the the best product for our IoT startup to use - however the cost of plugging it into APIM will prevent us from being able to do so.
A small company spending £1000+/month on Azure can't afford to make the leap to £3000+ because of one component.
Come on guys - flick the switch!
Steve Culshaw commented
Echoing everyone's previous comments; only having VNet support in Premium is killing any potential for APIM in our organisation.
The functionality already exists and two of the top ten requests here, arguably three when you include the on-prem version, are for this feature. Why don't you just give people what they want and take their money? You're losing market share here by not giving customers the features they require to keep their back ends private and secure when using this product.
James Maguire commented
Agreed. really wanted to use APIM but the pricing to get vnets is ridiculous.
Raul Gimenez commented
Fully agree with this request. Having VNET support it's also a must for our architecture, but make no sense to pay 2.400€/month for it. The other features of the Standard version are more than enough for us.
Please, include the VNET support in the standard version.
Mikhail Zingman commented
VNET support is an absolute must for our company, but there's no way anyone would agree to pay $2500+/month just for one gateway feature alone. Please support it in at least the standard SKU...