1

We are currently an AWS customer and have developed a few internal serverless apps that integrate with some of our business applications. Many of the functions we developed need to access private resources in our VPC. The userbase is small hence the frequency of function invocation are small and the cost is single digits generally.

We are evaluating moving to Azure. One aspect that I am stuck, is the cost of running similar apps to Azure. There are a number of the question here addressing the limitation of the Consumption Plan (link and link) and the breaking down of, the confusing, cost structure of Azure Functions Premium needed for VNet (to access private resources).

The difficulty I have is it appears that our cost jumps from a few dollars to $100+ for similar functionality. Are there alternative ways/designs that can be used without having to resort to Azure Function Premium? Have any experienced similar issue and how did you address them?

Nishit Joseph
  • 75
  • 3

1 Answers1

0

From the matrix of networking features, the VNet integration features exists on the Premium plan, App service plan and App service environment.

enter image description here

ASEs are isolated to running only a single customer's applications and are always deployed into a virtual network. It needs high cost. Azure Functions Premium plan is sometimes referred to as Elastic Premium plan. The Azure App Service plan operates at a fixed scale and offers network isolation similar to the Premium plan. Currently, you may consider using app service plan and premium plan on Azure for VNet integration to access private resources in a VNet.

Nancy
  • 26,865
  • 3
  • 18
  • 34