Retiring Teams Shifts Connection cmdlets from Teams PowerShell Module

Microsoft is retiring Teams Shifts Connection cmdlets in Microsoft Teams PowerShell Module 7.9.0. Organizations using these cmdlets must update or remove dependencies before upgrading, as scripts relying on them will stop working. Those not using these cmdlets are unaffected.

[What and Why:]

Microsoft is removing support for Teams Shifts Connection PowerShell cmdlets in Microsoft Teams PowerShell Module 7.9.0. Organizations that currently use these cmdlets to manage Teams Shifts connector scenarios will no longer be able to rely on them after upgrading to version 7.9.0 or later.

This change affects the following cmdlets:

• New-CsTeamsShiftsConnection, Set-CsTeamsShiftsConnection, Remove-CsTeamsShiftsConnection, Update-CsTeamsShiftsConnection
• New-CsTeamsShiftsConnectionInstance, Set-CsTeamsShiftsConnectionInstance, Remove-CsTeamsShiftsConnectionInstance, Update-CsTeamsShiftsConnectionInstance
• Remove-CsTeamsShiftsConnectionTeamMap
• New-CsTeamsShiftsConnectionBatchTeamMap
• Get-CsTeamsShiftsConnectionConnector
• Get-CsTeamsShiftsConnectionOperation
• Get-CsTeamsShiftsConnectionSyncResult
• Get-CsTeamsShiftsConnectionErrorReport, Remove-CsTeamsShiftsConnectionErrorReport
• Get-CsTeamsShiftsConnectionWfmTeam
• Get-CsTeamsShiftsConnectionWfmUser
• Test-CsTeamsShiftsConnectionValidate

[Rollout Schedule:]

This change takes effect with the release of Microsoft Teams PowerShell Module 7.9.0. Organizations should review dependencies before upgrading to this version or any later version.

[Impact on Your Organization:]

Who is affected:

• Microsoft Teams administrators.
• Organizations using Teams Shifts connector scenarios managed through PowerShell automation.

Platforms/Services:

• Microsoft Teams
• Microsoft Teams PowerShell Module
• Teams Shifts connectors

What will happen:

• The Teams Shifts Connection cmdlets listed above are no longer supported in Microsoft Teams PowerShell Module 7.9.0 and later.
• Existing scripts, automation workflows, runbooks, and operational procedures that depend on these cmdlets may stop functioning as expected after an upgrade.
• Organizations that do not use these cmdlets are not impacted by this change.

[Action Required / Recommendations:]

• Review existing PowerShell scripts, automation workflows, runbooks, and operational procedures for dependencies on Teams Shifts Connection cmdlets.
• Remove or update affected dependencies before upgrading to Microsoft Teams PowerShell Module 7.9.0 or later.
• Validate administrative and operational processes that previously relied on these cmdlets.
• If your organization does not use these cmdlets, no action is required.