Doctor Flow- Best practices Microsoft flow - Techorama 2019

May 23, 2019Download as PPTX, PDF1 like895 views

This document summarizes a presentation about advanced tips, patterns, and best practices for using Microsoft Flow. It includes demos of creating automated timesheets, calling the Graph API, using custom connectors, implementing approval escalation workflows using the state machine pattern, managing errors and parallelism in flows, and integrating Flow with Power BI. It also covers topics like licensing requirements, throttling limits, and strategies for handling long-running processes and service accounts.

Doctor Flow- Best practices Microsoft flow - Techorama 2019

Microsoft Flow Advanced: tips,
pitfalls, patterns with Doctor
Flow
Doctor Flow

Office Apps & services MVP
Business Applications MVP
O365 Architect
@sergeluca
ShareQL Brussels
Office365
Flow
Dev
Architecture
Bullshit
Doctor Flow aka “Serge Luca”

https://myignite.techcommunity.microsoft.com/sessions/66476

What can block me ?
Do I need to use a third party tool ?
Is it robust enough for enterprise business processes ?
Flow is very easy to use and not expensive (Office 365 license)
Here is our experience after 3 years and 8 enterprise flow projects

Create REST
Services
(like Azure
functions)
Create
Custom
Connectors
Call REST
APIs from
Flow
Integrate
Flow in their
Applications
Developers
Activities
Requires P1Requires P1

State machine pattern or Controller patternNo State Machine
No custom task
forms
Max 5,000 iterations in Do until –> Create
embedded loops
Max 5,000 iterations in For each (100,000 in
Plan 1)
Loops
Create nested flows or raise a ticket250 actions/flow
Flow Approval
duration : 30 days
Flow duration :
30 days
No guest access
Controller pattern
In the roadmap for Flow & PowerApps
ALM/devops
weak
I could tell you, but then I would have to kill
you…
Custom approval actions

State Machine and
> 30 days
« Flow Controller
Pattern »
Controller
Launcher flow
SecretaryAdvisor Boss
escalate
timeout
approved
rejected
in vacation
timeout
approved
rejected
redirect
in vacation
timeout
approved
rejected
escalate
Normal flow
Service flow

3 Implementations Messages
(Service
Bus)
Database
(SQL Azure)
Http &
Request
(Requires
P1 license !)
Requires P1

Demo:
Approval escalation
Approval analytics
Controller pattern
Machine Learning

Started from
Excel
Started from SP
New Expense
from App
Trigger : Excel for a
selected row
Trigger :
SharePoint for a
selected row
Existing Expense
from App
Trigger :
SharePoint : when an item is
created
Proxy Flows
Service Flow

• the url might change, we want to use a stable vanity url like
https://flowdemo.azure-api.net
• you might need to protect it : authentication
• throttling
• restricting the callers to some specific network locations
• ….

Returns max
5000 records
or 100.000 if
P1 licence
$skiptoken=Page=TRUE%26p_ID=3000&top=5000

Adapt retry policy
Reduce flow concurrency
Use several connectors
Error HTTP 429 : « I’m too busy » come later (in 10 sec)
Flow throttled by the Service (like SharePoint) and by
the Connector (600 calls/min)

202 ACCEPTED
The request has been accepted for
processing, but the processing has not been
completed.
Long Call Duration
Pattern
Requires P1

FLOW
DATA ALERTS
DATA SOURCES
POWER B
I
SCHEDULED REFRESH
STREAMING DATA
LIVE
POWERQUERY
Requires P1
Data On premises
REFRESH DATASET (april 2019)

Keep your
forms Simple
Trigger
properties
Accounts Management Environments
Business
logic in Flow
In variables Owners :
ADD Groups
Connectors :
Services
Accounts
(except
personal
flows)
PowerShell
Flow
Management
connector
Use several
DLP

Flow can
complement
PowerShell
Be carefull with
P1
…Or run
Powershell via
Azure
Automation
runbooks/hybrid
You can avoid
it (split flows
and use service
accounts)
Integrate with
Azure DevOps
…I don’t want
to kill you
https://docs.microsoft.com/en-us/business-applications-release-
notes/April19/microsoft-flow/
And much
much more…
This is just the
beginning !

This document summarizes a presentation on advanced tips, patterns and demos for Microsoft Flow. The presentation covers state machine patterns, controller patterns, calling APIs, managing errors, parallelism and long calls. It also demonstrates approval flows, custom connectors, and integrating Flow with PowerBI. The presenter emphasizes keeping forms simple, using service accounts, and splitting flows to avoid PowerShell dependency for automation.

Microsoft flow best practices SharePoint Saturday Bremen 2019 (Germany)serge luca

