Updated May 31, 2022: This is the final reminder for this upcoming change. Starting June 15, 2022, all Teams PowerShell Module versions earlier than 4.x.x will be retired and will stop working. Please update to the latest Teams PowerShell Module version as soon as possible.
- Teams PowerShell Module versions 4.2.0 & 4.3.0 have also been released with support for Proxy & few additional fixes. More details in Microsoft Teams PowerShell Release Notes.
- While using Teams PowerShell Module versions 4.x.x or later, it’s recommended to not use any of the deprecated or unsupported cmdlets mentioned at Teams PowerShell Module – Supported Versions.
Updated May 05, 2022: We are updating this post as a reminder of this upcoming change and provide additional information you may find helpful:
- Teams PowerShell Module versions 4.2.0 & 4.3.0 have also been released with support for Proxy & few additional fixes. More details in Microsoft Teams PowerShell Release Notes.
- While using Teams PowerShell Module versions 4.x.x or later, it’s recommended to not use any of the deprecated or unsupported cmdlets mentioned at Teams PowerShell Module – Supported Versions.
Upcoming, we will be retiring all Teams PowerShell Module (TPM) versions older than 4.x.x. Instead, we recommend updating the TPM module to the latest version which is where we will continue to invest our resources.
Note: If your organization has already updated to TPM version 4.x.x or above, you can safely disregard this message.
When will this happen
We will begin retiring all Teams PowerShell Module (TPM) versions older than 4.x.x. in mid-June.
How this will affect your organization
After the retirement occurs, administrators won’t be able to use TPM versions older than 4.x.x.
What you need to do to prepare
Update to the latest TPM version (4.x.x or above).
Learn more
- Microsoft Teams > Reference > Teams PowerShell > Teams PowerShell Module – Supported Versions > Deprecated cmdlets
- Microsoft Teams > Reference > Teams PowerShell > Microsoft Teams PowerShell Release Notes
Message ID: MC350371
Published: 31 March 2022
Updated: 31 May 2022
Action required by: 15 June 2022
