SPS calgary 2017 introduction to azure functions microsoft flow
•Download as PPTX, PDF•
1 like•538 views
Slides of the session introduction to Microsoft flow and azure functions during SPSYYC. Lean to create no-code powerful workflows and extend those in a matter of minutes with Azure Functions
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to SPS calgary 2017 introduction to azure functions microsoft flow
Similar to SPS calgary 2017 introduction to azure functions microsoft flow (20)
More from Vincent Biret
More from Vincent Biret (20)
Recently uploaded
Recently uploaded (20)
SPS calgary 2017 introduction to azure functions microsoft flow
- 1. Introduction to Microsoft Flow and Azure Functions Or fast cycle development By: Vincent Biret
- 2. 2 | SharePoint Saturday Calgary – 01 APRIL 2017 Sponsors • Special Thanks:
- 4. @baywet bit.ly/vincentbiret Vincent Biret MVP Office Servers and Services Azure and Office 365 developer @ 2ToLead
- 5. Fact – development can get complex
- 6. Fact – costs increase rapidly
- 7. Your experience? • Customizing SharePoint Workflows with SPD? • Developing WF with Visual Studio? • Maintaining a WF infrastructure?
- 8. Why this session? • SharePoint workflows are a complicated thing • Limited to SharePoint • Software development is costly • Reusing what already exists
- 10. Agenda • Demo (“broken bridges” solution) • Introduction to Microsoft Flow • Introduction to Azure Functions • Conclusion
- 11. Ready?
- 15. Or workflows that actually work Microsoft Flow
- 16. Description • 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
- 17. Some Services
- 18. Pricing • 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
- 20. Some remarks • Performances are not guaranteed • Delivery is not guaranteed • User based execution context • No import/export • Inconstancies Folder/SPItem
- 21. What about the devs? • 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
- 22. Or focusing on what matters Azure Functions
- 23. Azure Functions • Run « pieces of code » • Focus on code, nothing else • Supported by Azure App Service/WebJobs • .NET is .netcore
- 25. Scenarios
- 26. Scenario 2
- 27. Available region
- 28. Triggers
- 29. 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…)
- 30. How to chose? f WebJob-App Service Cloud Service VM On prem si m pl ic it y c o n tr o l
- 31. Tools • 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’’
- 32. Functions: inspector localisation, web editor, Visual Studio (if we have time) Demo
- 33. Best practices Flow + Functions
- 34. Multiple integration options • WebHooks (both ways) • Simple API (limitations) • API + swagger • API + Swagger + PowerApps
- 35. I swear, I’m going to stop talking soon and let you free Conclusion
- 36. Conclusion • Native access to tons of services and data • Short developement cycles • More power to users • Time saved • Money saved
- 37. Bit.ly/vincentbiret @baywet slideshare.net/VincentBIRET Please fill evals!! Thanks!/Questions?
Editor's Notes
- Audience: power users, devs, décideurs
- L’objectif c’est que les usagers fassent des flow et demandent aux développeurs des API/functions
- Gestion des questions, interaction, ok avec ce programme?
- Verifier le compte de la personne avec twilio.com/user/account/phone-numbers/verified
- https://flow.microsoft.com/
- https://flow.microsoft.com/fr-fr/pricing/
- Le débuggueur a cessé quand j’ai oublié d’approuver On peut attendre jusqu’à plusieurs minutes sur une approbation https://powerusers.microsoft.com/t5/Flow-Ideas/Flow-export/idi-p/8912 http://social.technet.microsoft.com/wiki/contents/articles/36906.microsoft-flow-and-sharepoint.aspx
- https://flow.microsoft.com/fr-fr/documentation/get-started-flow-dev/ https://flow.microsoft.com/fr-fr/documentation/embed-flow-dev/ https://flow.microsoft.com/fr-fr/documentation/customapi-webhooks/ https://flow.microsoft.com/fr-fr/documentation/register-custom-api/ https://sandervandevelde.wordpress.com/2016/10/09/triggering-microsoft-flow-using-an-azure-function/
- Emphase: faible courbe d’apprentissage car langages très présents dans l’industrie C# et Javascript ceux qui ont le plus d’intégration pour le moment
- Toutes les 15 minutes, data scavenging Event blob storage, transformation du CSV en données, explotation via powerbi Event excel onedrive, creation de graphiques automatisée
- Photo prise qui appelle un webhook, stockage dans le blob storage, redimensionnement des images Implémentation d’un bot via le SDK, commandes mappées à des functions, sortie mappée à des réponses
- Les autres paramètres d’entrées vont être mappés aux paramètres de notre fonction en fonction des noms qu’on fournit
- Expliquer ce qu’est un webhook Modèles de route permettent de réutiliser la même fonction en contextualisant les appels
- https://blogs.msdn.microsoft.com/webdev/2016/12/01/visual-studio-tools-for-azure-functions/ Syntaxe r avec le pool de librairies à disposition Référencer une dll existante comme point d’entrée http://stackoverflow.com/questions/36577584/how-to-put-the-entry-point-of-an-azure-function-inside-a-net-dll
- https://www.visualstudio.com/fr-fr/docs/build/concepts/agents/hosted#software