Add ability to create/modify teams with PowerShell
The lack of any options for creating/modifying teams with PowerShell makes it much harder to support.
In my company, users will not be able to create teams themselves due to business requirements but will need to submit a request for a team to be created. As Office 365 administrators, we would rather use a PowerShell script to automate this than do it manually in the GUI.
The same is true for updating existing teams - our options are very limited when it comes to modifying an existing team that we are not an owner of. With other Office 365 services, we have these options in PowerShell.
You’ve been waiting for this feature and now we have it for you!
IT Professionals always look for ways to automate tasks and make daily operations simpler. In November, we released a new PowerShell module for Microsoft Teams that enables you to leverage PowerShell to configure and manage Teams.
The first version of the Microsoft Teams module – version 0.9.0 –includes 23 PowerShell cmdlets that make the administration of Teams easier. You can use the cmdlets for example to automate the creation of teams and channels, to bulk edit users or to set options such as a picture, and member permissions. The PowerShell module for Teams is a big step in our efforts to enable you to manage Microsoft Teams more effectively.
You can read more about it at the Teams’ blog.
10 commentsComments are closed
It would be nice to have a full range of actions for managing Teams through PowerShell. An example, Get-Teams only returns teams you're a member of and not tenant wide list.
As the request to instanziate Teams from a central e.g. Admin role is highly desired -- is the current creation of 250 Teams / per user -- still a limit or already gone by granting admin rights to this role? and if yes -- what is the O365 AD or what ever limt in case only one role is the creator of teams'/o365 groups?
Currently Get-Team in Teams PS v0.9.0 will only return details based on the logged in users. Agree that admins will manage teams to a certain extent need to list all teams.
As confirmed with support. this is expected behavior however not what I expected, or would like to see. ty.
[Deleted User] commented
It got released few days back.
The PowerShell Module for Teams got released, I did a quick overview of it here: https://absolute-sharepoint.com/2017/11/quick-overview-of-the-new-microsoft-teams-powershell.html
Chris Haaker commented
Same here. Until you get tools that allow us to apply rules to Team naming we cannot let users create them so we have to. Automation with PS is essential as is the ability to bulk create Teams vis a script as we move all SfB persistant chat rooms to Teams.
James Rule commented
We have scripts which we use to setup new users + run clearances. At the moment when a staff member is disabled on Office365 they simply appear as "Unknown User" in their existing teams. Would love to be able to Remove-TeamsMembership * to make sure none-users are stuck in teams.
Until the modules are ready I can suggest you to use: https://github.com/sanderdewit/teams-module
Dave Upton commented
Any update on timing or release?
John Grenfell commented
We have the same requirement. I work in an education environment and will be creating Office 365 groups containing students against registers with lectures being the owner. We fear the staff will not link the Team with the correct group. Having the ability to pre populate all the groups and have them "team enabled" via powershell is a must for us.