@Aaron Freeman Thanks for reaching out.
I understand your frustration with the pricing structure of Azure Logic Apps. The pricing for Azure Logic Apps can be complex and difficult to understand, especially if you have a simple workflow need.
Azure Logic Apps offers two pricing models: consumption-based and standard. The consumption-based pricing model is designed for workflows with sporadic or unpredictable usage patterns, while standard pricing model is designed for workflows with consistent and predictable usage patterns.
The main difference between the two pricing models is the predictability of the usage patterns. If you have a workflow with sporadic or unpredictable usage patterns, the consumption-based model may be more cost-effective. If you have a workflow with consistent and predictable usage patterns, the standard model may be more cost-effective.
It's important to note that the standard pricing model offers additional features and capabilities that are not available in the consumption-based model. For example, the standard model offers support for VNET integration, custom connectors, and integration service environments.
For more details on the comparison, you can refer to this document.
I understand that the pricing structure may not be suitable for all use cases, especially if you have a simple workflow need. However, Azure Logic Apps offers a wide range of features and integrations that may be beneficial for more complex workflows and if you have more workflow/usage and inbuild connector in your workflow then standard logic app may be cheaper than consumption logic app in some of the scenario based on your usage.
I hope this helps! Let me know if you have any other questions.