Logic Apps - Cost management

Vivek Komarla Bhaskar 956 Reputation points
2023-10-11T12:32:22.27+00:00

Currently, I am under a consumption model for my logic apps, and I have accrued around 425£ between 01st Oct and 10th Oct. Is it beneficial for me to move these logic apps from the consumption model to the standard plan?

  • Below are my incurred costs -Screenshot 2023-10-11 at 1.13.32 pm

If the Consumption Data Retention cost is due to the default setting on Workflow settings -> Run history retention in days. I assume changing this to custom 7 day retention would lower the costs. Is it possible to reduce this further?

  • Standard plan costs -

Screenshot 2023-10-11 at 1.30.48 pm

Azure Cost Management
Azure Cost Management
A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.
3,615 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,555 questions
{count} votes

Accepted answer
  1. Sonny Gillissen 3,751 Reputation points Volunteer Moderator
    2023-10-12T09:08:33.6433333+00:00

    Hi Vivek Komarla Bhaskar,

    Thank you for reaching out on Microsoft Q&A!

    Unfortunately there's not a one-off answer to your question. It depends.

    In general it is indeed possible to switch to a Logic App Standard in terms of cost, because it's a fixed price instead of consumption thus you know what you're going to pay and also know it will be less.

    However, a fixed price also means reserved resources, so a Logic App Standard does not automatically scale out when you need more resources on peak moments (thus it "hangs" at that point). You can, off course, create your own scaling options in the Logic App Standard, but keep in mind that this scaling will also cost you money. On heavy workloads you may not end up cheaper then with a Consumption plan.

    My advise to you would be to test your workloads based on a single Logic App Standard, and see if it holds the load. If so, you're perfectly fine with using it. When you need scaling it may be as expensive as Consumption. But this needs to be thoroughly tested, based on your workloads.

    So, long story short: yes it could potentially be an outcome for saving cost, but always keep performance and scaling in mind to fit your needs. This determines whether or not it's actually cheaper.

    Please click “Accept answer” if you find this helpful. Feel free to drop additional queries in the comments below!

    Kind regards,

    Sonny


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.