Microsoft Teams PowerShell Module General Availability

This post has been republished via RSS; it originally appeared at: Microsoft Teams Blog articles.

We are excited to announce the general availability of the Microsoft Teams PowerShell module. This PowerShell module, first released in Beta last year, allows you to manage the lifecycle of teams within your organization. As a Global Administrator or Teams Service Administrator, you can identify and manage teams on behalf of your users, and make bulk updates to teams faster – including changing memberships or managing team settings. This new version of our module leverages only 1.0 Graph APIs.

 

Going forward, we will be maintaining both a Preview and Generally Available versions of the Microsoft Teams PowerShell module. This will allow us to deliver new, preview functionality to our customers faster for testing, while ensuring that our Generally Available module continues to leverage only 1.0 APIs.

 

The following cmdlets are supported in our generally available module:

Cmdlet

Description

Connect-MicrosoftTeams

Connects an authenticated account to use for Microsoft Teams environment

Disconnect-MicrosoftTeams

Disconnects from the Microsoft Teams environment

Get-Team

Retrieves teams with particular properties or information

Get-TeamChannel

Gets all the channels for a team

Get-TeamHelp

Provides a list of commands for Microsoft Teams

Get-TeamUser

Returns the users of a specific team

New-Team

Provisions a new Team, or converts a group to a team

New-TeamChannel

Adds a new channel to a team

Add-TeamUser

Adds an owner or member to the team

Remove-Team

Deletes a team

Remove-TeamChannel

Deletes a channel

Remove-TeamUser

Removes an owner or member from a team

Set-Team

Updates properties of a team

Set-TeamChannel

Updates Team channel information

 

Additional Functionality in New Release
In addition to leveraging solely 1.0 APIs, we have made a few improvements to cmdlets in the Generally Available module:

 

Connect-MicrosoftTeams: You can now specify a Teams Government Environment (-TeamsEnvironmentName) that your organization is homed in.

 

Get-Team: We expanded the filter and selection criteria to include properties such as the Visibility or Archived state of the teams so that you can more easily identify teams that may require your attention

Simplified Experience
To improve the discoverability of certain team settings, we consolidated the functionality of the following cmdlets into the Get-Team and Set-Team cmdlets:

 

- Get-TeamFunSettings
- Get-TeamGuestSettings
- Get-TeamMemberSettings
- Get-TeamMessagingSettings
- Set-TeamFunSettings
- Set-TeamGuestSettings
- Set-TeamMemberSettings
- Set-TeamMessagingSettings

 

Note: These beta cmdlets will not be available in future module releases

 

Want to learn more about PowerShell?
Because Teams is built on top of different services, PowerShell controls for Teams are split across several modules. Learn more about PowerShell for Teams (also includes links to the technical docs for individual cmdlets).

 

Let us know what you think!
If you have suggestions on how to make Teams better, please submit your idea via User Voice or vote for existing ideas to help us prioritize the requests. We read every piece of feedback that we receive to make sure that Microsoft Teams meets your needs.
Christopher Bryan, Microsoft Teams

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.