All About the Microsoft Teams PowerShell Module

Current Version of the Microsoft Teams PowerShell Module is 6.4

Updated June 20, 2024

Updating the Module

Updating the Microsoft Teams module is easy. In an administrator PowerShell session, run the Update-Module cmdlet. Here’s an example showing how to update the Microsoft Teams module to a specific version:

Update-Module MicrosoftTeams -RequiredVersion 6.4.0 -Force

Here are some articles about helper scripts to update Microsoft 365 PowerShell modules, including Teams, to the latest version. Importantly, the scripts clean up by removing old module versions too:

• Update PC with Microsoft 365 PowerShell Modules (Teams, Exchange Online, SharePoint Online, Microsoft Graph PowerShell SDK, etc.).
• Update Azure Automation accounts with Microsoft 365 PowerShell modules.

Version 6.4

Released on June 19, 2024 (another short period since the previous release), V6.4 of the Microsoft Teams PowerShell module adds the ExternalAccessWithTrialTenants parameter to the New/Set-CsTenantFederationConfiguration cmdlet. This is required to support the block for external federation with tenants that only have trial Teams licenses.

Version 6.3

Released on June 5, 2024 (a rather short delay since 6.2), V6.3 of the Microsoft Teams PowerShell module introduces a major change in that the module is only supported on PowerShell V7.2 or later or Windows PowerShell V5.1 or later. I have tested the module on PowerShell V7.4.2 and Windows PowerShell 5.1.22621.2506. The text in the release notes “Module is now supported only in PowerShell 7.2 & later, Windows PowerShell 5.1.” could be better formulated, but PowerShell Core and Windows PowerShell are both supported, providing you have the right version.

Apart from the important change to supported versions, the other changes are:

• Adds AcsResourceId output attribute to the Get-CsOnlineApplicationInstance cmdlet.
• Adds new parameter DefaultFileUploadAppId to [Set|New]-CsTeamsFilesPolicy cmdlets.
• DefaultFileUploadAppId attribute is added in the Get-CsTeamsFilesPolicy output.

Version 6.2

Released on May 17, 2024, V6.2 of the Microsoft Teams PowerShell module doesn’t change very much.

• New app management cmdlets Get/Update-M365TeamsApp and Get-AllM365TeamsApps.
• Updates for Get-CSOnlineUser to include unlicensed users in output. Also, account types previously returned as Unknown are now marked as IneligibleUser. Usually, these are member accounts that don’t have a valid Teams license. Guest accounts are excluded, as are resource accounts and Skype for Business on-premises users.
• New AcsResourceId parameter added to Set/Sync- CsOnlineApplicationInstance cmdlets.
• Bug in Get-CsPhoneNumberAssignment fixed to address bad parsing of ReverseNumberLookup property.

Version 6.1

Released on April 4, 2024, V6.1 of the Microsoft Teams PowerShell module includes a useful addition to the Set-CSTenantFederationConfiguration cmdlet to block all sub-domains of a tenant when setting up a block list (rather than an allow list as described in this article). The other changes include:

• New parameters for the Set/New-CsCallQueue cmdlets to configure courtesy callbacks.
• New Get/New/Set/Grant-CsTeamsMediaConnectivityPolicy cmdlets (another policy to manage).
• New Get/New/Set/Grant-CsTeamsWorkLocationDetectionPolicy (yet another policy…)
• New Get/New/Set/Grant-CsTeamsRecordingRollOutPolicy cmdlet (what can I say…)
• New implementation (modernization) of the Get/Set-CsTeamEducationConfiguration cmdlets.
• Addition of SmsNotifications parameter for the TeamsMeetingPolicy cmdlets.
• Addition of UpdateParentInformation parameter for the TeamsEducationConfiguration cmdlets.
• Addition of parameters to the Set/New-CsCallQueue cmdlets to configure response time service level thresholds.
• Removal of the LocationPolicy attribute from the output generated by the Get-CsOnlineUser cmdlet.

Version 6.0

Released on February 24, 2024, V6.0 of the Microsoft Teams PowerShell module is most unlike the release of a major version of a software product because it doesn’t contain very much that’s new. The release:

• Fixes a problem with access tokens granted by running the Connect-MicrosoftTeams cmdlet.
• Releases the private preview of the Remove-CsUserLicenseGracePeriod cmdlet. This is associated with some license management functionality needed for the various licenses associated with Teams such as Teams Premium.
• Includes the IsInGracePeriod and GracePeriodExpiryDate properties for each plan in the AssignedPlan attribute reported by the Get-CsOnlineUser cmdlet. For example, this command shows the full set of service plans from Teams licenses assigned to a user:

get-csonlineuser -Identity tony.redmond@office365itpros.com | Select-Object -ExpandProperty AssignedPlan

