Introduction Azure Logic Apps provide a powerful alternative to Power Automate for building workflows and integrations in the cloud. While both tools share similarities, Logic Apps offer unique advantages, especially for enterprise-scale solutions. However, managing Logic Apps in source control and deploying them via Azure DevOps pipelines comes with its own set of challenges. This blog post explores the differences between Logic Apps and Power Automate, highlights the limitations of Logic Apps in source control, and provides insights into handling system-assigned identities and API versions during deployment.

Introduction In SharePoint, you can enhance user interactions by conditionally triggering different Power Automate flows based on specific conditions in a list or library. This is achieved using JSON column formatting and the executeFlow action. By dynamically linking flows to specific conditions, you can streamline processes and improve automation. List formatting provides a powerful feature to control the flow of a process from filling mandatory fields, create approval tasks. Depending on the status of the list item, different power automate flows can be called.

Power Automate: Save Run Flow URL to SharePoint List Item When running a Power Automate flow, capturing and saving the flow’s run URL to a SharePoint list item can simplify troubleshooting and auditing. This allows you to easily revisit the flow run details in case of failures or for review purposes. However, note that flow run URLs are only available for 30 days, so older links may no longer work.