Retiring Teams Shifts Connection cmdlets from Teams PowerShell Module

🚨 The Signal: Microsoft is deprecating PowerShell cmdlets for Teams Shifts connections in Teams PowerShell Module 7.9.0+. This removes programmatic management of Shifts integrations, requiring administrators to find alternative methods for automation.

The Impact

Teams administrators using PowerShell for Shifts integrations are affected, with a low security risk as this is a management method change, not a security vulnerability.

• Teams administrators: Loss of automated Shifts connection management.
• Organisations: Potential disruption to existing Shifts integration workflows.
• Security teams: No direct security risk, but review of automation practices may be needed.

The Action

1. Identify all existing PowerShell scripts using `*CsTeamsShiftsConnection*` cmdlets.
2. Review Microsoft documentation for alternative methods to manage Teams Shifts connections.
3. Plan for manual configuration or re-development of automation using supported APIs/methods.
4. Before upgrading, test the impact of Teams PowerShell Module 7.9.0+ on existing Shifts automation.

Domain: Teams · Impact: low · Workload: Teams