One of the great things about Teams is the way that it orchestrates Office 365 resources like SharePoint Online sites. The downside is that a tenant’s valuable SharePoint storage quota might be absorbed by a profusion of Teams. To offset the problem, you can apply lower limits to sites belonging to Teams and the best approach is to use PowerShell for the job.
The modern SharePoint Admin Center introduces the ability to rename the URLs for SharePoint site names. This responds to a longstanding customer request and makes it possible for site names to reflect what users see elsewhere in Office 365 groups or Teams. It’s a small but welcome change in the fit and finish category.
The Teams Admin Center now boasts the ability to delete teams and (if you don’t want to get rid of them altogether) archive teams. And unarchive teams back into use. All is good, even if Microsoft is making slow progress at building out Teams management functionality. Some of the slowness is due to dependencies, some because of other factors.
Every Office 365 group (and team) has a SharePoint site. But how to find the URLs of all the sites used by teams in a tenant. One PowerShell answer came from Syskit, but it’s an old technique and we can do better now by fetching a list of teams in the tenant and then retrieving the URL for each team-enabled group.
It’s easy to create a webhook connector to post information to a team channel or an Office 365 group. What might not be quite so easy is formatting the JSON payload. Here’s how to use a template card to simplify the process.
Teams has released version 0.9.6 of its PowerShell module. You should upgrade to the new module because it fixes some bugs and allows administrators to manage any team, even when they’re not a team owner.
Exchange Online distribution lists can be used to populate the membership of Office 365 Groups or Teams by applying a little PowerShell magic. Here’s how.
A reader asked if it is possible to add an administrator account to every Office 365 Group. This feature doesn’t exists OOTB, but it’s an easy task to script with PowerShell.
Teams offers a number of ways to create new teams, which is good. However, if you create a new team with PowerShell, make sure that you add the team owners to the members list as otherwise they won’t be able to access Planner.
Office 365 doesn’t include a way to export a list of Teams in a form that can be imported by Power BI, but PowerShell makes it an easy task to accomplish. Here’s a script to help solve the problem.