Microsoft is phasing out one of the most widely used automation toolkits for IT professionals, and the deadline is looming for anyone still running the legacy Windows shell.
According to reporting by Neowin, Microsoft is retiring the Graph PowerShell modules on Windows PowerShell 5.x — the Windows-only shell that has shipped with the operating system for more than a decade. The move affects the tooling that lets administrators and developers manage cloud services such as Microsoft 365, Entra ID (formerly Azure Active Directory), and other Graph-backed products straight from a PowerShell prompt.
What’s changing with the Graph PowerShell modules
The Microsoft Graph PowerShell modules are the official bridge between PowerShell and Microsoft Graph, the underlying API that powers most of Microsoft’s cloud services. Rather than manually constructing REST calls and managing authentication tokens yourself, you install the module, sign in once, and gain a full library of cmdlets that map directly to Graph operations.
Microsoft is now signaling that these modules will no longer be actively supported on Windows PowerShell 5.x. That doesn’t necessarily mean they vanish overnight — the more typical retirement pattern is that the modules stop receiving updates, bug fixes, and new-cmdlet releases on that platform. But if you’re relying on the latest features or security patches, Windows PowerShell 5.x is no longer the home for this tooling.
The modules have come in a few different flavors over the years: the original modular Microsoft.Graph family, the preview Microsoft.Graph.Beta branch, and Microsoft’s newer unified Graph PowerShell SDK. All of them have been installable on both Windows PowerShell 5.x and PowerShell 7, but the retirement being announced targets the Windows PowerShell 5.x side specifically.
Why Microsoft is pushing this change
The bigger picture is Microsoft’s long-running push to move everyone off Windows PowerShell 5.x and onto PowerShell 7 (shipped as pwsh). Windows PowerShell 5.x has been in maintenance mode for years — Microsoft adds bug fixes at most, with no new features, and the platform is locked to Windows. PowerShell 7, by contrast, is open-source, cross-platform, and actively developed, with performance improvements and modern language features.
Because Microsoft Graph is a cloud service, there is little technical reason to keep its automation modules pinned to a Windows-only, feature-frozen shell. Running them on PowerShell 7 gives you a single, future-proof environment that works the same way whether you’re on Windows, macOS, or Linux — which matters a great deal for teams running automation across mixed fleets.
What this means for you
If you run any Graph-based automation on Windows PowerShell 5.x — scheduled tasks, CI/CD pipelines, or manual day-to-day management scripts — your modules will eventually stop getting updates. In practice, that means newer cmdlets, compatibility fixes, and security-related changes may not reach your environment until you migrate.
This is especially relevant for anyone using Graph automation inside managed environments like Azure Automation runbook workers, Intune automation, or third-party RMM tools that still default to Windows PowerShell 5.x. Those platforms increasingly offer PowerShell 7 worker options, so it’s worth checking whether your automation host supports the newer runtime before the cutoff bites.
How to prepare for the transition
The migration path is straightforward. First, install PowerShell 7 (pwsh) alongside your existing Windows PowerShell 5.x — the two can coexist, and you won’t lose anything by adding it. PowerShell 7 installs to its own path and doesn’t overwrite the legacy shell.
Next, test your existing scripts under PowerShell 7 before you cut over. Most Graph scripts work as-is, but it’s wise to verify authentication flows and any version-specific syntax. Once everything checks out, point your scheduled tasks, runbooks, and automation accounts toward the PowerShell 7 executable.
Microsoft’s broader direction is clear: PowerShell 7 is the present and future, and legacy shells are being steadily sunset across its toolchain. Migrating now keeps your Graph PowerShell modules current and avoids a rushed move later when support fully drops.
Source: Neowin
Over to you: Are you still running Graph automation on Windows PowerShell 5.x, or have you already moved to PowerShell 7?