AssignedTimestamp   Capability           CapabilityStatus GracePeriodExpiryDate IsInGracePeriod ServiceInstance
-----------------   ----------           ---------------- --------------------- --------------- ---------------
25/02/2024 16:48:08 M365_COPILOT_TEAMS   Enabled                                False           TeamspaceAPI/NA001
09/02/2024 10:04:56 MCO_VIRTUAL_APPT     Enabled                                False           MicrosoftCommunication…
09/02/2024 10:04:56 TEAMSPRO_CUST        Enabled                                False           TeamspaceAPI/NA001
09/02/2024 10:04:56 TEAMSPRO_WEBINAR     Enabled                                False           TeamspaceAPI/NA001
09/02/2024 10:04:56 TEAMSPRO_PROTECTION  Enabled                                False           TeamspaceAPI/NA001
09/02/2024 10:04:56 TEAMSPRO_MGMT        Enabled                                False           TeamspaceAPI/NA001
09/02/2024 10:04:56 TEAMSPRO_VIRTUALAPPT Enabled                                False           TeamspaceAPI/NA001
14/09/2023 21:49:26 MCOProfessional      Enabled                                False           MicrosoftCommunication…
14/09/2023 21:49:26 Teams                Enabled                                False           TeamspaceAPI/NA001
14/09/2023 21:49:26 MCOEV                Enabled                                False           MicrosoftCommunication…
14/09/2023 21:48:18 MCOMEETADD           Enabled                                False           MicrosoftCommunication…
10/08/2023 09:36:16 MCOEssential         Deleted                                False           MicrosoftCommunication…
10/08/2023 09:36:16 MCOPSTN2             Deleted                                False           MicrosoftCommunication

Version 5.9

Released on January 24, 2024, V5.9 of the Microsoft Teams PowerShell module. The big change is the addition of support for managed identities for the policy management cmdlets inherited from the Skype for Business connector (the *-cs cmdlets, like Get-CsTeamsMessagingPolicy). This allows the policy cmdlets to run in Azure Automation runbooks. A small number of cmdlets from the Teams module do not support managed identities. Other changes include:

• Performance improvements for the Get-CsOnlineUser cmdlet in GCC and DoD environments.
• The Set-CsTeamsMeetingConfiguration cmdlet now supports enabling or disabling anonymous meeting participants to receive surveys using FeedbackSurveyForAnonymousUsers parameter. This change supports message center notification MC703705 (4 January 2024).
• The unused DomainController (on-premises!!) parameter is removed from a number of cmdlets where the parameter persisted.

The change to support policy cmdlets is sufficient to warrant a fast update to V5.9.

Version 5.8

Released on November 16, 2023, V5.8 of the Microsoft Teams PowerShell module doesn’t contain any earthshattering changes.

• The Get-MultiGeoRegion cmdlet returns the PreferredDataLocation and LastMovementTimeStamp properties for a user or group (but only in a multi-geo deployment).
• A bug in the Set-Team cmdlet that stopped the updating of the GiphyContentRating control is fixed.
• The ContentSharingInExternalMeetings and UseMicrosoftECDN parameters are now available for the New|Set-CsTeamsMeetingPolicy cmdlet.
• The NumberOfResultsToSkip parameter (deprecated earlier) comes back to the Get-CsOnlineLisLocation and Get-CsOnlineLisCivicAddress cmdlets.

Version 5.7

Released on October 17, 2023, V5.7 of the Teams PowerShell module contains the usual mixture of tweaks, bug fixes, and cmdlet refreshes:

• The deprecated ExternalAccessPrefix and OptimizeDeviceDialing parameters are no longer available with the New/Set-CsTenantDialPlan cmdlets.
• The Get-CsTenantDialPlan cmdlet now returns the correct format of dial plan policy.
• The Get-CsOnlineUser cmdlet now outputs the AdministrativeUnitReference property holding an array of identifiers for the Entra ID administrative units a user account belongs to.
• Fixes the Connect-MicrosoftTeams cmdlet to display the correct tenant identifier after authenticating with a Managed Identity.
• Fixes an error in Sync-CsOnlineApplicationInstance output.
• Delivers a new (modernized) implementation of the *-CsTeamsVdiPolicy cmdlets. Functionality remains the same as previous implementation.
• The Get-CsPhoneNumberAssignment cmdlet now outputs the NumberSource property.
• The New/Set-CsTeamsMessagingPolicy cmdlets support the CreateCustomEmojis and DeleteCustomEmojis parameters. Obviously these parameters are to control some exciting functionality.
• The New/Set-CsTeamsMeetingPolicy cmdlet now supports the ParticipantNameChange and AutoRecording parameters.
• Fixes a bug in the Get-Team cmdlet where duplicate progress record appeared.
• Fixes token expiry issue with Get-Team cmdlet.

