- Vincent Biret -@baywet
- Franck Cornu - @FranckCornu
This solution was first designed to avoid SharePoint sites sprawling resulting of an uncontrolled Teams deployment inside an organisation. By 'uncontrolled' we mainly refer to Teams containing organisation reference or critical documents without any kind structure or metadata making hard for users to find them outside this specific Teams (data isolation).
A provision solution can, of course, also serve many other purposes. You can also refer to this article to know more about this topic: https://laurakokkarinen.com/teams-and-sharepoint-provisioning-what-why-and-how/
This tutorial only provides the very minimum building blocks to create a working provisioning solution for Office 365 groups. Feel free to adapt it according to your context and requirements.
Here are the covered topics during this tutorial:
- Use Microsoft Graph and SharePoint APIs to create and configure Office 365 groups.
- Use Azure back end services to run the provisioning logic.
- Create and use SharePoint web hooks.
- Create a SharePoint search experience for created groups.
- A subscription to Office 365 developer tenant
- An Azure subscription (Free Trial).
- Azure following permissions
- Create AD applications and resource groups
- Office 365
- Create term groups and term sets
- Create site collections
- Node.js 10 (not latest)
- Visual Studio Code
- Postman
- A modern browser (pick one)
- A modern command line tool (pick one)
- SharePoint Online Client Components SDK + PnP PowerShell for SharePoint Online
- Azure CLI
- Dot Net Core SDK 2.2 (installer version)
- (Optional) Azure Functions Core tools 2.X :
npm i -g azure-functions-core-tools@2.7.1149