VPN/ExpressRoute support in Standard Tier
If you must charge more for VPN make it a paid for add-on for Standard tier.
Using the standard tier is already tough to justify for our low volume business case. Unfortunately the backend servers are in a private network so we need the ExpressRoute functionality.
API Management was justified based on it also being the authentication gateway and firewall between the Internet and our internal APIs. The business case doesn't work if we still need to manage Internet facing reverse proxy servers or pay for Premium.
Kristi Ryder (Tek Experts) commented
I agree that the Virtual Network should be available on tiers other than just developer and premium
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 tier.
EL Mostafa Lourhmati commented
The VNET is very inportant feature for this service so it should be in the Basic and Standard pricing option. All of our Microservices are hosted on-premises.
a real show stopper for us. Too expensive to secure small set of apis
Saurabh Rajguru commented
This is must have feature.
We are integrating it with service fabric and it is not practical to do it without VNET.
Since VNET is only available in premium which does not fit into our production scenario.
Please provide that otherwise we have to drop our whole infrastructure from azure and move elsewhere.
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.
Darren Kay commented
As an enterprise, we have asked for this for nearly 3 years and still no feedback. If you're urgently waiting on this idea I suggest looking at alternative solutions.
Christian Weiss commented
VNET integration should really be included in ALL plans - even Basic. We will not use API management until that's changed.
Rune Synnevåg commented
Any updates ?
We only have a small number of APIs and calls to manage but require ExpressRoute support so using Azure API Management isn't feasible given the cost of the Premium tier. This would be our preferred option if it was supported in the Standard tier.
Rune Synnevåg commented
Anything new in this case? This is important to in order to justify the use of API managment, You want to be able to put a WAF in front of a gateway like this. And properly secure it.
[Deleted User] commented
This is a very important feature for us in the Standard Tier. We must have this or we are going with Mulesoft!
Venkat Krishnamoorthy commented
Hello what is the status on this?..
VNet support in standard is key for us
There should be an option to expose an Azure VM deployed backend through API Management in Standard tier without having to expose the backend to Internet.
The VNET is very inportant feature for this service so it should be in the Standard pricing option