Microsoft Begins Retirement of Windows PowerShell Support for Graph SDK

Microsoft is confronting a growing maintenance burden as it continues to support the Microsoft Graph PowerShell SDK on the legacy Windows PowerShell 5.1 platform. The older runtime introduces dependency and assembly-loading challenges that complicate development and reduce reliability. Maintaining compatibility across both PowerShell generations also consumes engineering resources that could otherwise go toward new features and platform improvements.

Organizations still running Graph PowerShell automation on Windows PowerShell 5.1 risk falling behind as Microsoft’s focus transition elsewhere. Existing scripts are expected to continue functioning during the transition period, but customers remaining on the legacy platform will no longer benefit from platform-specific bug fixes. Administrators may also need to revisit automation environments, including scripts hosted in services such as Azure Automation, to ensure they remain supported in the future.

Graph PowerShell v3.0 will focus on PowerShell 7.x

Microsoft recommends a gradual transition to PowerShell 7.x, which it views as the long-term foundation for the Graph PowerShell ecosystem. The company has started a 12-month retirement period for Windows PowerShell 5.x support while keeping Graph PowerShell v2.x operational and eligible for security updates. Microsoft also plans to release Graph PowerShell v3.0 in Q4 2026, with support focused exclusively on PowerShell 7.x and later.

The tradeoff is that customers gain a more modern and potentially more reliable platform, but they must invest time in migration planning, script validation, and runtime upgrades. Microsoft expects the transition to be manageable for most organizations, yet environments that depend on older PowerShell runtimes, outdated .NET components, or long-established administrative workflows may face additional testing and remediation work before adopting the new SDK version.