Skip to main content
Azure Logic app - When to choose which plan (Consumption vs Standard)?

#cloud #azure

Hi All!

When we want to perform some workloads without worry about an environment in our hand and need serverless architecture (i.e Microsoft Managed), we can go for either Azure function App or Logic App.

In both of Logic App and Function App, we need not to worry about the infrastructure. Microsoft will take care of it at that time of workload(s) running. i.e. for example, If we choose Azure function app .NET based, MS will take care of OS and its necessary packages installation to run etc..,

One who likes code part can go for Function app and Some who likes visual designer to create flow/connectors can go for Logic App.

In this article we will see which plan type we have to choose for our workloads.

Azure Logic App service provides a way to automate workflow (i.e Workflow is a series of steps that defines a task, business process, or workload).

We need to pay attention carefully while create a Logic app. If not, either we may loss money or halt in the middle due to not able to achieve some feature because of limitation(s).

For example, If I create a Logic app in standard plan where it enough and should have with consumption because it runs occassionally, we need to pay from the beginning (not even for running).

Logic App has 2 set of plans as below.

  1. Consumption
  2. Standard

Go for Consumption when your workload(s) come under the below category

  • Pay per run - i.e. Cost calculated only/whenever workload running.
  • Multi-Tenant/Shared - Logic App can be accessed by other tenants including home tenant.
  • Entry-level, ad-hoc - It will be suited for R&D, small adhoc workflows running with limited use.
  • Only one workflow supported - You can't create multiple workflows in single Logic App.
  • When you don't want Virtual Network Integration, Private Endpoint support, Network Isolation
  • Need not of Hosting plan.

Go for Standard when your workload(s) come under the below category

  • Single-Tenant- Logic can be accessed only by home tenant
  • Cost calculated from the created time wven though workflow not run, need to pay.
  • It suits for Enterprise level
  • Multiple workflow - You can create multiple workflows in single Logic App. (i.e 1-to-Many relationship is possible)
  • When you need Virtual Network Integration, Private Endpoint support, Network Isolation
  • Require Hosting plan - Hosting plan is a storage mechanism which stores state, run history, artifacts of workflow for Logic app ,either azure storage or (SQL(preview) and Azure storage)

Comments

Post a Comment

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
1 comment
Read more
Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Post a Comment
Read more
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...
Post a Comment
Read more