-Members should accept ids

[danielniccoli]

Is your feature request related to a problem? Please describe the problem.

New-MgGroup … -Members 70b5931c-98e4-4077-8e96-81b7a5b057ff,189d20f0-ab4e-4378-a728-3ea0b6f7b1a0

Returns

Error: "Cannot convert the "d7df1f72-6d53-4667-ba05-90a979412bb8" value of type "System.String" to type "Microsoft.Graph.PowerShell.Models.IMicrosoftGraphDirectoryObject"

Describe the solution you'd like.

I'd like the SDK to handle ids natively.

Additional context?

No response

[timayabi2020]

@danielniccoli thank you for raising this issue. Based on the error, the type -Members parameter expects is of Microsoft.Graph.PowerShell.Models.IMicrosoftGraphDirectoryObject. Please refer to the documentation here on how to use that particular parameter.

[danielniccoli]

I know it expects Microsoft.Graph.PowerShell.Models.IMicrosoftGraphDirectoryObject and that is exactly why I created this feature request. Using a complex object type, when IDs suffice is completely unnecessary. The SDK should make your life easier, not harder! And frankly, using plain HTTPS requests is much simpler at this point.

And the "documentation" you linked is not helpful.

Supports the List members, Add member, and Remove member operations. Nullable. Supports $expand including nested $select. For example, /groups$filter=startsWith(displayName,'Role')&$select=id,displayName&$expand=members($select=id,userPrincipalName,displayName).

What does that even mean?

To construct, see NOTES section for MEMBERS properties and create a hash table.

There is no section "MEMBERS" in the notes.