5 Best Practices to Manage access in MS Teams | Deep Overview 

Hi Ksee!! I wonder if the 100,000 item issue we had in classic SharePoint and breaking inheritance is still an issue in modern SharePoint? This is similar to the concerns with the 5000 view limit threshold and column indexing, seems like Microsoft has been resolving these issue quietly in the background. Definitely worth a test though. Just ensure the test if against a true modern SharePoint site in SPO (vs a classic site within SPO)

Awesome! Thanks for watching

awesome, hope this sparks some ideas...let me know if there are questions, or additional scenarios I should vlog about

awesome! awesome! awesome...so glad it was helpful.

yes, I see your point. I think it is one of those things that are not obvious, and as soon as there is a different security use case, normal users are creating private channels or other teams, which IMO breaks the context of the other data, and also creates multiple options for the user to store the data. The fact that you can lock down a folder from other team members, and/or share a specific file/folder with users outside of the team gives a new range of possibilities and keeping the group of files together.

hey Teddy! you're right, the users will do whatever path of least resistance to get it done. I'm learning sometimes the right way takes too many steps and is hard to sustain over time :-)

You're welcome! I'm glad you found the video helpful for your end users. If you have any more questions or need further assistance, feel free to ask.

You're absolutely right! Individually permissioning each file or folder can become very time-consuming and difficult to maintain, especially for large organizations. In such cases, it may be more practical to consider using SharePoint site permissions and SharePoint security groups to manage permissions at a broader level. This way, you can assign permissions to a group of users or stakeholders and apply those permissions across multiple files or folders. It's important to find a balance between granularity and manageability when setting up permissions in Microsoft Teams.

You're welcome! I'm glad the video was helpful to you. If you have any more questions, feel free to ask!

yes! you got it! the Azure AD group used by the MS Team is the same Azure AD group used to manage permissions in the connected SharePoint site. Once I made this correlation, all type of fun stuff opened up. We can now go beyond the implied limits of MS Teams security and cut down on some unnecessary channels and teams. Fun stuff. Keep it clean

You're welcome! I'm glad you found the video helpful. If you have any more questions or need further assistance, feel free to ask.

hello! thanks for watching. You are right, there is not system indicator that the Reports folder is being shared out. This would require inner communication with the team. One other approach that I like to use, is to create two folders right off the bat "admin" meaning only owners can see and "external" meaning folks outside of the team can see. Then configure the security settings accordingly. where where file within these folders would adjust to the security setting for the folder. I love setting up the "alternate security" settings at these parent folder levels, for ease of maintenance and indicators that security is different.

Thanks for the feedback, I'll take a look at this for the next one