MicrosoftChrisAtMaf I understand your frustrations and appreciate the feedback; to shed some light ;
As part of the parity work, we are looking at both the https://docs.microsoft.com/en-us/powershell/module/msonline/?view=azureadps-1.0 (MSOnline) and Azure AD libraries of Azure AD cmdlets and mapping the functionality onto the MS Graph PowerShell SDK, to make sure that all scenarios are available. We have started working on a https://docs.microsoft.com/en-au/powershell/microsoftgraph/azuread-msoline-cmdlet-map?view=graph-powershell-beta for MSOL vs Microsoft Graph PowerShell, and Azure AD Graph PowerShell vs Microsoft Graph PowerShell, as part of the migration documentation. Users have contacted us requesting specific scenarios/cmdlets that we will add to Microsoft Graph PowerShell. We will continue to deliver tools like https://docs.microsoft.com/en-us/powershell/microsoftgraph/find-mg-graph-command?view=graph-powershell-1.0 and https://docs.microsoft.com/en-us/powershell/microsoftgraph/find-mg-graph-permission?view=graph-powershell-1.0, that will assist users in locating and using the appropriate Microsoft Graph cmdlet.
Microsoft Graph cmdlets are autogenerated from the Microsoft Graph API schema. The process has many advantages, for example, providing a rich set of cmdlets that cover the whole API landscape. The disadvantage is that the resultant cmdlets may not be as user friendly, when compared to human authored cmdlets. Consequently, we are actively working on usability improvements of MS PS SDK cmdlets docs and examples and more tools on migration.
