vincent biret azure functions and flow (ottawa)

aOS 2017Canadian Tour

Fueled by

QuebecMontrealOttawaToronto

February 6February 7 February 8February 10

Introduction to Azure Fonctions

and Microsoft FlowOr reliable and fast development

Vincent BiretMVP Office Servers and Services

Cloud Architect @ 2ToLead@baywetbit.ly/vincentbiret

Thanks !

Fact – it’s hard to find good devs

Fact – dev can get complex

Fact – costs increase rapidly

• Customizing SharePoint Workflows with SPD?

• Developing WF with Visual Studio?

• Maintaining a WF infrastructure?

Your experience?

• SharePoint workflows are a complicated thing

• Limited to SharePoint

• Software development is costly

• Reusing what already exists

Why this session?

The TeamUsers Devs

• Demo (“broken bridges” solution)

• Introduction to Microsoft Flow

• Introduction to Azure Functions

• Conclusion

Agenda

Ready?

Text messages volonteer

Demo“broken bridges” solution

Microsoft FlowOr workflows that actually work

• User based workflow solution

• 91 services integrated as of today

• Web editor

• You can leverage on prem data via a gateway

• Steps based concept

• Numerous templates already available

Description

Some Services

• Free – 750 ex/month, 15 min

• Plan 1 – 5USD/u/m – 4500 ex/month, 3min

• O365 or D365 – free – 2000 ex/month, 5 min

• Plan 2 – 15USD/u/m – 15 000 ex/month, 1 min

Pricing

DemoThe Approbation flow

• Performances are not guaranteed

• Delivery is not guaranteed

• User based execution context

• No import/export

• Inconstancies Folder/SPItem

Some remarks

• WebHooks to start the flows

• Private API’s => use of swagger + AAD app

• Public API’s => Swagger (Icone…) => flowdev@microsoft.com

• Catalog => Iframes + URL params system or SDK JS

What about the devs?

Azure FunctionsOr focusing on what matters

• Run « pieces of code »

• Focus on code, nothing else

• Supported by Azure App Service/WebJobs

• .NET is .netcore

Azure Functions

Supported langages

Scenarios

Scenario 2

Available region

Triggers

• One trigger per function

• Can have multiple inputs (SQL, Azure Storage, DocumentDB…)

• Can have multiple outputs (same as inputs + http, SendGrid, Twilio…)

Triggers/Inputs/Outputs

f

WebJob-App Service

Cloud Service

VM

On prem

How to chose?

simplicity

controle

• Web Editor

• Git + Visual Studio• VS 2015 update 3• Azure SDK 2.9.6 +• Web dev tools• https://aka.ms/azfunctiontools (SDK in preview)

• #r ‘’Newtonsoft.Json’’

Tools

DemoFunctions: inspector localisation, web editor, Visual Studio (if we have time)

Flow + FunctionsBest practices

• WebHooks (both ways)

• Simple API (limitations)

• API + swagger

• API + Swagger + PowerApps

Multiple integration options

ConclusionI swear, I’m going to stop talking soon and let you free

• Native access to tons of services and data

• Short developement cycles

• More power to users

• Time saved

• Money saved

Conclusion

Thanks!/Questions?Bit.ly/vincentbiret @baywet slideshare.net/VincentBIRET