This document provides an introduction and overview of Microsoft Flow. It begins with introductions of the presenters and then covers the following topics in Microsoft Flow: 1. How flows can connect to on-premises data using the on-premises data gateway. 2. How environments and data loss prevention settings isolate flows and data. 3. How flows can extend connectivity to systems outside of Microsoft apps through actions, custom connectors, and HTTP requests. 4. A comparison of Logic Apps and how the workflow engines are related. 5. Pricing comparisons between Flow and SharePoint Designer. 6. The roadmap for upcoming Flow features. It concludes with

1. Introduction à Microsoft
Flow
Serge Luca
Isabelle Van Campenhoudt
Sabrine Chouk14 octobre 2017
#SPSParis

2. Merci pour votre soutien

3. Serge Luca
11 x SharePoint MVP, Brussels
SharePoint since 2002
Architect (Admin, Dev, gouvernance)
Managing partner of www.shareql.com
Worked for the MS workflow team
Blog: http://sergeluca.wordpress.com/
sergeluca@shareql.com
@sergeluca

4. SQL Server MVP, Brussels
Consultant, speaker, trainer, GUSS Board Member, PASS V-Chapter Leader
Managing partner de www.ShareQL.com
SQL Server since 1999
Blog: http://thesqlgrrrl.wordpress.com/
ivc@ShareQL.com
@thesqlgrrrl
Isabelle Van Campenhoudt

5. • Consultante Office 365 & SharePoint Chez
Orange Application For Business
• Pseller Office 365 chez Microsoft
• Membre de L'AOS community
• Blog: http://sharepointsabrine.wordpre
ss.com/
• Sabrine.chouk@orange.com
• @ChoukSabrine
Sabrine CHOUK

7. Flows and on premises
Environment + Data Loss prevention
Extensibility : communication with the outside world
Logic Apps
Prices & Roadmap
Creating Flows
Introduction : the context
Conclusions

8. Introduction : the context

9. The context : business Apps
Empower power users
Connect data across apps
More efficient developers
App Services
Service Fabric
Azure Functions
…
Logic Apps
API Management
BizTalk
…
SQL Server BI
Data analytics
Internet of Things (IoT)
…
Build modern business app fast

10. Creating Flows
Introduction : the context

11. Creating and managing Flows
Microsoft Account (free) or Office 365 or Dynamics 365 or Flow (paid)
or PowerApps ( or free new PowerApps Community Plan)
Flow.microsoft.com
Powerapps.microsoft.com
A modern SharePoint Online list
Mobile app (iOS and Android, Windows Mobile is coming)

12. Flow templates

13. demoEXPENSE REPORT

14. Flows and on premises
Creating Flows
Introduction : the context

15. Flow and data on Premises
• Install the « on Premises data gateway »
(shared between PowerBI, PowerApps and Azure Logic
Apps)

16. demoFLOW AND DATA ON PREMISES

17. Flows and on premises
Environment + Data Loss prevention
Creating Flows
Introduction : the context

18. Why« environments » ?
• Isolated spaces where Flows/Data are
running/stored
– Ex HR, Marketing, Production, Legal, DEV,
TEST, UAT, PROD…
• Different rules (DLP)
– Ex marketing can use twitter, Legal and
Production cannot
• Different regions if needed

19. Flow Administration Center

21. demoENVIRONMENTS & DLP

22. Limitations
• Gateways are created in the default
environnement
• Resources like Custom API must be in
the same flow environment
• The Microsoft Common Data Service is
linked to only 1 environnement

23. Flows and on premises
Environment + Data Loss prevention
Extensibility : communication with the outside world
Creating Flows
Introduction : the context

24. Extensibility : communication with the
outside world
 Action Request
 Custom Connector (REST API described in a Swagger )
 Action Http
PowerApps calls Flow
A custom app calls Flow
PowerBI calls Flow (Data Alerts)
Flow calls the outside world

