Clarification on Azure Logic App Pricing

Question

I intend to run an Azure Logic app on a consumption plan. I have the following logic app below and intend to do polling every 1 minute.

Please see sample logic app below:

I have the following questions based on above scenario with polling at 1minute.

1. Am I correct to assume that this logic app runs 6 standard connectors? Assuming that it will be executed 3,000 times (my business case is 3,000 files to be processed per month) then the total Standard Connector executions per month is 3,000 x 6 = 18,000?
2. If polling is 1 minute, and that there are 1440 minutes per day am I correct to compute that there are 1440 action executions per day?
3. Is the pricing calculator I did below correct?
4. What is the data retention for?

Answer 1

@Ziggy Zulueta Thanks for reaching out.

As you are using the Consumption tier so both builtin and Azure action/trigger will be charged per call.

Am I correct to assume that this logic app runs 6 standard connectors? Assuming that it will be executed 3,000 times (my business case is 3,000 files to be processed per month) then the total Standard Connector executions per month is 3,000 x 6 = 18,000?

A total of 6 actions (both Azure and built in action) are there in your workflow so your above assumption is correct for the action cost in the ideal scenario where there are no failures, issue exception.

If polling is 1 minute, and that there are 1440 minutes per day am I correct to compute that there are 1440 action executions per day?

Yes, it is correct for trigger. Per days (60 min * 24 hr ) --> or 1440 API calls

Is the pricing calculator I did below correct?

Yes, it is correct as per your assumption and data retention.

What is the data retention for?

Azure Logic Apps uses a fixed pricing model for data retention and storage consumption. The data retention and storage consumption costs accrue using a fixed pricing model. Inputs and outputs from run history are kept in behind-the-scenes storage, which differs from storage resources that you independently create, manage, and access from your logic app. For more details you can refer to this section here.

In nutshell Azure Logic Apps meters all successful and unsuccessful actions as executions. However, Logic Apps don't meter these actions:

1. Actions that get skipped due to unmet conditions
2. Actions that don't run because the logic app stopped before finishing

Please note that skipped triggers are billable. For more details, follow the doc.

Let me know if you have any queries or concerns.

Please "Accept Answer" if the answer is helpful so that it can help others in the community.