This feature request is working its way through the backlog queue. No new details are available yet.
An error occurred while saving the commentBrian commented
Why is Microsoft creating silos within SharePoint - with existing historical drives/files on one side and "Team" files on the other?
In my own company, the Document Libraries replaced the "Drives" of our old, on-premises server. Each drive (main company, subsidiary, HR, etc.) had many sub folders for different operations (marketing, accounting, stats, etc.) that had been accumulating projects and files for years. This separation, however, has made Teams the workspace and our existing SharePoint an historical repository for final documents. That only works if people remember to transfer their files back over once they are done in Teams. What if the Team leader leaves for another job, who's going to remember to transfer the files?
When creating a new Team it would be a great option to select WHERE the files will be saved 1) in Teams as a stand alone as is done now, or 2) in an existing SharePoint folder. There is an option to link to an existing document library but that falls short. That requires linking to existing folders, whereas Teams should be able to create and save new folders/files within the existing SharePoint site.
Example: I have my computer's File Explorer open on one screen and the Teams App open on the other. I also have synced all of the existing SharePoint document libraries to my computer. When I create a new team within the Teams App, I could select to CREATE a new folder for saving documents anywhere within my existing SharePoint site. When I create that folder in the Teams App, it now pops up in my in my synced File Explorer. That new team folder would have a general folder for files. If I create another channel, another folder pops up alongside the general folder and so on.
Now everything is saved and stored in one place but you can CREATE everything in the Teams workspace.