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

Popular posts from this blog

View powershell history and invoke Hi All! When you do administration activities, you may need to work around with multiple commands in powershell. It is bit difficul to remember all the commands we tried because some of them may be fetched from internet. Consider you tried more than 100 commands in current powershell session and may require to try the same large command. One of the way is you can press up arrow many times to see the previously tried command. we have another easy way is to see the history and invoke it by using its order number instead of whole command typing. Please look into the below example
Wow! Monitor web apps running in azure VM and VMSS via app insights Hi All! Application insights monitors the telemetry of web applications, function app, APIM and etc., Consider a scenario that your organization has some web applications hosted in IIS of an azure VM and they want to monitor performance of those applications. Azure VM was not the eligible candidate to map with Application insights then how can we monitor app(s) running inside azure VM? Now azure offers the feature of monitoring azure vm's web applications through application insights generally available. Please follow the below steps and have a look into the picture You need to have a connection string of an existing application insights. If have, copy it. Go to the VM which has web apps running in IIS Click "Extension+applications" and then click Add Find Application insights agent for .NET and click next Paste the copied connection string of app insights and click Review+Cre...
While loop with head and tail in linux Hi All! In today's post we're going to see/refresh about while loop with head and tail in bash. head - Read the first top 'n' lines. Example: head -n 5 reads first 5 lines from a file or input. tail - Read the last 'n' lines. Example: tail -n 5 reads last 5 lines from a file or input. Please look into the below image we have a txt file called file1.txt which has 3 lines of text and we read using head and tail as above.