Updated: July 23, 2020 (September 3, 2018)
Analyst ReportFlow Administration and Development Timeline
- Flow is becoming the standard workflow engine for multiple Microsoft services.
- Administrative improvements could help companies better control Flow’s use.
- Additional design features make it a serious developer platform.
- Flow service charges can add to IT budgets, and unauthorized projects could burden administrators.
Microsoft Flow consists of a graphical design environment and an Azure-hosted workflow engine. Flow targets power users of Office 365 applications and services with more experience than information workers, but who are not full-time developers.
Flow Overview
Users use the Flow design environment to create individual workflow routines, known as flows, which are executed after a triggering event or user interaction. Data is moved between services in Flow through connectors: Web service wrappers allow Flow to easily use data from both Microsoft services, such as OneDrive for Business and SQL Server, and third-party services, such as Google Drive and Salesforce.
Atlas Members have full access
Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.
Membership OptionsAlready have an account? Login Now