Teams and Sharepoint Architecture and practices

Iron Contributor

Hi all,

 

My organization is at the beginning of developing our SP online-based intranet and we want to incorporate and use Teams as a primary way of driving projects and possibly creating long term Team sites for our departments.  Before we go too far, we want to make sure that we have an appropriate architecture and possible "workflows" (not Workflow) to ensure that documents are available and record management is as easy as possible.  We have identified multiple ways that we can see published pages making available major documents (perhaps an approved policies) developed by a group using a Team site.  For instance, do you link from the published site to the teams doc?  Do you migrate the final products or even libraries to an intermediate collaboration site?  Do you move the products or even the libraries to the site with published pages?  Does anyone know of a "best practices" to support Teams integrated SP search, metadata consistency, indexing, records management and such?  I have read that Teams flattens the architecture and I see why.  But I also see difficulties with each option.  So any experience, suggestions or resources that are available would be helpful.

1 Reply
Hi @shawn_fielding

Here is the logical architecture for Teams and Office 365 Groups. Was issued about a month ago.

https://docs.microsoft.com/en-us/MicrosoftTeams/teams-architecture-solutions-posters

Here is a few other articles which should help

https://www.avepoint.com/blog/microsoft-teams/microsoft-teams-sharepoint-site-architecture/ (AvePoint)
https://office365atwork.com/teams/connect-microsoft-teams-with-sharepoint-site/ (AtWork)

To note, certain aspects such as the new Files experience (pulling the full modern SharePoint file experience through) in Teams

https://www.microsoft.com/en-us/microsoft-365/roadmap?featureid=30548

Hope that helps

Best, Chris