Microsoft is shifting active Microsoft Graph PowerShell development toward PowerShell 7 and later. Existing scripts may continue to run on Windows PowerShell 5.1, but platform-specific problems will become harder to investigate and fix.
What is changing?
This is not an immediate compatibility shutdown. Microsoft may still issue security fixes for Microsoft.Graph v2.x when necessary, but it is ending active investigation of issues specific to Windows PowerShell 5.x. The planned Graph PowerShell v3.0.0 release in the fourth quarter of 2026 will not explicitly support Windows PowerShell 5.x.
Prepare your automation
- Inventory dependencies: Record the Microsoft.Graph version, imported modules, authentication approach, and execution location for each script.
- Prioritize important jobs: Start with automation that manages users, devices, or Microsoft 365 services, especially scheduled and managed jobs.
- Test on PowerShell 7: Use a non-production environment and compare authentication, Graph calls, output, and error handling with the existing run.
- Keep a rollback path: Preserve the current script and execution method until the new test results are accepted.
Why it matters
Continuing to depend on a platform outside the main maintenance path can increase troubleshooting effort and operational risk. Early testing gives teams time to identify compatibility issues before Graph PowerShell v3 becomes the target for new development.
Practical takeaway
Begin with an inventory, then migrate and validate the most important scripts in stages. Record test results so the production change can be scheduled with clear evidence.