Skip to main content

Workflow Automation with Microsoft Flow and Azure Logic Apps

Source: Microsoft


In June 2016, Microsoft released the preview of its Flow workflow productivity app.  This app allows you to create transactions that span multiple software products in a similar way to competitors IFTTT and zapier.  For instance, I might want an incoming email to save attachments to SharePoint or Dropbox, or generate a notification by text for an email sent from a key contact.

You can start with a Flow template and customize it to your business needs. Flow doesn't require programming and is simple to configure.

Today Microsoft offers connections to 45 services including Office 365, Twitter, Dropbox, Salesforce, MailChimp, and Slack.  Microsoft is adding more services and improving the performance and reliability of Flow.

What is even more exciting to me is that Microsoft offers an industrial strength workflow app for business customers.  Flow templates can be migrated to Azure Logic Apps  which allow developers to build complex and scalable workflows, and to create new connectors to systems that are not covered out of the box.  Logic Apps was released into production in late July 2016.



There is even a BizTalk Server connector in preview now.  Often workflow conditions and parameters are more complex than can easily be captured in a configuration, so having support for code will make many more scenarios viable for Logic Apps.

The following video offers an introductory tutorial on Azure Logic Apps:


Although workflow software has been around for many years, no vendor has really claimed a leadership position or set a standard for the entire industry. Microsoft has the opportunity to do so with these products and related cloud offerings (Azure and Office 365).

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo