This publish is definitely an excerpt from your latest ebook “Using and Tailoring Microsoft Teams for the Organization.” Download free of charge today!
Browse the other posts within our series below:
Microsoft Teams cloning is really a native feature that enables users to produce new Teams according to existing Teams. It will help your users or IT team replicate the preferred “best practice” settings in one Team to other people.
Teams cloning transfers the member permission settings configured through the Team Owner along with the funnel, tab, and applying the initial Team. However, tabs and connectors have to be reconfigured. A tab (e.g. Planner) will display in the new Team however it will have to be visited, setup, and approved as new for that Team prior to it being used.
Teams cloning doesn’t transfer any content, including messages and files (which may be easily moved while using SharePoint move feature as needed). Team cloning also doesn’t transfer membership—members should be selected by individual users or even the Group for that new Team. Additionally, any kind of policy (i.e. “Team proprietors cannot produce a SharePoint subsite”) can’t be incorporated inside a cloned Team. Consider it as being this is the “shell” that may be replicated inside a new space.
Cloning a group can be achieved in the Microsoft Teams client or programmatically using Microsoft Graph. Watch this on-demand web seminar to learn to clone Teams.
Cloning Teams enables organizations to produce templates for various use cases making it simpler for users to tailor Teams for their communication needs.
However, you will find limitations:
- Teams templates for cloning are tenant wide so each department might find almost every other department’s templates.
- Cloning isn’t enforced.
- Cloning is not able to transfer other key settings which are configured in the Group or tenant level by managers, which we’ll cover within the next section.
Find out more about cloning Microsoft Teams within the full ebook.