On October 20, 2023, Microsoft released version 5.7.1 of the Microsoft Teams module. They didn’t say what problem created the need to patch V5.7 so quickly after its release.

Version 5.6

Released on September 14, 2023, V5.6 of the Teams PowerShell module contains several bug fixes and some new cmdlets. Here’s what’s in the release:

• The Set/Get-CsPhoneNumberAssignment cmdlets support NetworkSiteId for unassigned numbers.
• Fixes bug in Get-CsTenantNetworkSite cmdlet introduced in 5.5.
• Release of new Get/Set-CsTeamsSipDevicesConfiguration cmdlets to manage the configuration of SIP devices.
• Release of New/Get-CsSdgBulkSignInRequest and Get-CsSDGBulkSignInRequestsSummary cmdlets.
• Release of New/Get/Set/Remove-CsTeamsCustomBannerText cmdlets.
• Updates the Get/Set-CsTeamsMeetingConfiguration cmdlets
• New CopyRestriction and CopilotWithoutTranscript parameters added to New/Get-CsTeamsMeetingPolicy cmdlets.

Version 5.5

Microsoft released Version 5.5 of the Teams PowerShell module on August 2, 2023. Like most of the recent monthly releases, this is a fit and finish update. The changes are:

• Release of the New-CsTeamsHiddenTemplate cmdlet.
• Release of the New|Get|Set|Remove]-CsTeamsTemplatePermissionPolicy cmdlets.
• New IncludePhoneNumbers parameter is available for the Get-CsTenantNetworkSite cmdlet.
• Deprecation of the EnableShiftPresence parameter from the TeamsShiftsPolicy cmdlets.
• New implementations (modernized) of the [Get|Set]-CsTeamsUpgradeConfiguration, [Get|Set|Remove|New]-CsTeamsComplianceRecordingPolicy, [Get|Set|Remove|New]-CsTeamsComplianceRecordingApplication, and New-CsTeamsComplianceRecordingPairedApplication cmdlets

Version 5.4

Microsoft released Version 5.4 on July 13, 2023. This release can be categorized as a fit and finish update. The major changes are:

• Fixes for Set-CSUser and other cmdlets.
• Adds a State output attribute to the Get-CsTeamsShiftsConnectionTeamMap cmdlet.
• Addition of the Remove-CsTeamsShiftsConnection cmdlet.
• Updates for the Set/Get-CsPhoneNumberAssignment cmdlets to support AssignmentCategory.
• Updates for the Set-CsPhoneNumberAssignment cmdlet to support the l;ocation updaate for unassigned numbers.

Version 5.3

Microsoft released Version 5.3 on June 19, 2023. The release mostly updates support for cmdlets dealing with the Teams Shifts app and includes:

• Adds State parameter and Output attributes to the *-CsTeamsShiftsConnection and *-CsTeamsShiftsConnectionInstance cmdlets.
• Introduces the *-CsTeamsMeetingTemplatePermissionPolicy cmdlet set to manage Teams meeting templates.
• Releases the Get-CsTeamsFirstPartyMeetingTemplateConfiguration cmdlet. This lists the set of Microsoft-provided meeting templates.
• Releases the New-CsTeamsHiddenMeetingTemplate cmdlet.
• Improves the management of call queue handling by adding new parameters to the Set-CsCallQueue and New-CsCallQueue cmdlets to allow users to set No Agent Opt In/Logged In. New parameters are added for No Agent disconnect/redirection options, target, shared voicemail prompts and whether to enable shared voicemail system prompt suppression and transcription.
• Adds a warning message to the output of the Set-CsPhoneNumberAssignment cmdlet to give information about unlicensed users in their grace period.

Version 5.2

Microsoft shipped Version 5.2 on May 15, 2023. This version includes:

• Modernized versions of several cmdlet sets, including CsTeamsAppPermissionPolicy, CsTeamsAppSetupPolicy, CsTeamsEventsPolicy, CsExternalAccessPolicy, and CsTeamsCallingPolicy. The functionality of these cmdlets remains the same.
• Changes to the Teams Shifts cmdlets.
• Adds the HideAuthorizedUsers parameter to CsAutoAttendant and CsCallQueue New/Set cmdlets.
• Release of the Set|Clear-TeamsEnvironmentConfig and Get|Set-CsTeamsSettingsCustomApp cmdlets.
• Fixes for the ComplianceRecordingPolicy and ComplianceRecordingApplication cmdlets.

Version 5.1

Microsoft shipped Version 5.1 on March 31, 2023. The changes that took my eye are:

