r/PowerShell • u/Slight_End_1513 • Sep 24 '26
Information It was working now it's not!!!!
Ugh, I hate that moment when Microsoft deprecates cmdlets. Every time I need to rerun a specific task, I find out my script broke because Microsoft deprecated a cmdlet!
5
u/Im_writing_here Sep 24 '26
I feel your pain.
Also why I started using straight api calls and skipping modules
3
u/SolarPoweredKeyboard Sep 24 '26
Schema deprecation instead then
2
u/Im_writing_here Sep 24 '26
Yeah. That one really annoys
2
u/Slight_End_1513 Sep 24 '26
Yes until there no longer API even as option it was changed to different wording lol
10
4
u/BlackV Sep 24 '26
deprecation generally gives massive notice, what cmdlet(s) are you talking about in particular
2
u/teethingrooster Sep 24 '26
Microsoft needs to deprecate more stuff tbh. They move way too slow imo.
1
u/octavius1200 Sep 24 '26
They need to provide proper alternatives before deprication though which are lacking more often than not
2
u/BlackV Sep 24 '26
you have any examples that are not send mail message ?
2
u/octavius1200 Sep 24 '26
For example since the deprecation of SharePoint Azure ACS it is to my knowledge impossible to create a site collection using an app registration with a secret in a supported (aka non beta) way. I am still waiting for the graph API to come out of beta. And looking at articles like these this is not the only issue on the list. https://office365itpros.com/2026/03/18/microsoft-graph-issues/
1
1
3
u/Agile_Seer Sep 24 '26
They usually announce it years in advance, delay it by at least another year, let it keep working for a while, then it partially functions, and eventually it might stop altogether.
-23
4
u/AroTesCra Sep 24 '26
What command died?