Recommendations To Use Teams In A Better Way - Part One

Introduction

 

“Teams is a collection of people who gather together around a common goal. This group of people may be within a department or across the organization. What brings them together is the outcome they are driving toward. Members of a team may work at a different pace or create assets differently, but in our experience, they often collaborate quickly with each other, a process we call "high-velocity teamwork.” – Microsoft.

 

However, Teams needs a process of validating users, tools, licenses and much more, you must be more proactive to check the limits for each toolset used in teams. Before you start rolling out Teams, admin should assign security and compliance policies wherever applicable.

If you are new to Microsoft Teams, please visit my previous articles to get more understanding on teams- Introduction, Teams Differently, Guest Users In Teams

 

Understanding New Team in Microsoft Teams

 

In this article, we'll understand how the creation of a new Team impacts Administration and which are the best methods to follow to avoid confusion.

• Firstly, the Team name is always public, even for a privately owned team, you cannot modify it later in all internal places.
• If you choose a team name like this “This Is New Team For Sales Support Calls” – it will create a new email at [email protected]. It is annoying, right?

You should prefer to include the prefix for each team by business or department or project names to differentiate from other team names in your organization.

• Do your self-analysis on - is my new team name is already present in company? If yes, choose another name or join an existing team in case it comes under the same context.
• Admin needs to organize teams’ configurations for predefined terms (names) for the team for the overall organization, such as – HR, CEO, Payroll, etc.,

These names will not be allocated to other users of teams, internally it will allocate its own naming convention. For example, If an employee tries to create a new “CEO” team– Team user will not get any warning for an existing team name but his team name will be given a random number, to get more clarity read below step.

• Team naming will especially affect you in the below areas,
  
  
  1. SharePoint site collection
  2. Outlook email address

If you choose to give the same name, then Office365 will give your team a random number at the end of the group as well as the newly created SharePoint site.

 

For example, let’s create a new HR Team in Teams - it generates a new HR group as below.

 

Figure 1: HR team email address generated in Office 365 groups

 

Now, let’s create the same HR group again.

 

Figure 2: Two groups generated in Office 365 groups with the same name but different email addresses

 

Figure 3: Two teams with the same names in Microsoft Teams

 

Now a new name has been given to the SharePoint Site as well.

 

https://<Tenant>.sharepoint.com/sites/HR857/Shared%20Documents/Forms/AllItems.aspx

 

Figure 4: Newly created team gets new SharePoint site with a random number

 

By default, when you create a new team in Teams, it will create a new SharePoint modern site under “/sites/” managed path (… /sites/…). For example, if the team name is TestTeam, then the SharePoint site is, 

 

https://<Tenant>.sharepoint.com/sites/<TestTeam>/

 

It is recommended to create all Microsoft Teams SharePoint sites under “/Teams/” managed path. After the change of this setting, the new team will be created at this address.

 

https://<Tenant>.sharepoint.com/teams/<TestTeam>/

 

To change this setting, visit the SharePoint admin center under the “Settings” option (refer to figure 5).

 

https://<Tenent>-admin.sharepoint.com/_layouts/15/online/TenantSettings.aspx

 

Figure 5: Change new Site creation managed the path from SharePoint Admin Center

• The team should have a minimum of 2 team owners to avoid issues later when one owner is not available to manage.
• By default, every Office 365 user can create a new team in Teams, which will result in a new Office 365 group and a SharePoint Site created behind the scene.

For end-users, it has great flexibility but as an admin, you will be getting a lot of pain points when these groups increase beyond your limits and it will lead difficulty in managing as well higher costs.

 

Check default standard limits for teams mentioned in below figure 6.

 

 

Figure 6: Default standard limits for teams & channels 

 

Suggested workaround - Create an empty security group and then disable Office 365 group creation for all users except this group. Now, add users in this group to whom you want to give group creation or team creation permissions.

 

Summary

 

Creating a team will be a costly matter if it is not well-thought process.