16,636 views
Microsoft 365, Teams, OneDrive and SharePoint Online create additional storage locations for files. However, users are unclear about which files should still be stored on the file server and which files can be stored in Teams or SharePoint. The result: Teams proliferation. The answer to the question of what a practical solution looks like is, as is so often the case: It depends... Only a clear concept against the background of a defined use case helps here. In the video, I present a detailed demo of a concept for setting up a central file storage facility for project-oriented companies. This concept combines a structure of project directories on a SharePoint site with user access from Teams channels. The focus here is on the possibility of cross-departmental access and considerations of the data lifecycle from the initiation phase of a project to the service phase. In addition, I use a flow in Power Automate to automatically create the project folders and subdirectories. This is triggered from a central project list (Microsoft Lists) and ensures that the file storage is structured the same across all projects. And this also provides the most important factor for high user acceptance, namely clarity in the file storage. Summary of the solutions in this video: Microsoft Teams for user access to file storage Microsoft SharePoint Online for central file storage Microsoft Lists for maintaining a central project list Power Automate for automatically creating the project folder structure for new projects 00:00 Introduction to Teams file storage 01:13 Requirements for file storage 04:10 Central SharePoint project folders 07:17 Teams in connection with SharePoint storage 10:08 Multichannel communication with files 14:30 Creating a folder structure with Power Automate 22:47 Recommendations for file storage in Teams 24:07 Video recommendations for Teams and SharePoint Online