#SPSHouston Automating your digital workplace proivisioning with #Azure Durable #Functions and #MicrosoftGraph
Download as PPTX, PDF0 likes343 views
The document outlines a presentation by Vincent Biret on automating provisioning in the digital workplace using Azure Durable Functions and Microsoft Graph. It discusses the challenges and benefits of specialized tools in the Microsoft 365 ecosystem, the complexities of provisioning processes, and how Azure Durable Functions can streamline automation workflows. Key topics include user interface choices, automation methods, and the advantages of using Azure services for Office 365 development.
More Related Content
Similar to #SPSHouston Automating your digital workplace proivisioning with #Azure Durable #Functions and #MicrosoftGraph (20)
More from Vincent Biret (20)
#SPSHouston Automating your digital workplace proivisioning with #Azure Durable #Functions and #MicrosoftGraph
- 1. Automating Provisioning For Your Digital Workplace: With Azure Durable Functions & Microsoft Graph SharePoint Saturday Houston 2019 Vincent Biret
- 2. Passionate about technologies, development and community Vincent Biret @baywet bit.ly/vince365 Microsoft Office Dev MVP Azure and Office 365 developer @ 2toLead
- 3. Welcome to the 10th Annual HOU365 Saturday Formerly SharePoint Saturday
- 4. Attendee Checklist • Turn phones off or set the ringer to vibrate • Make FOLLOW @SPSHOU on Twitter • Make sure you are in the correct room • SPSHOU Updates #HOU365 • Bingo Cards are on the schedule • Visit Vendors to complete Bingo Cards • Enjoy the presentations!
- 5. Where is the Social? • Drinks wills be served during the Closing Session and Raffle
- 6. Audience?
- 7. Agenda •Introduction •User Interface choices •Automation choices •Azure Durable Functions •SharePoint specifics •Microsoft Graph •Conclusion
- 8. Ready?
- 9. Context
- 10. 2017201620152014 Over the last years Microsoft focused on delivering more specialized tools Microsoft 365 Ecosystem 201820132012
- 11. Different tools for boundaries Internal External Public It’s important to consider the right tool for the right boundary, and your automation options must account for it as well.
- 12. Overall users are happier with better tools, but it added stress on IT and power users. The effects of more specialized tools Pros •Improved users efficiency •Better capabilities •Faster releases Cons •Context Switching •Licensing complexity •Managing multiple API’s •Administrative lifecycle tasks The first rule of licensing is we don’t talk about licensing
- 13. Provisioning processes can be quite complex and often require to integrate many technologies together. Thankfully the Microsoft Graph provides most of the APIs. What do we want to automate? • Create Office 365 group • Enable Teams on the group • Update the logo • Set security • Create Channels for each project • Create a templated NoteBook for each project • Create a Planner Plan for each project • Add a welcome message • Add all the tabs • Create extranet site collection & sites • Apply a template to it • …
- 14. Building custom User Interfaces in Microsoft 365
- 15. When building custom user interfaces for Office 365, the trick is to find the right balance. Available choices when building custom UI COMPLEXITY C O N T R O L Bots Custom Teams Tabs/SPFx PowerApps Forms
- 16. Benefits of going SPFx/Teams •Modern technologies (react, typescript…) •Open source libraries (PnP & more) •Integrated AuthN & AuthZ •Integrated hosting •Discoverable •High flexibility/control
- 17. UI of the provisioning solution Demo
- 19. Azure Functions is a good complement to Flow/Logic App. Logic App good transition from Microsoft Flow to move from user centric to entreprise grade Available choices when automating O365 COMPLEXITY C O N T R O L App Service Environment Automation RunBooks Custom WebJobs WebApps Functions Logic Apps Flow
- 20. ASE is a great tool to automate things for Office 365, especially if you’re a dev, with almost no limitations Benefits of App Service Environment • Built-in auth (Easy-Auth) • Built-in security (SSL…) • Autoscale • API driven (CORS…) • Built-in connectivity (vnet, vpns…) • Proven technology (6+ years) • Easy to get started • Cheap
- 21. Easy auth, CORS setup, CORS for dev Demo
- 23. Implementing complex workflows was complex with Azure Functions which are designed for quick and simple activities Value proposition of Azure Functions Pros •Cheap •Fast •Simple •Scale extensively Cons •Stateless •Coordination nightmare! •10/15 min limit run time
- 24. A common pattern to chain Azure Function was to use queues Coordinating Azure Functions: Chaining
- 25. A common pattern to chain Azure Function was to use a state repository, each function triggering the next one Coordinating Azure Functions: State Repo
- 26. The pain of coordinating Azure Functions grows exponentially with the number of functions. TRYING TO COORDINATE MANY FUNCTIONS
- 27. Durable Functions remove a lot of pain introduced with regular functions Introducing Durable Functions •All the benefits of « regular » Functions •Code defined workflow •Automates state management •Reports status •Enables new design patterns • Fan out/Fan-in • Chaining • Monitoring
- 28. The Orchestrator leverages a decorator design pattern to « work it’s magic » High level overview Orchestration client State persistence Orchestrator ActivitiesTrigger
- 29. Always remember these key principles toi avoid strange behavior Important things about Orchestrator •Orchestrator WILL run multiple time •Orchestrator ONLY coordinates activities • No random • No time • No async calls • Idem potent logic • Use orchestrator methods to call activities •Activities input/output MUST be serializable
- 30. Azure Durable Functions Orchestrator and Activities, Graph Beta Client Demo
- 32. Authentication & Authorization •Use Azure Active Directory, not ACS anymore • Most of ACS retired a year ago, which is not a good sign for auth part •Use certificate (not secret) authentication • Otherwise, for some endpoints, you’ll get a token, and a 403… ¯_(ツ)_/¯
- 33. The situation is currently painful if you want to leverage Azure Functions and work with SharePoint’s CSOM Laggy SDK/CSOM • CSOM still does not support dot net standard • Azure Functions are now on dot net core 2.x • Most libraries moved to dot net standard • Painful transition ADAL/MSAL on top of that • Functions/Activities can only run for 10/15 minutes
- 34. It is possible to synchronize a webjob and Durable Functions using queues or events. Either to the same orchestrator or a separate one. Laggy SDK/CSOM - solutions • Talk to SharePoint REST APIs & split the code • This Orchestration client State persistence Orchestrator Activities Trigger Events WebJob
- 35. The WebJob for SharePoint and Synchronisation Demo
- 36. Conclusion
- 37. Conclusion •Lot of time saved •Consistency of environments •Self-Service •Deep integration •Money saved
- 38. It only contains 4 questions, 30 seconds of your time Please help me improve this new session http://bit.ly/SPSH2019
- 39. Bit.ly/vince365 @baywet slideshare.net/VincentBIRET Thanks!/Questions? Vincent Biret Office 365 and Azure Developer, 2toLead @baywet Bit.ly/vince365
Editor's Notes
- #7: Mostly Devs and architects that want to know how to implement it. PMO and PMs who want to know how it’s done. Questions: XP with functions XP with SPFx XP with MS Graph
- #9: Gestion des questions, interaction, ok avec ce programme?
- #11: Timing: Just talk about the releases, do not explain what the products do
- #17: Discoverable: Teams Tabs, SharePoint App Pages, Webpart gallery, already in tools users leverage
- #18: Show the application page (create a PMO team and embed as a tab?), show all the controls (pnp), show the SPFx project and react components
- #21: Tip: flows are in fact Azure logic Apps behind the scenes
- #36: Not using event because passing data back (SharePoint) and renewing token (OneNote)
- #38: Money save = dev time saved, less support to provide, better product/service