Good work in putting it together in a straight forward article.
I would like to call something out though.
"On this note, there is no functional difference between a RPS cmdlet and its REST-backed equivalent." - Not quite, we lose the fairly useful automatic formatting data (ft). As an administrator and years of practice, its a significant difference. More on general PS behavior when compared to basic PS cmdlets.
Any plans to move towards Mg cmdlets, AzureAD has already made the move. Changing the endpoint to graph.microsoft.com should bring in higher throttling benefits, which is 20 on max concurrent sessions.
The new module is missing below ones for me.
Windows | PowerShell |
Function | ConvertFrom-ExoJobData.ps1 |
Function | New-ApplicationAccessPolicy |
#2.0.5
gcm new-app*
CommandType Name Version Source
----------- ---- ------- ------
Function New-App 1.0 tmp_zjv1yi2a.zm1
Function New-ApplicationAccessPolicy 1.0 tmp_zjv1yi2a.zm1
Cmdlet New-AppLockerPolicy 2.0.0.0 AppLocker
#2.0.6
gcm new-app*
CommandType Name Version Source
----------- ---- ------- ------
Function New-App 1.0 tmpEXO_h234vekq.caz
Cmdlet New-AppLockerPolicy 2.0.0.0 AppLocker
Normal cmdlet count for non REST (-UseRPSSession) : Count : 795
New Preview6 : Count : 793