The net is that we have plenty of time to drink coffee. Unfortunately, the Get-UnifiedGroup cmdlet (often used to retrieve information not returned by Get-Team) is a sloth of a cmdlet too. Microsoft acknowledges that performance isn’t what it should be, and we can hope for improvements in the future. This won’t be a big deal when you only work with a few teams, but it becomes a much bigger problem as the number of teams mounts into the hundreds or thousands. For instance, wildcard matching is unsupported. Second, the filters are client-side rather than server-side and don’t support the kind of filtering functionality that you might be accustomed to with cmdlets like Get-Mailbox. While you retrieve sets of teams with Get-Team, two issues become painfully apparent. You can combine the parameters too: Get-Team -Visibility Private -Archived $True -User Get-Team -Archived $TrueĪccess (public or private): specify the Visibility parameter and set it to Public or Private to retrieve the teams you want: Get-Team -Visibility Public Owned by someone: specify the User parameter and pass the user’s email address: Get-Team -User Īrchived (read-only): specify the Archived parameter and set it to $True to return a set of archived teams or $False to see a set of teams that are not archived. First, Get-Team supports basic filtering capabilities. The big changes in the V1.0 module are in the Get-Team cmdlet. MicrosoftTeams 1.0.0 Get-Team and Filtering Connect-MicrosoftTeamsĪt this point, if you check the module, you should see it report the correct version: Get-Module |?|Select Name, Version
Then, install the V1.0 release from the PowerShell Gallery: Install-Module MicrosoftTeams -Repository PSGalleryįinally, connect to Teams with an administrator account (if you want to work with all the teams in the tenant) or a user account (to work with teams owned by that account). To get the new module, first make sure that you uninstall any of the older versions from your workstation: Uninstall-Module MicrosoftTeams The new module includes some cmdlet changes that might force updates for scripts. Now Microsoft has released the 1.0 version of the module, or the first “generally available” version. Invariably, soon after Microsoft upgraded the portal (for example, to manage teams in September 2018), a new version of the PowerShell module appeared. Over time, Microsoft updated the module (far too slowly for some) to a point where the preview versions 0.9.5 and 0.9.6 offered reasonable functionality.įor much of the time, progress with the module was gated by work Microsoft did on the Teams Admin Center. At the time, I wasn’t too impressed because the module was kind of odd in its approach and didn’t do a great job of managing teams.
February 2022 check before: Product: Microsoft 365 admin center, Power Automate, Purview Data Loss Prevention Platform: Windows Desktop, World tenant Status: Change type: Admin impact Links: Details: On November 2, 2021, the Power Platform started releasing…