As part of our effort to migrate to MS365, we tried to map out all the existing sync and google drive file shares, and all of the existing Co-op service and other work groups. Below is a diagram which captures these approximately (note we are aware it omits Sitka and has Support positioned incorrectly)

Out of this we create a number of MS365 Groups and related Teams that will provide the basic ways for you to share

Coming to understand Microsoft's terminology and how it is implemented in this software was one of the biggest challenges of this migration project because, frankly, it is just plain bad and confusing. This is my (Scott's) attempt at making it a little less so.

The term "groups" and "teams" get used in multiple ways in MS365 and depending on where you create a group, it has different implications and different sets of tools that gets deployed. The main ones we will focus on:

• MS365 Group - this is a group that in our case will almost exclusively get setup by the MS365 admin and should be recognizable as a "workgroup" or core group of people who need to collaborate together, either within a service or sometimes across services. When a MS365 Group is created, users are added to it, and it also creates a related Sharepoint site. This site has the capability of containing "pages" (think web pages that are published, things like central instructions or non-volatile and non-collaborative docs that say a manager would maintain for their team.) As well this sharepoint site has a document library. This will be the primary place for storing documents for that group
• Outlook Groups - these are typically distribution lists. You can create them youself and they can be unique to you or shared in the oprganization. They *only* distribute email. They do not have Sharepoint sites. They are of some use but ultimately will not form the backbone of our colaboration spaces.
• Teams