25. demoPOWERAPPS CALLS FLOW

26. demoA CUSTOM APPLICATION CALLS
FLOW

27. demoFLOW CALLS THE OUTSIDE WORLD

28. FLOW & POWER BI
FLOW
DATA ALERTS
DATA SOURCES
POWER BI
SCHEDULED REFRESH
STREAMING DATA
LIVE

29. demoFLOW & POWERBI

30. demoPOWERBI CALLS FLOW (data alerts)
)

31. Flows and on premises
Environment + Data Loss prevention
Extensibility : communication with the outside world
Logic Apps
Creating Flows
Introduction : the context

32. Logic Apps
More dev oriented(Json, Rest api, Visual Studio …)
Logic Apps connectors can be used in Flow
Exceptions : B2B connectors B2B (Very good integration with Biztalk
Server)
The workflow engine behind Flow is Logic Apps

33. demoLogic Apps
)

34. Flows and on premises
Environment + Data Loss prevention
Extensibility : communication with the outside world
Logic Apps
Prices & Roadmap
Creating Flows
Introduction : the context

35. Tarifs: Comparison

36. Tarifs: Comparaison

37. Today : SharePoint Designer versus Flow
SharePoint Designer Flow
Multiple connections to >150 data sources SQL, SP, ODBC & WSDL only ALWAYS
Out of box templates <5 100s
Workflow & approval history <365 days Perpetual
Approvals over mobile + mobile notifications NEVER iOS, Android, Windows Phone + in Outlook.
History coming imminently.
Loops, Do Until, Switch-case, parallels, variables Yes Yes
On-premises support Native Gateway support
Extended field types (people, choice, MMS, lookup) Yes People, choice, lookup – Yes new, MMS –
coming soon
Send email as user or system System only Yes
Attachments Yes Yes new

38. Gaps -> roadmap SharePoint Designer versus Flow
SharePoint Designer Flow
Out-of-box send for review Limited Q4CY2017
Reassignment of approvals Yes Q4CY2017
Approval reminders Yes Q4CY2017
Custom input forms for approvers Yes Q4CY2017
Document library CI-CO, approve Yes Future
Approver impersonation Via permission elevation Future
Site level actions Yes Future
Set permissions on an item Yes Future
Submit/upvote ideas : https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

39. Microsoft Flow roadmap - highlights
H2 Calendar 2017 Calendar 2018
oExport/import app packages across envs
oSPO – “In-the-box” review flows
oSPO – use flow for Content Publishing approvals
oSPO – people, choice, attachment and multi-values
oIn-context in Dynamics 365
oEmbedded Power BI analytics
oOffice 365 audit logs
oSupport for GDPR compliance
oUK deployment
oHTML rich text editor
oGuides for debugging actions and conditions
oGovernment and sovereign clouds deployment
oALM – Sandbox environments
oALM – Move or copy across environments
oLeverage device signals (e.g. Location)
oAppSource integration
oAzure functions integration

40. Flows and on premises
Environment + Data Loss prevention
Extensibility : communication with the outside world
Logic Apps
Prices & Roadmap
Creating Flows
Introduction : the context
Conclusions

41. Positive
• Simple
• Not just SharePoint
• Connection to hundreds of services
• Including on prem!
• SharePoint Integration
• PowerApps, PowerBI integration
• Team Flow is very proactive & delivers

42. Negative
• Young, unknown reliability
• Cannot copy flow across environments
• No state machines (but we have loops and tests)
• Collect feedback weak
• SharePoint integration weak (no lookup,…)

43. Advices
• Keep your forms as simple as possible
• Manage the business logic in the workflow
• Learn the Logic Apps Workflow Definition
Language (WDL)
– Read my blog post
https://sergeluca.wordpress.com/2017/04/26/u
sing-the-azure-logic-apps-workflow-
definition-language-in-microsoft-flow-part-1/

44. Thank you, for your for #SPSParis