Microsoft Teams Support for your first SharePoint Site requires some basic understanding of sites before proceeding.
- #1: Try to maintain a solid point of view of what Teams is at the end of the day.
- Teams is a box where people chat.
- Teams contains many links to many locations but is not a place to store files. Teams show your team’s files that are store on your team’s “team site” in SharePoint
- Teams greatness is that you have the chat room, and then you have other tabs at the top that allow to see things from other parts of M365 or outside your tenant completely,
- #2: Every action may have a consequence
- Educate the people that are going to use Teams
- Maybe they don’t need need a new team, maybe they need a new channel…
- Do they really need a channel? Implications of that…
- #3: Keep it simple. Don’t complicate things.
- Too often organizations try to roll out Teams and focus on the big picture—which can lead to frustration and low user adoption.
- Don’t overwhelm them. Teams is simply a tool we use to get an existing job done, so make it easy for users to get started. It grows over time.
- #4: Make sure default settings meet your default needs
- not all default settings are configured to what most people want.
- There is no reason to start using private teams if all users can find them and can probably extract some kind of information from the team name alone.
- #5: Look to the needs of the user
- #6: Implementation does not equal a mass adoption
- If users do not get training, they will create unnecessary teams and, eventually, feel overwhelmed. This is classic ‘over adoption’, just like we did with folders in Outlook as well as nested folders in file shares.
- Minimalized teams being created. Less is more. Users need to have training to understand what happens in the background when a team is created or what the purpose of Microsoft Teams is, and fully utilize all the features.
- If they’re not enjoying using Microsoft Teams, belong to gazillions of unnecessary teams, and it doesn’t make their lives easier—then we’re doing this wrong.
Microsoft Teams Support for your first SharePoint Site
The best practice is to create a Team Site via Microsoft 365 Group. The reason behind this method is you can see and edit all the settings, roles, and permissions in one place. By default, the first M365 Group is made when you first received Office 365 as illustrated below in Microsoft Admin Center.
Every time you create a NEW team in Teams, you’re also creating a NEW Office 365 Group, Calendar, Planner, and SharePoint team site.
Then you need to be careful because with a new Team site several entities will add to the Microsoft 365.
You are automatically creating a Microsoft 365 Group when clicking “From Scratch”
Sync Your Desktop to SharePoint
Sync allows to sync files from desktop to cloud but make sure you have the latest version of the desktop
Authenticate with you M365 credentials for desktop to SharePoint cloud sync
As per usual, Microsoft likes to confuse the situation by having two products with the same name.
Do not forget the path on your desktop. It for communal sharing of data with your peers. It is synced to SharePoint.
Good to know file sync statuses.
There’s some on to go mobile app services too!
A building is a shortcut for all your SharePoint data for that site.
Microsoft Teams Support for your first SharePoint Site Summary
You are all set! There are many ways to setup your SharePoint site and sync it to your desktop but this is clearly the easiest. Check out How to use Microsoft Teams with SharePoint & other key features – Network Antics for a complete understanding of what exactly Teams is.