You’re offline. This is a read only version of the page.
I'm going to be working on a contact tracing solution using a Power App as the front end. Clinical faculty (students in one of our graduate nursing programs) will be using it to record interactions with patients when doing their daily rounds. Each interaction will be stored in a SharePoint list and we need to adjust the permissions such that only the person creating it and their supervising instructor (another SP list will define that relationship) can view it. There are about 100 clinical faculty who will be recording up to 10 interactions per day 5 days a week. So, if we use a flow to set those permissions, that flow will run (approximately) 1,000 times a day, 5,000 times a week, 20,000 times a month.
We have the "Power Automate for Office 365" license (included in our E3 license) which - I believe - allows 2,000 flow runs per user per month. I know that's cumulative/aggregated, so having 20,000 flows run under my account would just absorb 10 other users' allowances.
Conversely, based on the Logic apps pricing page (https://azure.microsoft.com/en-us/pricing/details/logic-apps/), it looks like it would cost under $5 a month for 20,000 runs (based on use of one connector - SharePoint - and 4 actions). So, cost-wise, it seems like it may be better to go that route rather than risk going over quota on the flow runs.
Are there any other advantages to logic apps over flows in this scenario? I've read that logic apps is more efficient (less overhead) and better suited to frequently-running processes.
Share
Report
1,393
All responses (
Answers (