• The modernized versions of the Get-CsOnlineUser and Get-CsOnlineVoiceUser cmdlets are now available in GCC High and DoD tenants. TeamsEventsPolicy (needed for webinars) is now included un Get-CsOnlineUser output.
• The meeting policy cmdlets (like Get-CsTeamsMeetingPolicy) support a bunch of watermarking controls needed for the premium feature.
• The messaging policy cmdlets (like Get-CsTeamsMessagingPolicy) support the EnableInOrganizationChatControl and InOrganizationChatControl controls. I don’t have details about what these settings do yet.
• The branding policy cmdlets (like Get-CsTeamsMeetingBrandingPolicy) get a new RequireBackgroundEffect parameter (premium feature).

Version 5.0

This version appeared in early March 2023 and focuses on a major update for the Get-CsOnlineUser cmdlet. See this post for more information.

Version 4.9.3

Issued without notice on January 31, 2023, the changes in this version include:

• Addition of the Certificate parameter for Connect-MicrosoftTeams (fixes some known issues with certificate-based authentication).
• Adds WelcomeTextToSpeechPrompt parameter to [New|Set]-CsCallQueue.
• Fixes issues with pipeline input for Test-CsEffectiveTenantDialPlan & Test-CsVoiceNormalizationRule cmdlets.
• Releases [Get|Set]-CsOnlineVoicemailValidationConfiguration cmdlets.
• Releases [Get|Set|Grant|Remove|New]-CsTeamsMeetingBrandingPolicy cmdlets (for Teams Premium). A known issue exists that prevents using the ‘Remove’ list modifier when trying to delete a TeamsMeetingBrandingTheme or a NdiAssuranceSlate. To remove all elements from MeetingBrandingThemes, the workaround is to set the values to null. For example:

Set-CsTeamsMeetingBrandingPolicy -Identity <Identity> -MeetingBrandingThemes $null -DefaultTheme ""

• To update Meeting branding themes, use the Set-CsTeamsMeetingBrandingPolicy cmdlet and pass the list of desired branding themes created with New-CsTeamsMeetingBrandingTheme (this somewhat clumsy implementation will be fixed in the next release). Example:

$exampleMeetingBrandingTheme = New-CsTeamsMeetingBrandingTheme -DisplayName "exampleTheme" -LogoImageLightUri "https://contoso.com/light.jpg" -LogoImageDarkUri "https://contoso.com/dark.jpg" -BackgroundImageLightUri "https://contoso.com/backgroundlight.jpg" -BackgroundImageDarkUri "https://contoso.com/backgrounddark.jpg" -BrandAccentColor "#000000" -Enabled $true -Identity "exampleTheme"
Set-CsTeamsMeetingBrandingPolicy -Identity <Identity> -MeetingBrandingThemes @($exampleMeetingBrandingTheme) -DefaultTheme "exampleTheme"

• Releases [New]-CsTeamsMeetingBackgroundImage cmdlet.
• Releases [New]-CsTeamsMeetingBrandingTheme cmdlet.
• Releases [New]-CsTeamsNdiAssuranceSlate cmdlet.
• Delivers a new implementation of [New|Get|Set|Remove]-CsTeamsCallHoldPolicy, [New|Get|Set|Remove]-CsTeamsEmergencyCallingPolicy, [New]-CsTeamsEmergencyCallingExtendedNotification. The functionality remains the same as in the previous implementation.

Version 4.9.1

An unusual interim update released on November 15, 2022, V4.9.1 of the Microsoft Teams PowerShell module contains the generally available implementation of application-based authentication support for the Connect-MicrosoftTeams cmdlet. Several other changes are in the module, including:

• A new implementation of the *-CsTeamsChannelPolicy and *-CsTeamsUpdateManagementPolicy cmdlet sets. The Set- and New-CsTeamsUpdateManagementPolicy cmdlets also gain the UseNewTeamsClient parameter to prepare the way for the preview of the new Teams (V2) enterprise client. The Set- and New-CsTeamsChannelPolicy cmdlets have a new EnablePrivateTeamDiscovery parameter to allow clients to find teams marked as private.
• Fixes problems with authentication token refresh in some cmdlets.
• Adds several properties to Get-CsOnlineUser when run without an identity (for example, CountryAbbreviation).
• Fixes problems with how some cmdlets display properties.
• Fixes the Add-TeamChannelUser and Remove-TeamChannelUser cmdlets so that you can add or remove a user to a shared channel with a UPN rather than an object identifier.

Version 4.9

Released on November 1, 2022, V4.9 of the Microsoft Teams PowerShell module continues the work to modernize the cmdlets from the old Skype from Business Online connector. This work is important because some of the older cmdlets can’t run in environments like Azure Automation. The upgraded policy management cmdlets still aren’t perfect in terms of their support for Azure Automation, but they do work (as illustrated by this example).

The notable changes in V4.9 include:

