Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 417/444 docs · checked 16:17 UTC Customize Public modeDiscuss ChangeIntel on Discord

Retiring Teams Shifts Connection cmdlets from Teams PowerShell Module

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

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.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 16:17 UTC · 258 of 260 readable · 256 fully read · documentation 417/444 current