Azure Spring Cloud Basic tier does not support Vnet integration

Question

I was ready to start using Azure Spring Cloud and create an INT environment (I already went through the whole analysis and experimentation except for on-prem connectivity). My services require communication with on-prem services therefore I need VNET integration.
It seems that in order to have VNET I have go with the Standard Tier which is 3 times as expensive as the basic tier. https://azure.microsoft.com/en-us/pricing/details/spring-cloud/
The idea was to create 3 Spring Cloud instances. The first two for non-production (integration and staging) under the basic tier and then the last one, the production service under the standard tier. But I need for all those service instances to be able able to communicate with with existing on-prem services.
To move the 3 instances to the standard tier, cost wise is just prohibitive and it is not going to happen. And obviously to run basic tier for the non-production without VNET integration (and custom domains for that matter) defeats the purpose of their existance since they will not be able to do anything for us.

I am quite surprise about all of this. Am I missing something or totally misunderstanding the pricing tiers ?
Thanks

Answer 1

Hi @Fiallega, Jorge (ITD) , thanks for reaching out to us! Happy to help you. I understand your scenario and regret to inform you that if VNET Integration is required, then using Standard Tier for Azure Spring Cloud is the only option we have at this time.

I can suggest you just one thing - To reduce costs, I have seen some customers reduce higher tiers to the minimal. For instance, in your case, you can make 1 non-production app in Basic Tier, 1 non-production and 1 production apps in Standard Tier.

---------------

Please do not forget to "Accept the answer" if the information provided helps you. This will help others in the community as well.