• Modernized versions of the *-CsTeamsFeedbackPolicy, *-CsTeamsMessagingPolicy, *-CsTeamsMeetingPolicy, and *-CsOnlineVoiceMailPolicy cmdlet sets.
• The Get/Set-CsTeamsEducationConfiguration cmdlets are now GA. This only affects Teams for Education deployments.
• Adds the ExplicitRecordingConsent and ForceStreamingAttendeeMode parameters to the Teams meeting policy cmdlets.
• Adds the Description, PreambleAudioFile, and PostambleAudioFile to the Online voicemail policy.
• Adds the AllowChatWithGroup parameter to the Teams messaging policy.
• Adds the EnableFeedbackSuggestions parameter to the Teams feedback policy.
• Releases the Update-CsTeamsShiftsConnectionInstance cmdlet.

For the record, the Add-TeamChannelUser issue remains unresolved in V4.9. Documentation has not been updated at the time of writing.

Version 4.8

Released on October 11, 2022, V4.8 of the Microsoft Teams PowerShell module is another incremental fit and finish update. Microsoft documents the following in its release notes:

• [Get|New]-CsTeamsShiftsConnectionTeamMap cmdlets – TimeZone attribute added.
• Removes SendEmailFromAddress and SendEmailFromDisplayName input parameters from Set-CsOnlineDialinConferencingUser.Removes AllowAllAcsResources and BlockedAcsResources parameters from Set-TeamsAcsFederationConfiguration.
• Adds ForceListenMenuEnabled parameter to callflow settings in New-CsAutoAttendantCallFlow, New-CsAutoAttendant and Set-CsAutoAutoAttendant. This setting enables the tenant to ignore DTMF/speech inputs while greetings/menu options are played.

I thought that Microsoft was going to fix the bug in the Add-TeamChannelUser cmdlet that prevents a user from another tenant being added to a shared channel when specifying their user principal name – but they haven’t!

Version 4.7

Microsoft released V4.7 of the MicrosoftTeams PowerShell module on September 1, 2022. Unlike V4.6, this is very much a fit-and-finish release and most tenant administrator will not notice the changes because of the lack of impact on mainline cmdlets. Here’s the set of changes as documented in the release notes.

• Fixes issues with process clean-up when using module on PS ISE and dotnet applications.
• General availability of the [Get|New]-CsBatchTeamsDeployment cmdlets.
• Releases [New|Set]-CSTeamsShiftsConnectionInstance, Test-CsTeamsShiftsConnectionValidate support for UKG Dimensions.
• Fixes issues with incorrect token fetch while choosing between multiple accounts using AccountId parameter in Connect-MicrosoftTeams.
• Default values of Conference mode & Presence mode attributes are changed from false to true for New-CsCallQueue cmdlet.

Version 4.6

Microsoft released V4.6 of the MicrosoftTeams PowerShell module on July 29, 2022. Continuing the recent trend, the new version contains a lot of modernization activity as Microsoft seeks to upgrade cmdlets (mainly from the old Skype for Business connector) to match updated standards. Among the changes are:

The Get-CsOnlineUser cmdlet now has an AccountType parameter. For example, to find user accounts:

Get-CsOnlineUser -AccountType User | Format-Table DisplayName

This command returns accounts for user and shared mailboxes. The cmdlet supports “Guest” as a parameter value, but it doesn’t return any guest accounts in my tenant. Some other bits might be needed.

The *-CsTeamsEventsPolicy cmdlet set is added. This appears to be a policy to control webinars, perhaps to move settings for these (and other events) out of the meeting policy.

Get-CsTeamsEventsPolicy

AllowWebinars   : Enabled
EventAccessType : Everyone
Description     : Default policy
DataSource      :
Key             : ScopeClass=Global;SchemaId=;AuthorityId=;DefaultXml=;XmlRoot=
Identity        : Global

Some extra cmdlets to support shared channels are added. For example, the Add-TeamChannelUser cmdlet now takes an optional tenant identifier to allow the addition of a user from an external tenant to a shared channel:

Add-TeamChannelUser -GroupId b647d5ff-3bda-4333-b768-7990084569b6 -DisplayName "📔Teams Practices and Architecture" -User "James.Hoover@O365maestro.onmicrosoft.com" -TenantId 22e90715-3da6-4a78-9ec6-b3282389492b

The Get-SharedWithTeam cmdlet checks if a shared channel is shared with a team:

Get-SharedWithTeam -HostTeamId b647d5ff-3bda-4333-b768-7990084569b6 -ChannelId "19:5-aYUE7mEEoAmK8gzNZDfT6aTmsyh5DXKAWLNP45aks1@thread.tacv2" | fl


GroupId     : b647d5ff-3bda-4333-b768-7990084569b6
DisplayName : Office 365 Adoption
TenantId    : a662313f-14fc-43a2-9a7a-d2e27f4f3478
IsHostTeam  : True

The Get-TeamAllChannel cmdlet returns all channels and their properties found in a team. This cmdlet makes it easier to report channels.

