MicrosoftMicrosoftBuilding on ChrisAtMaf 's comment above—how does your team plan to avoid history repeating itself with this endeavor quickly losing momentum and getting abandoned, where for example the Graph PowerShell SDK plateaus at ~90% of the functionality of the AzureAD module, and the AzureAD module with ~90% of the functionality of the MSOL module, leaving us in a position where we require all three modules long-term? The AzureAD module also had good intentions to replace the MSOL module, but that momentum died very quickly.
The AzureAD module has been neglected for quite some time, while all along still being considered the current and future module, with no comment on PowerShell 7 support, new releases but the release notes page now one year out of date despite multiple people flagging that issue and receiving acknowledgement, etc. Just being put on life support long before this post that acknowledges its end-of-life, and us being left with a poorly supported module for over a year with no ownership from Microsoft.
There also seems to be significant issues in how the Graph PowerShell SDK is structured, with some native API functionality being broken in the PowerShell SDK due to "translation layer" issues, and subsequent finger-pointing between teams for over six months. Example: https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/452. Curious how these underlying issues plan to be addressed—as this is exactly the kind of thing that would lead to that future where the Graph PowerShell SDK plateaus at ~90% and has to get put out of its misery a few years later.
