Frequent Contributor

We are rolling out Teams pretty slowly and right now we provide our users with the following functions:

- Calls

- Calendar


The first step was the replacement of WebEx as video conference software. Now we want to take the next step and provide the users with Teams. But since we haven't established a rights management system yet, we have to disable the usage of SharePoint Online files usage. So what we want to provide is:

- Calls

- Calendar

- Teams

- OneNote

- Planner


I know that the OneNotes and Planner are located within SharePoint online or other online services. And I know that Teams don't work with any other data storage besides SharePoint Online.

So is there any way to activate Teams with channels but don't use the files? OneDrive for Business is already disabled for all users. The only idea that comes to my mind is to revoke all Team members the rights for the underlying SharePoint site. Since we established a Power Automate process to create a new Team it would just be another step to do that programmatically.


I know that it would be a far better user experience to provide all the amazing features of Teams. It's just the way it is.



@ThomschUnfortunately a lot of the features you mentioned just aren't possible if the users don't have OneDrive & SharePoint licensing and access. They'd experience jarring failures when they need to directly send any files or present documents in private chats/meetings (needs OneDrive), and without SharePoint they wouldn't be able to do that in team channels or meetings either. OneNote users also require OneDrive since that handles storage and sharing of their notebooks. As for revoking the Team site's permissions, Teams expects associated team site and exchange mailbox permissions to match the standard permissions assigned when a Team is created. If they don't match then features within the Teams app and the connectors that integrate with it (Planner, Power Apps, Forms, Wiki, etc...) tend to break in unexpected ways. I've managed to break permissions on team sites a few times, the one upside was that a lot of people told me about it very quickly.


It's definitely a slog to evaluate the user experience, compliance risk, etc... implications of making a big move to cloud file storage, but I'd consider looking at the available controls and initially rolling out onedrive/sharepoint with heavy restrictions until you reach a higher comfort level and can allow things like external sharing or file downloads.

Can you expand on the implications of other services regarding the revocation of rights from the SharePoint Teamsite?