When enabling the Teams license in Office 365, every member within the organisation can create Teams. To prevent uncontrolled growth of Teams, it is a best practice to disable the creation of Teams and put in place a provisioning engine instead.
In SharePoint Online, for a list or document library, it is possible to define default metadata values based on the folder where an item or document is added.
As with a lot of cases in SharePoint, the defaults are set on subfolders with inheritance. On every folder-level it is possible to break the inheritance and define other default values for your metadata.
In the example below we work with a Managed Metadata field, called customer, we need to default. This way our co-workers don’t need to specify the value everytime they create or upload a document to the document library.
There are two ways to make the magic happen. Through the user interface, and with Powershell.
In Sharegate, having the full license (!), it is possible to run PowerShell scripts. In this script we could read a CSV-file to bulk migrate document libraries, lists or sites.
This can speed up the migration time, since you would only need to specify the objects once in a simple CSV-file instead of manually going through every object one by one, which is very time consuming.
In this example, we will perform a bulk incremental update (only copy the item if it is newer in the source than the corresponding item at the destination) of some document libraries from an on premise environment to different Site Collections in SharePoint Online.
The reports can be found in Sharegate as well, through the “Migration reports” button in the Ribbon.
In some scenarios it is required to put a site in read only-mode, for example a project site, or to simply just remove access to it.
From the SharePoint Online Admin Center there is no way to lock your site, or to put it in read-only. There are two ways to achieve this, one is through Powershell, the other one through the Site Settings of your Site Collection.
A customer of mine had the need to get an overview of all the checked out documents for a given Site Collection, and to check them in afterwards prior to a content migration from SharePoint 2013 to SharePoint Online.
Since no out of the box features exist to accomplish this goal, I had to write a Powershell-script to find all the checked out documents in a Site Collection.
You can find the script here. It works for SharePoint Online as for SharePoint 2013. I did not test it with SharePoint 2010.