Get-TeamAllChannel -GroupId b647d5ff-3bda-4333-b768-7990084569b6

Id             : 19:212515334493446089249a5a1f7070cb@thread.tacv2
DisplayName    : Microsoft 365 Roadmap items
Description    :
MembershipType : Standard
HostTeamId     : a647d5ff-3bda-4333-b768-7990084569b6
TenantId       : a662313f-14fc-43a2-9a7a-d2e27f4f3478

Id             : 19:2868c84ae7ff43d09197f74ef44b4825@thread.tacv2
DisplayName    : Blog Posts
Description    : Blogs from many places
MembershipType : Standard
HostTeamId     : b647d5ff-3bda-4333-b768-7990084569b6
TenantId       : a662313f-14fc-43a2-9a7a-d2e27f4f3478

Id             : 19:44ecfd5231b44f4baf7bf664c7048e8e@thread.tacv2
DisplayName    : Project Hydra
Description    : Discussions about the Hydra Project
MembershipType : Private
HostTeamId     : a647d5ff-3bda-4333-b768-7990084569b6
TenantId       : a662313f-14fc-43a2-9a7a-d2e27f4f3478

Id             : 19:5-aYUE7mEEoAmK8gzNZDfT6aTmsyh5DXKAWLNP45aks1@thread.tacv2
DisplayName    : 📔Teams Practices and Architecture
Description    : Discussions about the most productive practices and architectural decisions in Microsoft Teams
                 deployments
MembershipType : Shared
HostTeamId     : b647d5ff-3bda-4333-b768-7990084569b6
TenantId       : a662313f-14fc-43a2-9a7a-d2e27f4f3478

The Get-TeamIncomingChannel cmdlet reports if a team has access to shared channels hosted in other tenants:

Get-TeamIncomingChannel -GroupId 5b617155-a124-4e32-a230-022dfe0b80ac

Id             : 19:qxTeKg0KEuJTNd9S-d75-dq4gJz30bdhSg4HOKBRj3Y1@thread.tacv2
DisplayName    : 📔Teams and Groups Discussion
Description    :
MembershipType : Shared
HostTeamId     : 2713f078-45a7-4b86-a548-d97870ad2b70
TenantId       : 22e90715-3da6-4a78-9ec6-b3282389492b

The Get-AssociatedTeam cmdlet reports the set of teams a user has access to, including teams hosting shared channels in another tenant (like the last team in the example listing):

Get-AssociatedTeam -User Ken.Bowers@office365itpros.com

GroupId                              DisplayName         TenantId
-------                              -----------         --------
82ae842d-61a6-4776-b60d-e131e2d5749c Rugby Lovers        a662313f-14fc-43a2-9a7a-d2e27f4f3478
bda4f6ed-f102-4a23-a2f7-ef363f45ded6 Sales Team          a662313f-14fc-43a2-9a7a-d2e27f4f3478
fee4a526-fd91-46e9-a45b-cdb92f929602 Corona Virus News   a662313f-14fc-43a2-9a7a-d2e27f4f3478
9367a82e-9c65-4258-86fb-c2eb304c79ef Privacy Advocates   a662313f-14fc-43a2-9a7a-d2e27f4f3478
50a43aed-4a24-4925-a2f4-6545e63a066d James Hoover Team   22e90715-3da6-4a78-9ec6-b3282389492b

The Get-TeamTargetingHierarchyStatus cmdlet is also released, but I don’t see how this is used.

Version 4.5

On July 1, 2022, Microsoft published V4.5.0. This release doesn’t contain anything earthshattering and is largely devoted to a set of fixes and enhancements (see the release notes). The Get-CsOnlineUser cmdlet now supports a SoftDeletedUsers parameter to list soft-deleted Azure AD accounts enabled for Teams:

Get-CsOnlineUser -SoftDeletedUsers | ft Displayname, SoftDeletionTimestamp

DisplayName   SoftDeletionTimestamp
-----------   ---------------------
Maurice Keane 01/07/2022 10:17:13

The Teams module doesn’t contain a cmdlet to restore a soft-deleted account. To do that, you’ll need to use a cmdlet like Restore-MgDirectoryDeletedItem as described in this article.

Version 4.4.1

On June 1, 2022, Microsoft published V4.4.1. This follows the release of 4.3 in May (not much happened in that version). Work continues to modernize the old Skype for Business policy management cmdlets and to fix bugs. The most important changes in this release are:

• The Get-CsOnlineUser cmdlet now returns null values if a user doesn’t have an explicit policy assigned (in other words, they use the default tenant policy).
• The Get-CsPhoneNumberAssignment cmdlet returns new City and IsoSubDivision attributes.

In reality, not much to report…

Version 4.2

