top of page

Governance of 

Microsoft Teams

Microsoft Teams offers a convenient way to collaborate during the time of remote workforce.  It is easy to share documents, collaborate on content together between multiple members, and keeping conversation and meetings happen through the same interface.  

Additionally, Teams offers channels to keep certain members of the group for a particular topic to a designated area.  A private channel is available if the topic or content is confidential to subset of the member.  


With all these flexibilities, however, it also brings a major challenge with MS Teams is in trying to keep your content organized within the larger context.  We know that each team is powered by a SharePoint site, and documents are stored in the default library of that site.  Each channel creates a folder within the library.  Yet, each private channel creates still another SharePoint site for permission control.  All these containers are potentially silo-ed from the main organizational library.  With working copies of these documents generated over time, and various versions created in different containers, information sprawl becomes very challenging to control. 


These are the major components to consider when thinking about governance of MS Teams.


  • The use of Teams - Is the team used or organizational collaboration or project collaboration?

  • Is there a provisioning and decommissioning process for the different purposes of Teams?

  • Is channel used to store content or chat? Is channel "Files" part of the main library file or should they be separate?

  • Are users clear in what content is stored in SharePoint sites outside of Teams vs content stored in Teams? 

Our MS Teams governance solution help you take a deep dive into how your organization is utilizing the MS Teams and SharePoint sites.  We provide a solution to keep content organized over time, so that you can avoid ROT (redundant, obsolete, trivial), dark data and information sprawl over time. 

bottom of page