HowTo — Three LogicApp Deployment Models/Options
LogicApp is a PaaS model but still they provide three different deployment modes. We will try to understand those options and when to use them.
Option1: PayAsYouGo Model (pay for each and every action)
Option2: Integration Service Environment ( pay monthly/hourly and all LogicApp deployed in ISE will be accounted for)
There are many more reasons than just running cost to use ISE ( Ref )
[ An integration service environment is a fully isolated and dedicated environment for all enterprise-scale integration needs. When you create a new integration service environment, it’s injected into your Azure Virtual Network, allowing you to deploy Logic Apps as a service in your VNET.]
Option3: LogicApp part of FunctionApp ( preview)
Both Option1 and Option 2 are extreme ends and most of the organization has requirements somewhere in the middle of Option1 and Option2, I think that's what the Azure-LogicApp product team recognized and provided the third option of hosting LogicApp as part of the Azure Function App.
- We can enable all network security on App Service Plan and bundle LogicApp And Supporting Function App as one interface
- No need for an integration account to store schema and maps ( thus additional cost saving)
It is still in preview mode
We have to wait for General Availability to understand the final list of features and cost model.
But based on the available details I will be using this deployment model for most of my projects and going for Integration Service Environment only when there are specific needs like due to secure transaction and system needs to be PCI-DSS compliant, or monthly running cost is more than ISE
Steps to create a logic app as par of App Service Plan