On April 13, 2022, Microsoft published V4.2 of the Microsoft Teams PowerShell module in the PowerShell Gallery. The release notes for the module are sadly deficient in terms of the clarity and completeness of the information they offer about the changes. I’ve noted these concerns to the Teams developers because it doesn’t take much effort for a program manager to write up some concise and coherent notes instead of grabbing a bunch of developer comments about changes. Here’s my interpretation of the changes:

Proxy support for all the cmdlets relevant for Teams. The supported cmdlets are being gradually rolled out.

In other words, Microsoft has deprecated some old cmdlets only used for managing Skype for Business Online. These cmdlets will be removed from the MicrosoftTeams module over the next few months.

Fixes issues with [New|Set]- modernized Policy cmdlets when used with PSListModifier type parameters.

This is an internal fix which shouldn’t affect scripts.

[BREAKING CHANGE] PSListModifier type parameters will only accept Hashtable with Add or Remove. Hashtable with Replace is not supported now, instead value(s) can be set directly in the parameter.

PSListModifier is a helper class used by many cmdlets to manipulate lists (for instance, the set of email addresses assigned to a mail-enabled recipient). Instead of passing simple values in parameters to update lists, you need to use hash tables.

Fixes format issues with [Get|New]- of few modernized Policy cmdlets (CsVideoInteropServiceProvider, CsInboundBlockedNumberPattern, CsTeamsComplianceRecordingApplication, CsTeamsTranslationRule, CsTeamsUnassignedNumberTreatment, CsVoiceNormalizationRule).

Improved performance of pipeline input processing with the modernized cmdlets.

A modernized cmdlet is one that is REST-based (AutoRest-generated) instead of communicating with the server using the older PowerShell remoting method. Some of the cmdlets needed a little help to improve their performance.

Fixes minor issues with pipeline input results.

Apparently, the fix makes sure that Catch handles errors correctly.

Get-CsOnlineUser: Country attribute (known as CountryOrRegionDisplayName in versions earlier than 3.x.x), is added.

[BREAKING CHANGE] Get-CsOnlineUser: CountryAbbreviation attribute is now only available when used with -Identity parameter.

Both these changes are due to an update to an internal store. You should update scripts to use Country instead of CountryOrRegionDisplayName and make sure that the identity parameter is passed to Get-CsOnlineUser when you want to see the CountryAbbreviation attribute. For example:

(Get-CsOnlineUser -Identity Kim.Akers@Office365itpros.com).CountryAbbreviation

[BREAKING CHANGE] Get-CsOnlineVoicemailPolicy returns data for MaximumRecordingLength in string format instead of TimeSpan.

The change from date time to string output might break some scripts.

Updates in Version 4.0

Version 4.0 of the Microsoft Teams PowerShell module is mostly a fit and finish release. This update marks the completion of the work to modernize the old policy management and voice cmdlets inherited from Skype for Business Online to versions that don’t use remoting. The new versions of the cmdlets should be more stable than their predecessors. Other changes include:

• Release of the *-CsCallingDelegate and *-CsUserCallingSettings cmdlets.
• The InMemory switch is no longer supported for any cmdlet except New-CsVoiceNormalizationRule.
• The following cmdlets are deprecated: ConvertTo-JsonForPSWS, Set-CsUserServicesPolicy, [Get|Set]-CsNetworkConfiguration, [Set|Remove]-CsTenantNetworkConfiguration, New-CsNetworkMediaBypassConfiguration, [Get|Grant|New|Remove|Set]-CsTeamsVerticalPackagePolicy,[Get|Remove|Set]-CsVoiceNormalizationRule.

It doesn’t appear that Microsoft has done any work to the cmdlets used to create and manage teams. Updates for shared channels were available in version 3.1.1. However, some shared channel operations are still not possible in PowerShell, such as inviting a team to join a channel.

Updates in Versions 3.0-3.1.1

Most of the work on the Microsoft Teams PowerShell module since 2.6.0 has focused on the older policy cmdlets inherited from the Skype for Business like Grant-CsApplicationAccessPolicy. The work converts the cmdlets from using remoting (based on the WS-Management protocol) to a more modern implementation better suited for cloud environments. Some performance issues have also been addressed. So far, there are no reports of any problems with the 3.1.1 version.

Updates in 2.6.0

So far, no known errors have shown up in version 2.6 of the Microsoft Teams PowerShell module. The changes noted in the release notes are:

