I recently put out a Twitter poll asking what technique organizations were currently using for creating SharePoint sites/Microsoft Teams in their tenant. Here are the results from 155 votes:
By those numbers, a majority of organizations (61%) are not giving end-users free-reign to create their own SharePoint Site/Teams. I believe the need for a custom provisioning solution, as demonstrated by 27% of the respondents, is 2-fold:
The first part of the need is to expedite the provisioning process rather than funneling all requests thru the IT department to review, meet with the team, and manually provision (34% of the respondents). As we all know, this takes time. Often too much time.
The second part of the need is to inject some governance into the process. There are many ways an automated, controlled provisioning process can aid in good governance across your organization. It may include, but is not limited to, any of these ways depending on the type of site you’re provisioning, the size of your organization, and your own governance requirements:
- to avoid site sprawl
- to ensure duplicate Teams aren’t being created
- to deploy a naming convention
- to deploy a consistent architecture (Site/Information)
- to automatically join to a Hub
- to apply protection/retention/security controls
- to schedule training for new site owners/members
Whatever the reasons are, if you want some organization-specific controls built into your own site provisioning process, but not sure where to start, I’ve curated a list of blog posts relating to the topic to help you out. As with most things in SharePoint, there’s several ways to get the job done with varying levels of difficulty and capability.
Disclaimer: There are excellent third-party products/solutions on the market that can also do auto-provisioning. If you don’t have the required technical skill yourself or available to you, or your organization doesn’t want to take on the technical debt of building your own, one of those products may be a more suitable choice for you.
This blog post is about solutions shared by the technical community