This document provides an overview of Microsoft Flow best practices. It discusses using logical workflow IDs and approval IDs, bulletproofing code with Coalesce(), state machine patterns for workflows over 30 days, error handling techniques like retry policies and reducing concurrency, asynchronous long calls, proxy and service flows, Flow extensibility through HTTP triggers and responses, integrating Flow with Power BI, and conclusions about keeping forms simple and using Flow to complement other tools like PowerShell. Demo flows are provided for expense reports, calling APIs, custom connectors, managing errors, parallelism, and connecting Flow to Power BI.

Microsoft flow best practices with Doctor Flow. PowerSaturday 2019, Parisserge luca

Using microsoft flow in real world projects 2 years later and what's nextserge luca

This document summarizes Serge Luca's presentation on using Microsoft Flow for real world projects and citizen developers. It discusses how Flow can be used to solve problems closer to where users work, provides examples of apps built by TransAlta using Flow and PowerApps, and highlights how 60 ideas for improvements were generated from a Flow workshop. It also provides an overview of new Flow features, patterns for complex workflows, and concludes that Flow is still in its early stages with great potential when used to complement other tools like PowerShell.

How to become a Power Automate/Flow hero with Doctor Flow (Session online SPS...serge luca

Power Automate/ Flow patterns tips and tricks after 3 years with Doctor Flowserge luca

2019-05-16 aOS Luxembourg - 6 - Flow avancé - Serge LucaaOS Community

AOS Germany- 2020-Advanced Business Process Management with Power Automate an...serge luca

Microsoft Flow best practices European Collaboration Summit 2018serge luca

F1_Design Mission Critical Enterprise Applications with Power Automate and Do...serge luca

Microsoft Flow in Real World Projects: 2 Years later & What's nextBIWUG

This document summarizes a presentation about Microsoft Flow given at the SharePoint Saturday Belgium 2018 conference. The presentation discussed how Flow has evolved over the past 2 years and what new capabilities are coming. It provided demos of common real-world Flow patterns for automating tasks like timesheets, expense reports, and calling APIs. It also covered Flow integration with other services like Power BI and limitations around loops, actions per flow, and error handling. The presentation concluded by discussing best practices for Flow development and extensibility options for communication with external systems.

Moving full trust code to the cloud using repeatable patterns and best practicesLuis Valencia

This document discusses SharePoint apps and provides an overview of app types and development patterns. It describes how apps can be used to customize SharePoint by adding new features like app parts, actions, and dialogs. Apps can be hosted within a SharePoint farm or externally and connect via OAuth, REST, or client-side APIs. The document recommends resources for exploring, signing up, training, and getting support for SharePoint app development.

4 Integrating azure monitor with power bi and power automateKumton Suttiraksiri

พบกับเซสชั่น "Integrating Azure Monitor With Power BI and Power Automate" ในงาน Microsoft 365 Developer Bootcamp - วิเคราะห์ข้อมูลการใช้งาน Resources บน Azure ด้วย Azure Monitor ร่วมกับ Power BI - ปรับลดการใช้งาน Resources แบบอัตโนมัติด้วย Power Automate เมื่อถึงขีดจำกัดด้วย Power Automate โดยคุณ Thanyapon Sananakin (Microsoft MVP)

Intelligent automation with Microsoft Power AutomateDaniel Laskewitz

The document discusses Microsoft Power Automate, a workflow automation tool. It highlights how Power Automate provides automation capabilities at scale across organizations, with secure integration of both cloud and on-premises applications. A demo is presented showing how Power Automate can automate approval workflows. Advanced capabilities are also discussed, such as combining Power Automate with other Azure services like Logic Apps and Functions.

Public v1 real world example of azure functions serverless conf london 2016 Yochay Kiriaty

Yochay Kiriaty gave a presentation on serverless computing using Microsoft Azure services. He began by defining serverless and its benefits like event-driven scaling, sub-second billing, and abstraction of servers. He then demonstrated several serverless patterns using Azure Functions for tasks like processing data from Blob storage, responding to API requests, and replicating logs between data centers. Throughout the presentation, he emphasized best practices for building serverless applications including designing functions to do single tasks, finish quickly, be stateless and idempotent.

Connect SharePoint Framework solutions to APIs secured with Azure ADBIWUG

This document discusses using the AadHttpClient to connect SharePoint Framework (SPFx) solutions to APIs secured with Azure Active Directory (Azure AD) without needing to handle authentication headaches. The AadHttpClient handles requesting and including access tokens in API calls automatically. Administrators configure which API permissions are available by setting permissions for a pre-provisioned Azure AD application. This allows SPFx solutions to connect to secured APIs seamlessly without having to specify reply URLs or handle multiple requests for tokens.

#SPFestSEA Automate digital workplace provisioning with #MicrosoftGraph and #...Vincent Biret

Building high scale, highly available websites in SharePoint 2010Ben Robb

This document discusses strategies for building high scale, high availability websites in SharePoint 2010. It covers reducing server workload through server topology optimization, managed code best practices, and deployment techniques. It also discusses reducing page payload size through viewstate, XHTML validation, lazy loading JavaScript, and compression. Finally, it discusses reducing the number of page requests through file consolidation, AJAX, removing unnecessary scripts/CSS, using CSS sprites, and content delivery networks. Testing approaches like load, spike, and endurance testing are also covered. The overall goal is to measure and optimize performance through techniques that reduce server load, page size, and page requests.

Build a SharePoint website in 60 minutesBen Robb

This document discusses how to build a SharePoint website in 60 minutes by setting up a development environment, using SharePoint Designer for rapid application development to quickly build out branding and site structure, and packaging the site into a Visual Studio project for professional development and deployment. The key takeaways are to script as much of the process as possible for things like environment setup, content import, and deployment, and to leverage tools like SharePoint Designer and Visual Studio to streamline development.

Introduction to Azure FunctionsMarco Parenzan

Logic Apps – DeploymentsBizTalk360

This document discusses deploying Logic Apps using version control and continuous integration/deployment. It demonstrates setting up a Logic App template in Visual Studio Team Services source control, building the template using a build definition, and deploying it to environments through release management. The deployment is fully automated using Azure Resource Manager templates, PowerShell scripts, and either Visual Studio Team Services or GitHub for deployment. This provides a unified process to deploy Logic Apps and related Azure resources across environments from source control in a reusable, parameterized manner.

[Roine] Serverless: Don't Take It LiterallyEuropean Collaboration Summit

SCU Asia System Center: Beyond orchestratorAlexandre Verkinderen

To evolve beyond a dependency on integration packs as the definition vehicle for workflow tasks, to overcome scaling and multi-tenant limitations, and to provide for effective web-based remote Runbook administration, a new paradigm for achieving automation in a Microsoft network is emerging. The name of this new technology is Service Management Automation. Let’s have a look during this session at the differences and when to use SMA or Orchestrator.

Custom dev o365Ashish Trivedi

Techorama: Power BI Automation with MS FlowIda Bergum

This document discusses automating Power BI using Microsoft Flow. It includes examples of automation scenarios for refreshing Power BI datasets and managing Power BI Premium capacities. The presentation covers creating a custom connector to the Power BI REST API, building flows to trigger dataset refreshes and assign workspaces to capacities, and testing the flows. The goal is to demonstrate how flows can be used to automate administrative tasks in Power BI.

Introduction to the Microsoft identity platform for developersChristos Matskas

Building workflow solution with Microsoft Azure and Cloud | Integration MondayBizTalk360

This document provides an overview of workflow solutions using Microsoft Azure and cloud technologies. It discusses Power Automate, Logic Apps, and Durable Functions for automating business processes and workflows. It covers what each technology can do, pricing models, use cases, and monitoring/governance options. Key takeaways are that the technologies are not competing and to choose based on use case, and that they are mature leading options with moderate learning curves.

PnP in building office add ins - publicMostafa

This document discusses Office Add-ins and how they integrate with Microsoft Office and Azure Active Directory (Azure AD). It explains that Office Add-ins can be built to be fully flexible and work across private, on-premises, hybrid or cloud environments. It also notes that Office Add-ins leverage the power of Office 365 services like Office, SharePoint and Exchange Online. The document outlines the basic steps to register an Office Add-in application in Azure AD including mapping the application to the actual web service and setting the necessary permissions.

ECS19 - Serge Luca - MICROSOFT FLOW IN REAL WORLD PROJECTS: 3 YEARS LATER AN...European Collaboration Summit

This document summarizes a presentation given by Serge Luca on Microsoft Flow after 3 years of use and 9 enterprise projects. It discusses how Flow has evolved from basic automation of Excel tasks to more advanced uses by both citizen developers and professional developers. It provides examples of using Flow for automated timesheets, calling APIs, custom connectors, long running processes, error handling, and integrating with Power BI. While Flow is easy to use and affordable, the document cautions that more advanced uses may require additional licensing or workarounds. It concludes by emphasizing the importance of defining requirements upfront using tools like use case diagrams and activity diagrams to help ensure project success.

ESPC18 Copenhagen session : Energize your application developments with micro...serge luca

More Related Content

What's hot (20)