• Fixes the bug where MicrosoftTeams module lookup failed if made a nested module of another custom PowerShell module. Now, MicrosoftTeams cmdlets are available even if it’s a nested module of another module.
• Releases [Get|New|Complete|Clear]-CsOnlineTelephoneNumberOrder cmdlets.
• Releases Get-CsOnlineTelephoneNumberCountry and Get-CsOnlineTelephoneNumberType cmdlets.
• Releases new parameters for these cmdlets : Get-CsOnlineApplicationInstance, New-CsExternalAccessPolicy, New-CsTeamsAppSetupPolicy, New-CsTeamsCallingPolicy, New-CsTeamsCallParkPolicy, New-CsTeamsMeetingPolicy, New-CsTeamsMessagingPolicy, Set-CsTeamsAppSetupPolicy, Set-CsTeamsCallParkPolicy, Set-CsTeamsGuestMessagingConfiguration, Set-CsTeamsMeetingPolicy, Set-CsTenantFederationConfiguration, Set-CsExternalAccessPolicy, Set-CsTeamsCallingPolicy.
• Fixes the failure that occurred when retrying login with Connect-MicrosoftTeams after an incorrect sign-in attempt.
• Fixes Add-TeamChannelUser and Remove-TeamChannelUser failing for private channel.
• Updates to make the module’s release notes available in PowerShell Gallery for each new version.

Updates and Issues in 2.5.0

Here are some details of the changes in the 2.5.0 release of the Microsoft Teams PowerShell module:

• Updates for AccessToken login with Connect-MicrosoftTeams. The Access Token login for the Connect-MicrosoftTeams cmdlet now uses a unified token array instead of separate parameters for each resource access token. Some fixes are also included for interactive logins using Connect-MicrosoftTeams in CloudShell.
• Improvements to New-Team cmdlet for team creation scenarios. The improvements are bug fixes to address issues reported when running New-Team to create new teams. However, the improvements appear to have introduced a new set of issues (see below).
• TeamsUnassignedNumberTreatment cmdlets are now available. No further details are available.
• The Get-CsCsOnlineDialInConferencingBridge and Set-CsOnlineDialInConferencingBridge cmdlets are available (if you have Teams Voice licenses).
• “Modernized” (Graph-based) versions of the Get-CsTenant and Get-CSOnlineUser cmdlets (using the identity parameter only) are available. The Get-CSOnlineUser cmdlet, which returns details of a Teams user and the policies assigned to their account, is often used in scripts. Modernization should ensure that output is the same as the old version of the cmdlet but experience tells that this is sometimes not the case, so it is wise to test scripts which use the cmdlet to validate that everything works as expected. For instance, the LineURI property no longer has a “Tel:+” prefix.

Updates in 2.3.1

The changes in the V2.3.1 of the Microsoft Teams PowerShell module are mostly bug fixes and don’t stretch to much new functionality. Here’s what’s important:

• A new cmdlet (Get-MultiGeoRegion) is available to get the multi-geo region for teams and groups. This is part of the Teams support for multi-geo organizations announced at Ignite 2021.
• The release notes for V2.2.0 preview said that another new cmdlet (Get-LicenseReportForChangeNotificationSubscription) would “get details of total change notification events that can be sent to users,” whatever that means. This cmdlet hasn’t made it into V2.3.1.
• The V2.2.0 preview also discussed some internal engineering in the refactoring of remote session management. As Microsoft observed at the time, this change should result in no functional change for tenant admins. There’s no mention of this work for V2.3.1, but Microsoft does say that they have fixed “a large latency issue while remoting commands,” which could be connected.
• General availability for the cmdlets to manage custom group policy assignments. Group policy assignments mean that organizations can build packages (sets) of policies to assign to groups (security groups, Microsoft 365 groups, or distribution lists). Microsoft includes some standard packages in Teams. If you want to build custom packages, you need the famous Teams Advanced Communications license.
• Microsoft notes “updates to input parameters and output formats” for many cmdlets. This appears innocuous (and seem to affect policy cmdlets like Get-CsTeamsMeetingPolicy and Get-CsTeamsMessagingPolicy) but might affect scripts which depend on a certain parameter being passed or returned data being in a certain format. Changes like this underline the need for testing against a new module.

Because of the bug fixes included in module updates, we recommend you download and test your scripts against the latest version of the Teams PowerShell module as soon as convenient. If the tests prove successful, then you can deploy the new module into production.

Retirement of old Skype for Business Online Cmdlets

Microsoft upgraded the Teams module to 2.0 in March 2021. This was a big update because it marked the incorporation of the cmdlets from the old Skype for Business Online connector. Replacing the Skype for Business Online connector with the Teams PowerShell module means that tenants must upgrade their scripts to ensure that the correct module is loaded. Although the New-CsOnlineSession is no longer necessary to connect to what is now effectively the Teams policy endpoint, the other cmdlets previously accessed through the connector are available after Connect-MicrosoftTeams runs to create a new session. A big advantage is that there’s no need to run the Enable-CsOnlineSessionforReconnection cmdlet to stop the session timing out after an hour.

---

Stay acquainted with all the moving parts of Office 365 by subscribing to the Office 365 for IT Pros eBook. Monthly updates mean that we stay ahead of the game in terms of warning our readers when they need to take action.