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 Devops Bypass policy when code push - Glimpse Devops is a culture most of the organizations embrace it. In this article let's see what is branch policy in Azure Devops (ADO). Before that, we need to know what is policy (aka) Branch policy in ADO Branch policy has set of policies to be applied on the branch typically main. By that we avoid accidental activity. Few are as Reviewers required to view the code change before move to main/master branch work item - ADO's user story / task / bug etc., any of the item number should be linked Consider a scenario that your organization's existing project has some policies like most recent code pusher can not push code again. Very rare case may happen or not, a senior developer needs a exclusion to fix an urgent pre-prod/production incident. So He/She does not want to be in that case. They want to push their code often when discussing with client manager or customer So, how can we override the bran
Post a Comment
Read more
Find your azure service/resource tab easily in chrome using an extension Irrespective of role like Azure devops, developer, network engineer, architect etc., we typically use azure portal primarily While working on issues and/or in presentation, we may require to have multiple azure tabs with different services Here consider a scenario that I am analysing an issue from logic app which uses azure function. So I need to visit logic app, function app and application insights if enabled. If we use single tab, it will take more time. So, we can have multiple tabs. Here logic app, azure function and application insights in each tab I would have. yes. It will save our time but consider that sometimes we would have more than 10 tabs at that time we may not know which tab has which resource because all browsers have A icon. So, while navigating, we may get annoyed. So, What's the solution when we use more tabs? Here we've a nice feature in chrome browser which provid
Post a Comment
Read more
Azure storage account new access tier - Glimpse Azure has introduced a new access tier for storage account called 𝐂𝐨𝐥𝐝. What is the use of it where we already have 3 access tiers as 𝐇𝐨𝐭, 𝐂𝐨𝐨𝐥 𝐚𝐧𝐝 𝐀𝐫𝐜𝐡𝐢𝐯𝐞? Let us take scenarios as below. When our document will get frequently accessed - 𝐇𝐨𝐭 When my document will be infrequently accessed (i.e Within 30 days, it can be accessed. - 𝐂𝐨𝐨𝐥 If my document will be accessed after 30 days, 𝐞𝐚𝐫𝐥𝐢𝐞𝐫 𝐰𝐞 𝐠𝐨 𝐟𝐨𝐫 𝐀𝐫𝐜𝐡𝐢𝐯𝐞 access tier but now When my document needs to be accessed within 90 days at any time - 𝐂𝐨𝐥𝐝 Data retrieval from Archive needs some process like rehydrating (i.e converting from Archive tier to (Hot or Cool) aka offline tier to online tier). To save some cost, we can go for cold tier which allows us to keep our data for 90 days instead of archive tier. Limitations and known issues. The change feed is not yet compatible with the cold tier. Object rep
Post a Comment
Read more