MicrosoftThank you merillms, I appreciate the clarification you provided, especially regarding not necessarily relying upon the API translation layer (that alone will be huge.) I am excited to see how this module shapes up and where it takes us.
I suppose you can answer my follow-up question and JamesC95's together - existing cmdlets that are currently implemented using the API translation layer, such as Get-EntraUser and Get-EntraUserMembership seem to be highly reflective of the API at the moment, obviously. Does the Entra module's current implementation allow for more user-friendly things such as what JamesC95 is saying in the short-term with just some quick over-the-top customization by the development team, or would these things be a longer-term goal for the development team in uncoupling these cmdlets from the API translation layer?
