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

New command: viva engage community user add #6293

Open
Jwaegebaert opened this issue Sep 2, 2024 · 0 comments · May be fixed by #6388
Open

New command: viva engage community user add #6293

Jwaegebaert opened this issue Sep 2, 2024 · 0 comments · May be fixed by #6388

Comments

@Jwaegebaert
Copy link
Contributor

Jwaegebaert commented Sep 2, 2024

Usage

m365 viva engage community user add [options]

Description

Adds a user to a specific Microsoft 365 Viva Engage community

Options

Option Description
-i, --communityId [communityId] The ID of the Viva Engage community. Specify communityId, communityDisplayName or entraGroupId.
-n, --communityDisplayName [communityDisplayName] The display name of the Viva Engage community. Specify communityId, communityDisplayName or entraGroupId.
--entraGroupId [entraGroupId] The ID of the Microsoft 365 group. Specify communityId, communityDisplayName or entraGroupId.
--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.
-r, --role <role> The role to be assigned to the new users. Valid values: Admin, Member.

Examples

Add a single user specified by ID as a member to a community specified by display name.

m365 viva engage community user add --communityDisplayName "All company" --ids 098b9f52-f48c-4401-819f-29c33794c3f5 --role Member

Add multiple users specified by ID as members to a community specified by ID.

m365 viva engage community user add --communityId eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiIzNjAyMDAxMTAwOSJ9 --ids "098b9f52-f48c-4401-819f-29c33794c3f5,f1e06e31-3abf-4746-83c2-1513d71f38b8" --role Member

Add a single user specified by UPN as an admin to a community specified by display name.

m365 viva engage community user add --communityDisplayName "All company" --userNames [email protected] --role Admin

Adds multiple users specified by UPN as admins to a community specified by its group ID.

m365 viva engage community user add --entraGroupId a03c0c35-ef9a-419b-8cab-f89e0a8d2d2a --userNames "[email protected],[email protected]" --role Admin

Additional Info

The role admin is essentially the same as owner, but the documentation refers to them as admin instead of owner for a community.

The endpoints you should look into for this scenario:

@Jwaegebaert Jwaegebaert added new feature needs peer review Needs second pair of eyes to review the spec or PR labels Sep 2, 2024
@waldekmastykarz waldekmastykarz added this to the v10 milestone Sep 18, 2024
@waldekmastykarz waldekmastykarz removed the needs peer review Needs second pair of eyes to review the spec or PR label Sep 18, 2024
@MathijsVerbeeck MathijsVerbeeck self-assigned this Sep 20, 2024
MathijsVerbeeck added a commit to MathijsVerbeeck/cli-microsoft365 that referenced this issue Sep 26, 2024
@MathijsVerbeeck MathijsVerbeeck linked a pull request Sep 26, 2024 that will close this issue
@MathijsVerbeeck MathijsVerbeeck linked a pull request Sep 26, 2024 that will close this issue
MathijsVerbeeck added a commit to MathijsVerbeeck/cli-microsoft365 that referenced this issue Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants