Forum Discussion
Deleting/Managing SharePoint sites that have been automatically created from MS Teams?
1.) in O365 in the New SharePoint Admin Center you can filter the sites. In the Filter Select "Office 365 group Sites" and it will give you the team sites. All Teams Site is associated with a TEAMS.
2.) If you delete the Site which belongs to a Team, then it will delete the group and all its resources, including the Outlook mailbox and calendar, and any Teams channels. You will have 30 days to restore the group.
3.) By default when you create a New Team, here's what gets created: A new O365 group, a SharePoint Online Site and document library to store teams files, an Exchange Online Shared Mailbox and Calendar, a OneNote notebook. Sadly, I have not come across any article or resource about disabling the link between the Team and SharePoint site. Any document which is shared in that Team or Channels in that team, gets stored in the Document Library and for each channel a folder is created in the document library. You can manage the contents of that Site by enabling the custom scripting options in the TeamSite also If you want to disable FileShare in Teams I am not sure if that is an option for now.
I hope it helps.
Hi Toby McDaid,
1. In the SharePoint Admin Center, how do I tell if a site is linked with a Teams channel? I want to know if the sites listed have been created in SharePoint, or whether they're just a byproduct of someone creating a new Teams channel.
Instead of using the SharePoint Admin Center use the Groups Admin Center. It lists what O365 Groups are Teams connected. See "Teams status" in the image below.
2. If I delete a site that is connected with a Teams channel, would the Teams channel be deleted also?
I believe the Team would be corrupted by this action.
3. Is there any way of disabling the connection between Teams and SharePoint. We want staff to use SharePoint for document management, not Teams. This way we can better control metadata, otherwise people use Teams too informally for document storage and it becomes messy.
You could restrict Teams create to certain security groups but that may not achieve what you are going after. I think guidance and user education are better suited to the task of what document management should look like.
I hope this helps.
Norm