Introduction to Microsoft Flow and Azure Functions
-
Upload
biwug -
Category
Technology
-
view
103 -
download
0
Transcript of Introduction to Microsoft Flow and Azure Functions
![Page 1: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/1.jpg)
Introduction to Microsoft Flow and Azure FunctionsOr fast cycle development
By: Vincent Biret
![Page 2: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/2.jpg)
![Page 3: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/3.jpg)
Vincent Biret
Passionate about development, community and technologies
@baywetbit.ly/vince365
MVP Office Servers and ServicesAzure and Office 365 developer @ 2toLead
![Page 4: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/4.jpg)
Often we think we need more than what we actually need and end up over-designing
Fact – development can get complex
![Page 5: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/5.jpg)
That’s, and other causes, leads to spending way more than we thought
Fact – costs increase rapidly
![Page 6: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/6.jpg)
Workflows and SharePoint always has been a love and hate story
Your experience?
• Customizing SharePoint Workflows with SPD?
• Developing WF with Visual Studio?
• Maintaining a WF infrastructure?
![Page 7: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/7.jpg)
Let’s try to find better and more enjoyable tools that’ll make us more productive
Why this session?
• SharePoint workflows are a complicated thing
• Limited to SharePoint
• Software development is costly
• Reusing what already exists
![Page 8: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/8.jpg)
Users build flows, developers extend capabilities with Azure Functions
The Team
Users Devs
![Page 9: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/9.jpg)
Agenda
• Demo (“beer locator” solution)
• Introduction to Microsoft Flow
• Introduction to Azure Functions
• Conclusion
![Page 10: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/10.jpg)
Dynamic interactions, don’t be afraid to ask questions, I’ll ask you questions as well
Ready?
![Page 11: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/11.jpg)
Beer locator solution
Update metadata
Obtain the manager
Send approval email
Approbation?
Notify approbation
Determine an agent
SMS Notification
yes
Tweet
![Page 12: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/12.jpg)
“broken bridges” solution
Demo
![Page 13: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/13.jpg)
Or workflows that actually work
Microsoft Flow
![Page 14: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/14.jpg)
Cloud based solution for workflows provided by Microsoft with or without Office 365
Description
• User based workflow solution
• Connectors based (extensible)
• Web editor
• You can leverage on prem data via a gateway
• Steps based concept
• Numerous templates already available
![Page 15: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/15.jpg)
171 connectors to date, most of them are free (might require a service purchase), some require a premium license
Some Services
![Page 16: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/16.jpg)
The Approbation flow
Demo
![Page 17: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/17.jpg)
You can either use it for free, have it as part of your office 365 plan or add it to it
Pricing
![Page 18: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/18.jpg)
Good for 80% of the workloads, I’d avoid it for mission critical workflows for now
Some remarks
• NEW: performances are guaranteed for paid tiers
• NEW: retry policies
• User based execution context
• NEW: import/export as template or logic app
• Inconstancies Folder/SPItem
![Page 19: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/19.jpg)
Devs have multiple ways to integrate, from the one-deal integration to the ISV
What about the devs?
• WebHooks to start the flows
• Private API’s => use of swagger + AAD app
• Public API’s => Swagger/OpenAPI => [email protected]
• Catalog => Iframes + URL params system or SDK JS
![Page 20: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/20.jpg)
Or focusing on what matters
Azure Functions
![Page 21: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/21.jpg)
Microsoft’s response to the serverless opening market, allowing you to run code and just not care.
Azure Functions
• Run « pieces of code »
• Focus on code, nothing else
• Supported by Azure App Service/WebJobs
• .NET is .net standard• backed by runtime 4.7 for now• soon by asp.net core / dotnet core
• NEW: now available in most of the regions
• PREVIEW: integration with MS Graph
![Page 22: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/22.jpg)
Multiple languages supported which lowers the entry cost as the devs in your company probably already master one or two of those
Supported langages
![Page 23: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/23.jpg)
Functions can be triggered periodically, on events, http/webhook or using the bot framework
Triggers
![Page 24: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/24.jpg)
Triggers/Inputs/Outputs
• One trigger per function
• Can have multiple inputs (SQL, Azure Storage, DocumentDB…)
• Can have multiple outputs (same as inputs + http, SendGrid, Twilio…)
![Page 25: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/25.jpg)
The more control you want, the lower in the stack, the more simplicity the higher
How to chose?
f
WebJob-App Service
Cloud Service
VM
On prem
simplicity
control
![Page 26: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/26.jpg)
SDK is still in preview but usefull to implement DevOps and more advanced scenarios
Tools
• Web Editor
• Git + Visual Studio• VS 2015 update 3 + Azure Sdk 2.9.6 + functions SDK
• VS 2017 update 3 + azure dev checked
• #r ‘’Newtonsoft.Json’’
![Page 27: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/27.jpg)
Azure functions are making progress on the DevOps path allowing you to better control the lifecycle
Continuous integration
• Publication via web deploy
• Same as a app Service
• ARM
• NEW: Can (easily) be set up via VSTS
• NEW: Deployment slots are in preview
• **VSTS hosted agent doesn’t have Azure functions SDK for now
![Page 28: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/28.jpg)
Functions: inspector localisation, web editor
Demo
![Page 29: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/29.jpg)
Audit log export project in VS, CI/CD for the project
Optional Demo (if we have time)
![Page 30: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/30.jpg)
Microsoft Graph integration with Azure Functions
Optional Demo (if we have time)
![Page 31: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/31.jpg)
Best practices
Flow + Functions
![Page 32: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/32.jpg)
WebHooks are probably the most straight forward way to integrate both together
Multiple integration options
• WebHooks (both ways)
• Simple API (limitations)
• API + swagger
• API + Swagger + PowerApps
![Page 33: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/33.jpg)
I swear, I’m going to stop talking soon and let you free
Conclusion
![Page 34: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/34.jpg)
Conclusion
• Native access to tons of services and data
• Short development cycles
• More power to users
• Time saved
• Money saved
![Page 35: Introduction to Microsoft Flow and Azure Functions](https://reader031.fdocuments.net/reader031/viewer/2022021503/5a65033f7f8b9a6c118b48f1/html5/thumbnails/35.jpg)
Bit.ly/vince365 @baywet slideshare.net/VincentBIRET Please fill evals! At spsbe.be
Thanks!/Questions?