This continues to be on our backlog due to prioritization of other work items. We will update when there is more to share.
An error occurred while saving the commentThomas Leibetseder commented
for our business we have either the choice of (A) creating individual teams (and subsequently also sharepoints) for each project OR (B) we use channels (either department or product specific) which can be moved or relocated under a "root directory"as per the actual organizational structure.
version (A) leads to hundreds of individual sharepoints over time which need to be administred separately.
version (B) would give us the chance to define a project portfolio organized according to the actual organization structure, top level administration of users and a possibility of re-organization in case of organization changes which occur frequently over the years or re-organize e.g. according to product types or others simply by copying channels and all related data in behind (planner/tasks, sharepoint data, etc.)
this feature is truly essential for us since we have our project data on network folders which can not effectively be accessed from home office while sharepoint data can be easily accessed from anywhere.