Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance entra m365group user set by specifying multiple users #6059

Open
1 task
Tracked by #5432
milanholemans opened this issue May 18, 2024 · 1 comment
Open
1 task
Tracked by #5432

Enhance entra m365group user set by specifying multiple users #6059

milanholemans opened this issue May 18, 2024 · 1 comment

Comments

@milanholemans
Copy link
Contributor

Currently, the command entra m365group user set only supports specifying one user by UPN. Let's enhance this command so it can accept multiple users by UPN or ID.
In addition, let's also add the possibility to reference the group by display name.

Options to add

Option Description
--groupName [groupName] The display name of the Microsoft 365 group. Specify only one of the following: groupId, groupName, teamId, or teamName.
--teamName [teamName] The display name of the Microsoft Teams team. Specify only one of the following: groupId, groupName, teamId, or teamName.
--ids [ids] Microsoft Entra IDs of users. You can also pass a comma-separated list of IDs. Specify either ids or userNames but not both.
--userNames [userNames] The user principal names of users. You can also pass a comma-separated list of UPNs. Specify either ids or userNames but not both.

Deprecate current option

This will come at a cost, we'll have to deprecate the currently required option -n, --userName <userName>.
Let's make the option optional and deprecate it.

  • Create v8 issue to remove the deprecated option.
@milanholemans milanholemans added enhancement needs peer review Needs second pair of eyes to review the spec or PR labels May 18, 2024
@Jwaegebaert Jwaegebaert added help wanted and removed needs peer review Needs second pair of eyes to review the spec or PR labels May 22, 2024
@Saurabh7019
Copy link
Contributor

@milanholemans, Can you assign this one to me as well? It's quite similar to #6060

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants