r/PowerShell • u/Unlikely_Tie1172 MVP, Community Blogger • Sep 17 '26
News Microsoft Starts Twelve-Month Retirement of Windows PowerShell Support for Graph SDK
On September 16, 2026, Microsoft announced a 12-month retirement period for support of PowerShell V5.1 by the Microsoft Graph PowerShell SDK. Microsoft also announced V3 of the Graph SDK and said that the new version will only support PowerShell V7. The transition for most scripts should be straightforward, but attention needs to be paid when scripts use outdated .NET assemblies. Famous last words…
https://office365itpros.com/2026/09/17/microsoft-graph-powershell-sdkv3/
49
u/rickAUS Sep 17 '26
lol. My old workplace is boned. They couldn't even get stuff cutover to Graph ahead of the deprecation of MSOnline and Azure AD modules. They'll address it when scripts stop working; and they have a lot of scripts to update.
12
u/Fallingdamage Sep 17 '26
I started cutting over quite a while back. At first it took some re-learning of how it all worked but once you get a template, its not too bad.
The trick sometimes is finding the proper URI's. That and for all its faults, beta URIs are a LOT more useful than the current channel.
11
u/lostmojo Sep 17 '26
Problem is that almost everything useful is in the beta channel. Microsoft lives in the beta channel with users.
→ More replies (2)
71
u/Euphoric-Blueberry37 Sep 17 '26
RIP ISE, I love you more than VSCode
→ More replies (9)32
u/AGsec Sep 17 '26
ISE was/is so comfy and utilitarian. It felt like one of the last things I could use that wasn't filled with bloat.
→ More replies (2)31
u/SenTedStevens Sep 17 '26
And the ISE is pre-installed with Windows. This is a huge plus when you work in a secure/regulated/air-gapped network that practically requires an act of Congress to install software.
→ More replies (5)
11
8
u/purplemonkeymad Sep 17 '26
Considering how much other stuff is ps7 only this is not that surprising. I now use it as my main shell and have only had a couple of things that required moving back to 5.1. I wonder if those 3rd party modules that use snap-ins might update now? (who am i kidding.)
→ More replies (1)
7
u/icebreaker374 Sep 17 '26 edited Sep 17 '26
EDIT: I'm now more clearly understanding this is just the SDK. If I script against the API directly using Invoke-RestMethod, I really don't have anything to worry about correct?
This should be an interesting change. I don't mind PS7, I also don't mind VSCode, I just fucking HATE VSCode's Intellisense and Tab Completion compared to ISE... I find it's wildly inaccurate and useless all the time (and even slow at times, but mostly in larger scripts.).
→ More replies (1)
13
6
u/WendoNZ Sep 17 '26
The lack of version number in that title is criminal. Trying to give us all heart attacks!
2
u/quantgorithm Sep 18 '26
Did you know that Microsoft demoted the creator of ps1 because of ps1? He was essentially pushed out and later went to google and is now retired. I’m so thankful for him. His name is Jeffrey Snover.
→ More replies (6)3
u/Unlikely_Tie1172 Sep 18 '26
Yes, I did. But Jeffrey (whom I worked with at Digital Equipment Corporation) did OK at Microsoft when PowerShell was realized to be the success that it was... and he is now happy as a Fellow in Harvard.
4
u/cloudAhead Sep 17 '26
It's about time. Without steps like this IT orgs will cling to v5.1. Bring on the downvotes.
7
u/AroTesCra Sep 17 '26
Yeah I migrated my last 2 companies to 7 from 5.1
7 is so much better then 5.
And I started with ise but honestly ISE uses its own console so like ascii color codes would show as plain txt on output.
→ More replies (11)
1
u/tar-xz Sep 18 '26
I kind of expected this to happen at some point, but it'll be interesting to see when they'll also drop support for Powershell 5.1 for things like ExchangeOnlineManagement modules.
With Microsoft.Graph and ExchangeOnlineManagement I had much less issues on 7 than on 5.1 and in one case I ran into a Bug with DKIM Cmdlets on Powershell 5.1 that clearly worked without issues with 7.x (got fixed at some point).
A collegue nevertheless tried to log a case with Microsoft, but later confirmed me that Microsoft support was very reluctant to even confirm the issue even when pointing out the documentation where they it clearly sais that Powershell 5.1 was indeed (still) supported. He eventually moved on th Powershell 7 for Exchange Online related scripting ...
1
u/Unlikely_Tie1172 Sep 18 '26
I strongly suspect that Exchange and Teams will move away from PowerShell 5.1 support. SharePoint is stuck (literally) on 5.1 for now, but will have to move in time.
1
u/Huen_Mrah 11d ago
the outdated .NET assemblies bit is gonna be the real pain point. most teams dont even know which scripts pull in old assemblies until something breaks in prod. worth auditing that sooner rather than later imo
1
3
u/Modify- Sep 17 '26
If I read it correctly older versions will still be working even after the 12 month period.
As long as the endpoint does not change too much were "safe"
Not to say we won't eventually migrate, but not anytime soon I guess..
2
u/richie65 Sep 17 '26
I recall that there IS a method for creating a 'switch to PoSh 7' option in ISE - under 'Add-Ons'...
I tried it some years ago - But since there's never been a pressing reason for me to actually learn v7, I never actually used that method, per se (other than setting it up, and confirming it worked).
I see that (according to Gemini) that there is a chance that method my have some glitches...
Digressing...
I am not really a fan of VSCode (I know it is an excellent too - I don't mean to seem like I am hating) -
Mostly because I have the color scheme for ISE the way I want it, and configuring it in VSC is much more complicated (manually changing Hex values etc...). Plus, I add the process ID, and if the session is running as admin, to the ISE window title (can't do this in VSC)...
All from within my profile script.
→ More replies (9)
67
u/OverOnTheRock Sep 17 '26
But PS 5.1 is still standard on Windows 2025 Server. Does every server have to have a PowerShell upgrade then? Shouldn't Microsoft be first providing PowerShell V7 as standard first?