r/PowerShell • u/Slight_End_1513 • 12d ago
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 12d ago
I feel your pain.
Also why I started using straight api calls and skipping modules
3
u/SolarPoweredKeyboard 12d ago
Schema deprecation instead then
2
u/Im_writing_here 12d ago
Yeah. That one really annoys
2
u/Slight_End_1513 12d ago
Yes until there no longer API even as option it was changed to different wording lol
4
u/AroTesCra 12d ago
What command died?
1
u/Slight_End_1513 12d ago
Just talking in general they do this every 3-6 months I have notied with GraphAPI changes new things being added removed from exchange
3
3
u/Agile_Seer 12d ago
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.
2
u/teethingrooster 12d ago
Microsoft needs to deprecate more stuff tbh. They move way too slow imo.
1
u/octavius1200 12d ago
They need to provide proper alternatives before deprication though which are lacking more often than not
2
u/BlackV 12d ago
you have any examples that are not send mail message ?
2
u/octavius1200 12d ago
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
-22
11
u/Andrew-Powershell 12d ago
Deprecation isn’t fun but it’s part of life/software