154 - Azure Logic Apps and Power Automate Differences - Part 1

In this video, we are going to discuss the similarities and differences between Azure Logic Apps and Power Automate. Topics include:
- Subscriptions, Security Boundaries, Additional Security Features, Governance.
Please see this short follow-up video regarding governance and a couple DLP features which were not mentioned in original video: • 155 - Power Automate a...
Part 2- Connectors: • 156 - Azure Logic Apps...
References from video:
Blog Post: www.serverless360.com/blog/az...
Power Platform Governance: • 007 Power Platform S...
Azure Logic Apps Playlist: • Azure Logic Apps
Power Automate Playlist: • Power Automate

[@dougydoe]

Well presented Kent. I look forward to the subsequent ones.

[@KentWeare]

Thanks Douglas!

[@rezcan]

Love the content Kent. You rightly pointed out Easy Auth & Conditional Access separately, but another thing that I think needs to be highlighted here is the powerful use cases that the combination of these two can unblock for http based triggered Workflows in Logic Apps. It's a big plus for Logic Apps an for those customers that security is important to them, but they want to keep their API exposure to public internet simple (and not use APIM or reverse proxy based solutions). Easy Auth + AAD Conditional Access = Another layer of security! Also it's worth noting that Power platform tenant isolation is only for AAD based connectors :)

[@KentWeare]

Thanks Reza...all valid points

[@tylerkolota]

Topic Suggestion: Pay as you go PA vs. Consumption LA
Seems like consumption based Logic Apps is always better. I’d like to know if you or anyone know something I’m not seeing.

[@KentWeare]

A good suggestion...I will keep it in mind when I talk about licensing.

[@rezcan]

If you are modeling a business process in a D365 app, why would you want to prefer consumption LA to PAYG Power Automate and lose all native capabilities (e.g. current environment connector) and ease of deployment within your solution packaging ecosystem? As Kent said, this is really not a vs. conversation and more organizations end up choosing the best solution for the use case. Personally I've seen more customers choosing to use both technologies than those who prefer one over another.

[@Xprtentertainment]

Curious how you think of lifecycle and deployment of logic app standard, whats the way here? Is it local development (which sucks) and deploy? Or Is it from portal? How can u test vnet stuff from local? We skipped all recommended ways and just develop in portal and manual extrakt workflows becuase local dev and deployment (built in vs managed connector sucks) when Will this be eneterprise ready? (Dev,qa,prod) Also: why isnt file system connector (built in) supported ourside asev3! It was supposed to be

[@rezcan]

Overall local dev experience and automated deployment of Logic Apps Standard (like many other Azure services) in a true enterprise world using CI/CD is still not there in my opinion. In demos and conferences everything works (single service deployment or really simplified scenarios), but when you start putting a number of these Azure services together in pipelines, create this dependency chain between them and apply private networking & security on the top, then there are serious challenges reaching that level of repeatability, predictability and reliability that's the basic premise behind DevOps. That's my' experience with every single customer I've worked with in the past 4-5 years in the Azure space.

[@KentWeare]

There is definitely room for improvement on the dev experience and CI/CD. We do have some investments being made in next 6 months that should help.

[@Xprtentertainment]

@@KentWeare its only supported in ASEv3? Or what do u mean? I have been told its exclusive asev3

[@KentWeare]

@@Xprtentertainment When it is rolled out shortly it will be available to Logic Apps Standard instances, including those using App Service Plans