MWPRO IMPACT SCORE
OPERATIONAL IMPACT
62
0
25
50
75
100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
Review the update and plan any required actions before rollout.
What is MWPro Impact Score?
Watch our 60‑second explainer
Primary Audience
Tenant AdminsMicrosoft 365 AdminsTeams AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Microsoft is retiring all Teams Shifts Connection cmdlets starting with Teams PowerShell Module 7.9.0, making automation scripts and runbooks dependent on these cmdlets fail after upgrade. Admins need to review and update affected scripts before installing the new version, which creates a configuration and testing workload. User impact is minimal since it is primarily an admin-side change, but workflows relying on automation may see indirect effects. Urgency is high due to immediate relevance when moving to the new module version.
78
Admin Impact
15
User Impact
70
Urgency
65
Effort
WHAT YOU NEED TO KNOW
AT A GLANCE
Teams PowerShell Module 7.9.0 drops support for Shifts Connection cmdlets. Check scripts and automation before upgrading.
END USERS
No major end-user change expected.
IT ADMINS
Review scripts and workflows for Shifts Connection cmdlets and update or remove before upgrading to 7.9.0 or later.
ROLLOUT TIMELINE
Start:
With 7.9.0 release
With 7.9.0 release
📢 Official Microsoft Message Center Announcement
Retiring Teams Shifts Connection cmdlets from Teams PowerShell Module
Message ID: MC1454390
[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-CsTeamsShiftsConnectionNew-CsTeamsShiftsConnectionInstance,Set-CsTeamsShiftsConnectionInstance,Remove-CsTeamsShiftsConnectionInstance,Update-CsTeamsShiftsConnectionInstanceRemove-CsTeamsShiftsConnectionTeamMapNew-CsTeamsShiftsConnectionBatchTeamMapGet-CsTeamsShiftsConnectionConnectorGet-CsTeamsShiftsConnectionOperationGet-CsTeamsShiftsConnectionSyncResultGet-CsTeamsShiftsConnectionErrorReport,Remove-CsTeamsShiftsConnectionErrorReportGet-CsTeamsShiftsConnectionWfmTeamGet-CsTeamsShiftsConnectionWfmUserTest-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.
Source: Microsoft Message Center • Analysed by MWPro
