@pnp/cli-microsoft365 7.0.0-beta.c2db9df → 7.0.0-beta.e15bb2d

package/docs/docs/cmd/aad/group/group-remove.mdx

@@ -0,0 +1,44 @@
+import Global from '/docs/cmd/_global.mdx';
+
+# aad group remove
+
+Removes an Azure AD group
+
+## Usage
+
+```sh
+m365 aad group remove [options]
+```
+
+## Options
+
+```md definition-list
+`-i, --id [id]`
+: The ID of the Azure AD group. Specify either `id` or `displayName` but not both.
+
+`-n, --displayName [displayName]`
+: The display name of the Azure AD group. Specify either `id` or `displayName` but not both.
+
+`-f, --force`
+: Don't prompt for confirmation.
+```
+
+<Global />
+
+## Examples
+
+Remove an Azure AD group by display name
+
+```sh
+m365 aad group remove --displayName Developers
+```
+
+Remove an Azure AD group by ID
+
+```sh
+m365 aad group remove --id 016bf125-195b-43c5-a1a0-28ccd3192c6d
+```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/aad/m365group/m365group-add.mdx

@@ -30,8 +30,8 @@ m365 aad m365group add [options]
 `--members [members]`
 : Comma-separated list of Microsoft 365 Group members
 
-`--isPrivate`
-: Specify, if the Microsoft 365 Group should be private. If not specified, will create a public group (default)
+`--visibility [visibility]`
+: Specifies the group join policy and group content visibility for groups. Possible values are: `Private`, `Public`, or `HiddenMembership`. Defaults to `Public`.
 
 `--allowMembersToPost [allowMembersToPost]`
 : Set if only group members should be able to post conversations to the group
@@ -53,9 +53,19 @@ m365 aad m365group add [options]
 
 ## Remarks
 
+You cannot change the group type when you choose `HiddenMembership` visibility. HiddenMembership can be set only for Microsoft 365 groups, when the groups are created. It can't be updated later.
+
 When specifying the path to the logo image you can use both relative and absolute paths. Note, that ~ in the path, will not be resolved and will most likely result in an error.
 If an invalid user is provided in the comma-separated list of Owners or Members, the command operation will fail and the Microsoft 365 Group will not be created.
 
+Group visibility options:
+
+Value	| Description
+-------|-------------
+Public | Anyone can join the group without needing owner permission. Anyone can view the attributes of the group. Anyone can see the members of the group.
+Private | Owner permission is needed to join the group. Anyone can view the attributes of the group. Anyone can see the members of the group.
+HiddenMembership | Owner permission is needed to join the group. Guest users cannot view the attributes of the group. Non-members cannot see the members of the group. Administrators (global, company, user, and helpdesk) can view the membership of the group. The group appears in the global address book (GAL).
+
 ## Examples
 
 Create a public Microsoft 365 Group
@@ -67,7 +77,7 @@ m365 aad m365group add --displayName Finance --description "This is the Contoso
 Create a private Microsoft 365 Group
 
 ```sh
-m365 aad m365group add --displayName Finance --description "This is the Contoso Finance Group. Please come here and check out the latest news, posts, files, and more." --mailNickname finance --isPrivate
+m365 aad m365group add --displayName Finance --description "This is the Contoso Finance Group. Please come here and check out the latest news, posts, files, and more." --mailNickname finance --visibility Private
 ```
 
 Create a public Microsoft 365 Group and set specified users as its owners

package/docs/docs/cmd/graph/subscription/subscription-add.mdx

@@ -16,19 +16,19 @@ m365 graph subscription add [options]
 
 ```md definition-list
 `-r, --resource <resource>`
-: The resource that will be monitored for changes
+: The resource that will be monitored for changes.
 
-`-c, --changeType <changeType>`
-: The type of change in the subscribed resource that will raise a notification. The supported values are: `created`, `updated`, `deleted`. Multiple values can be combined using a comma-separated list
+`-c, --changeTypes <changeTypes>`
+: The type of change in the subscribed resource that will raise a notification. The supported values are: `created`, `updated`, `deleted`. Multiple values can be combined using a comma-separated list.
 
 `-u, --notificationUrl <notificationUrl>`
-: The URL of the endpoint that will receive the notifications. This URL must use the HTTPS protocol
+: The URL of the endpoint that will receive the notifications. This URL must use the HTTPS protocol.
 
 `-e, --expirationDateTime [expirationDateTime]`
-: The date and time when the webhook subscription expires. The time is in UTC, and can be an amount of time from subscription creation that varies for the resource subscribed to. If not specified, the maximum allowed expiration for the specified resource will be used
+: The date and time when the webhook subscription expires. The time is in UTC, and can be an amount of time from subscription creation that varies for the resource subscribed to. If not specified, the maximum allowed expiration for the specified resource will be used.
 
 `-s, --clientState [clientState]`
-: The value of the clientState property sent by the service in each notification. The maximum length is 128 characters
+: The value of the clientState property sent by the service in each notification. The maximum length is 128 characters.
 ```
 
 <Global />
@@ -52,19 +52,19 @@ To subscribe to change notifications of Outlook contacts, events, or messages in
 Create a subscription
 
 ```sh
-m365 graph subscription add --resource "me/mailFolders('Inbox')/messages" --changeType "updated" --notificationUrl "https://webhook.azurewebsites.net/api/send/myNotifyClient" --expirationDateTime "2016-11-20T18:23:45.935Z" --clientState "secretClientState"
+m365 graph subscription add --resource "me/mailFolders('Inbox')/messages" --changeTypes "updated" --notificationUrl "https://webhook.azurewebsites.net/api/send/myNotifyClient" --expirationDateTime "2016-11-20T18:23:45.935Z" --clientState "secretClientState"
 ```
 
 Create a subscription on multiple change types
 
 ```sh
-m365 graph subscription add --resource groups --changeType updated,deleted --notificationUrl "https://webhook.azurewebsites.net/api/send/myNotifyClient" --expirationDateTime "2016-11-20T18:23:45.935Z" --clientState "secretClientState"
+m365 graph subscription add --resource groups --changeTypes "updated,deleted" --notificationUrl "https://webhook.azurewebsites.net/api/send/myNotifyClient" --expirationDateTime "2016-11-20T18:23:45.935Z" --clientState "secretClientState"
 ```
 
 Create a subscription using the maximum allowed expiration for Group resources
 
 ```sh
-m365 graph subscription add --resource groups --changeType "updated" --notificationUrl "https://webhook.azurewebsites.net/api/send/myNotifyClient"
+m365 graph subscription add --resource groups --changeTypes "updated" --notificationUrl "https://webhook.azurewebsites.net/api/send/myNotifyClient"
 ```
 
 ## Response
@@ -125,7 +125,7 @@ m365 graph subscription add --resource groups --changeType "updated" --notificat
   <TabItem value="Markdown">
 
   ```md
-  # graph subscription add --resource "groups" --changeType "updated" --notificationUrl "https://webhook.azurewebsites.net/api/changeNotificationHook" --expirationDateTime "2023-05-23T18:23:45.935Z" --clientState "some secret value"
+  # graph subscription add --resource "groups" --changeTypes "updated" --notificationUrl "https://webhook.azurewebsites.net/api/changeNotificationHook" --expirationDateTime "2023-05-23T18:23:45.935Z" --clientState "some secret value"
 
   Date: 2023-05-22
 

package/docs/docs/cmd/spfx/project/project-upgrade.mdx

@@ -35,7 +35,7 @@ m365 spfx project upgrade [options]
 
 ## Remarks
 
-The `spfx project upgrade` command helps you upgrade your SharePoint Framework project to the specified version. If no version is specified, the command will upgrade to the latest version of the SharePoint Framework it supports (v1.17.4).
+The `spfx project upgrade` command helps you upgrade your SharePoint Framework project to the specified version. If no version is specified, the command will upgrade to the latest version of the SharePoint Framework it supports (v1.18.0).
 
 This command doesn't change your project files. Instead, it gives you a report with all steps necessary to upgrade your project to the specified version of the SharePoint Framework. Changing project files is error-prone, especially when it comes to updating your solution's code. This is why at this moment, this command produces a report that you can use yourself to perform the necessary updates and verify that everything is working as expected.
 

package/docs/docs/cmd/spo/file/file-get.mdx

@@ -15,10 +15,10 @@ m365 spo file get [options]
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : The URL of the site where the file is located
 
-`-u, --url [url]`
+`--url [url]`
 : The server- or site-relative decoded URL of the file to retrieve. Specify either `url` or `id` but not both
 
 `-i, --id [id]`

package/docs/docs/cmd/spo/file/file-remove.mdx

@@ -19,13 +19,13 @@ m365 spo page template remove
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : URL of the site where the file to remove is located
 
 `-i, --id [id]`
 : The ID of the file to remove. Specify either `id` or `url` but not both
 
-`-u, --url [url]`
+`--url [url]`
 : The server- or site-relative decoded URL of the file to remove. Specify either `id` or `url` but not both
 
 `--recycle`

package/docs/docs/cmd/spo/file/file-version-clear.mdx

@@ -13,10 +13,10 @@ m365 spo file version clear [options]
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : The URL of the site where the file is located
 
-`-u, --fileUrl [fileUrl]`
+`--fileUrl [fileUrl]`
 : The server- or site-relative decoded URL of the file. Specify either `fileUrl` or `fileId` but not both
 
 `-i, --fileId [fileId]`

package/docs/docs/cmd/spo/file/file-version-get.mdx

@@ -15,13 +15,13 @@ m365 spo file version get [options]
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : The URL of the site where the file is located
 
 `--label <label>`
 : Label of version which will be retrieved
 
-`-u, --fileUrl [fileUrl]`
+`--fileUrl [fileUrl]`
 : The server- or site-relative decoded URL of the file to retrieve. Specify either `fileUrl` or `fileId` but not both
 
 `-i, --fileId [fileId]`

package/docs/docs/cmd/spo/file/file-version-list.mdx

@@ -15,10 +15,10 @@ m365 spo file version list [options]
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : The URL of the site where the file is located
 
-`-u, --fileUrl [fileUrl]`
+`--fileUrl [fileUrl]`
 : The server- or site-relative decoded URL of the file. Specify either `fileUrl` or `fileId` but not both
 
 `-i, --fileId [fileId]`

package/docs/docs/cmd/spo/file/file-version-remove.mdx

@@ -13,13 +13,13 @@ m365 spo file version remove [options]
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : The URL of the site where the file is located
 
 `--label <label>`
 : Label of version which will be removed
 
-`-u, --fileUrl [fileUrl]`
+`--fileUrl [fileUrl]`
 : The server- or site-relative decoded URL of the file to retrieve. Specify either `fileUrl` or `fileId` but not both
 
 `-i, --fileId [fileId]`

package/docs/docs/cmd/spo/file/file-version-restore.mdx

@@ -13,13 +13,13 @@ m365 spo file version restore [options]
 ## Options
 
 ```md definition-list
-`-w, --webUrl <webUrl>`
+`-u, --webUrl <webUrl>`
 : The URL of the site where the file is located
 
 `--label <label>`
 : Label of version which will be restored
 
-`-u, --fileUrl [fileUrl]`
+`--fileUrl [fileUrl]`
 : The server- or site-relative decoded URL of the file whose version will be restored. Specify either `fileUrl` or `fileId` but not both
 
 `-i, --fileId [fileId]`

package/docs/docs/cmd/spo/group/group-member-add.mdx

@@ -16,72 +16,72 @@ m365 spo group member add [options]
 
 ```md definition-list
 `-u, --webUrl <webUrl>`
-: URL of the site where the SharePoint group is available
+: URL of the site where the SharePoint group is available.
 
 `--groupId [groupId]`
-: Id of the SharePoint Group to which the user needs to be added, specify either `groupId` or `groupName`
+: Id of the SharePoint Group to which the user needs to be added, specify either `groupId` or `groupName`.
 
 `--groupName [groupName]`
-: Name of the SharePoint Group to which the user needs to be added, specify either `groupId` or `groupName`
+: Name of the SharePoint Group to which the user needs to be added, specify either `groupId` or `groupName`.
 
-`--userName [userName]`
-: User's UPN (user principal name, eg. megan.bowen@contoso.com). If multiple users need to be added, they have to be comma-separated (e.g. megan.bowen@contoso.com,alex.wilber@contoso.com). Specify either `userId`, `userName`, `email`, `aadGroupId` or `aadGroupName`
+`--userNames [userNames]`
+: User's UPN (user principal name, eg. megan.bowen@contoso.com). If multiple users need to be added, they have to be comma-separated (e.g. megan.bowen@contoso.com,alex.wilber@contoso.com). Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
 
-`--email [email]`
-: User's email (eg. megan.bowen@contoso.com). If multiple users need to be added, they have to be comma-separated (e.g. megan.bowen@contoso.com,alex.wilber@contoso.com). Specify either `userId`, `userName`, `email`, `aadGroupId` or `aadGroupName`
+`--emails [emails]`
+: User's email (eg. megan.bowen@contoso.com). If multiple users need to be added, they have to be comma-separated (e.g. megan.bowen@contoso.com,alex.wilber@contoso.com). Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
 
-`--userId [userId]`
-: The user Id of the user to add as a member. (Id of the site user, for example: 14) If multiple users need to be added, the Ids have to be comma-separated. Specify either `userId`, `userName`, `email`, `aadGroupId` or `aadGroupName`
+`--userIds [userIds]`
+: The user Id of the user to add as a member. (Id of the site user, for example: 14) If multiple users need to be added, the Ids have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
 
-`--aadGroupId [aadGroupId]`
-: The object Id of the Azure AD group to add as a member. If multiple groups need to be added, the Ids have to be comma-separated. Specify either `userId`, `userName`, `email`, `aadGroupId` or `aadGroupName`
+`--aadGroupIds [aadGroupIds]`
+: The object Id of the Azure AD group to add as a member. If multiple groups need to be added, the Ids have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
 
-`--aadGroupName [aadGroupName]`
-: The name of the Azure AD group to add as a member. Specify either `userId`, `userName`, `email`, `aadGroupId` or `aadGroupName`
+`--aadGroupNames [aadGroupNames]`
+: The name of the Azure AD group to add as a member. If multiple groups need to be added, they have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
 ```
 
 <Global />
 
 ## Remarks
 
-For the `userId`, `userName`, `email`, `aadGroupId` or `aadGroupName` options you can specify multiple values by separating them with a comma. If one of the specified entries is not valid, the command will fail with an error message showing the list of invalid values.
+For the `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames` options you can specify multiple values by separating them with a comma. If one of the specified entries is not valid, the command will fail with an error message showing the list of invalid values.
 
 ## Examples
 
-Add a user with the userName parameter to a SharePoint group with the groupId parameter
+Add a user with the userNames parameter to a SharePoint group with the groupId parameter
 
 ```sh
-m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userName "Alex.Wilber@contoso.com"
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userNames "Alex.Wilber@contoso.com"
 ```
 
-Add multiple users with the userName parameter to a SharePoint group with the groupId parameter
+Add multiple users with the userNames parameter to a SharePoint group with the groupId parameter
 
 ```sh
-m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userName "Alex.Wilber@contoso.com, Adele.Vance@contoso.com"
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userNames "Alex.Wilber@contoso.com, Adele.Vance@contoso.com"
 ```
 
-Add a user with the email parameter to a SharePoint group with the groupName parameter
+Add a user with the emails parameter to a SharePoint group with the groupName parameter
 
 ```sh
-m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Contoso Site Owners" --email "Alex.Wilber@contoso.com"
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Contoso Site Owners" --emails "Alex.Wilber@contoso.com"
 ```
 
-Add multiple users with the email parameter to a SharePoint group with the groupName parameter
+Add multiple users with the emails parameter to a SharePoint group with the groupName parameter
 
 ```sh
-m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Contoso Site Owners" --email "Alex.Wilber@contoso.com, Adele.Vance@contoso.com"
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Contoso Site Owners" --emails "Alex.Wilber@contoso.com, Adele.Vance@contoso.com"
 ```
 
-Add a user with the userId parameter to a SharePoint group with the groupId parameter
+Add a user with the userIds parameter to a SharePoint group with the groupId parameter
 
 ```sh
-m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userId 5
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userIds 5
 ```
 
-Add multiple users with the userId parameter to a SharePoint group with the groupId parameter
+Add multiple users with the userIds parameter to a SharePoint group with the groupId parameter
 
 ```sh
-m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userId "5,12"
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userIds "5,12"
 ```
 
 Add multiple users with the aadUserId parameter to a SharePoint group with the groupId parameter
@@ -140,7 +140,7 @@ m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --
   <TabItem value="Markdown">
 
   ```md
-  # spo group member add --webUrl "https://contoso.sharepoint.com" --groupId "5" --aadGroupId "f2fb2f10-cfd2-4054-8ffd-64533657a5ab"
+  # spo group member add --webUrl "https://contoso.sharepoint.com" --groupId "5" --aadGroupIds "f2fb2f10-cfd2-4054-8ffd-64533657a5ab"
 
   Date: 13/2/2023
 

package/docs/docs/cmd/spo/list/list-contenttype-remove.mdx

@@ -51,7 +51,7 @@ m365 spo list contenttype remove --webUrl https://contoso.sharepoint.com/sites/p
 Remove content type with a specific id from the list retrieved by server relative URL in a specific site. This will not prompt for confirmation.
 
 ```sh
-m365 spo list contenttype remove --webUrl https://contoso.sharepoint.com/sites/project-x --listUrl 'sites/project-x/Documents' --contentTypeId 0x010109010053EE7AEB1FC54A41B4D9F66ADBDC312A --force
+m365 spo list contenttype remove --webUrl https://contoso.sharepoint.com/sites/project-x --listUrl 'sites/project-x/Documents' --id 0x010109010053EE7AEB1FC54A41B4D9F66ADBDC312A --force
 ```
 
 ## Response

package/docs/docs/cmd/spo/page/page-set.mdx

@@ -42,6 +42,9 @@ m365 spo page set [options]
 
 `--title [title]`
 : The title to set for the page.
+
+`--content [content]`
+: JSON string containing page content
 ```
 
 <Global />
@@ -52,6 +55,20 @@ If you try to create a page with a name of a page that already exists, you will
 
 If you choose to promote the page using the `promoteAs` option or enable page comments, you will see the result only after publishing the page.
 
+Running this command from the Windows Command Shell (cmd.exe) or PowerShell for Windows OS XP, 7, 8, 8.1 without bash installed might require additional formatting for command options that have JSON, XML or JavaScript values because the command shell treat quotes differently. For example, this is how you can add page content from the Windows cmd.exe:
+
+```sh
+m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites/a-team --content '[{\"controlType\": 4,\"id\": \"42b8afe8-dafe-4c11-bfbf-df5ef5b1feb7\",\"position\": {\"layoutIndex\": 1,\"zoneIndex\": 1,\"sectionIndex\": 1,\"sectionFactor\": 12,\"controlIndex\": 1},\"addedFromPersistedData\": true,\"innerHTML\":\"<p>Hello World</p>\"}]'
+```
+
+Note, how the content option has escaped double quotes `'[{\"controlType\": 4,\"id\": \"42b8afe8-dafe-4c11-bfbf-df5ef5b1feb7\",\"position\": {\"layoutIndex\": 1,\"zoneIndex\": 1,\"sectionIndex\": 1,\"sectionFactor\": 12,\"controlIndex\": 1},\"addedFromPersistedData\": true,\"innerHTML\":\"<p>Hello World</p>\"}]'` compared to execution from bash `''[{"controlType": 4,"id": "42b8afe8-dafe-4c11-bfbf-df5ef5b1feb7","position": {"layoutIndex": 1,"zoneIndex": 1,"sectionIndex": 1,"sectionFactor": 12,"controlIndex": 1},"addedFromPersistedData": true,"innerHTML":"<p>Hello World</p>"}]'`.
+
+:::caution Escaping JSON in PowerShell
+
+    When using the `--content` option it's possible to enter a JSON string. In PowerShell 5 to 7.2 [specific escaping rules](./../../../user-guide/using-cli.mdx#escaping-double-quotes-in-powershell) apply due to an issue. Remember that you can also use [file tokens](./../../../user-guide/using-cli.mdx#passing-complex-content-into-cli-options) instead.
+
+:::
+
 ## Examples
 
 Change the layout of the existing page to _Article_
@@ -102,6 +119,12 @@ Set page description
 m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites/a-team --description "Description to add for the page"
 ```
 
+Set page content
+
+```sh
+m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites/a-team --content '[{\"controlType\": 4,\"id\": \"42b8afe8-dafe-4c11-bfbf-df5ef5b1feb7\",\"position\": {\"layoutIndex\": 1,\"zoneIndex\": 1,\"sectionIndex\": 1,\"sectionFactor\": 12,\"controlIndex\": 1},\"addedFromPersistedData\": true,\"innerHTML\":\"<p>Hello World</p>\"}]'
+```
+
 ## Response
 
 The command won't return a response on success.

package/docs/docs/cmd/spo/site/site-commsite-enable.mdx

@@ -17,7 +17,10 @@ m365 spo site commsite enable [options]
 : The URL of the site to enable communication site features on
 
 `-i, --designPackageId [designPackageId]`
-: The ID of the site design to apply when enabling communication site features. Allowed values are `96c933ac-3698-44c7-9f4a-5fd17d71af9e` (Topic = default), `6142d2a0-63a5-4ba0-aede-d9fefca2c767` (Showcase), `f6cc5403-0d63-442e-96c0-285923709ffc` (Blank)
+: The ID of the site design to apply when enabling communication site features. Specify designPackageId or designPackage but not both.
+
+`-p, --designPackage [designPackage]`
+: The site design to apply when enabling communication site features. Valid values are: Topic, Showcase, or Blank. Defaults to Topic. Specify designPackageId or designPackage but not both.
 ```
 
 <Global />
@@ -38,12 +41,18 @@ Enable communication site features on an existing site
 m365 spo site commsite enable --url https://contoso.sharepoint.com
 ```
 
-Enable communication site features on an existing site and apply Showcase design package
+Enable communication site features on an existing site and apply the Showcase design package using its ID.
 
 ```sh
 m365 spo site commsite enable --url https://contoso.sharepoint.com --designPackageId 6142d2a0-63a5-4ba0-aede-d9fefca2c767
 ```
 
+Enable communication site features on an existing site and apply the Showcase design package using its friendly name.
+
+```sh
+m365 spo site commsite enable --url https://contoso.sharepoint.com --designPackage Showcase
+```
+
 ## Response
 
 The command won't return a response on success.

package/docs/docs/cmd/teams/app/app-remove.mdx

@@ -13,11 +13,14 @@ m365 teams app remove [options]
 ## Options
 
 ```md definition-list
-`-i, --id <id>`
-: ID of the Teams app to remove. Needs to be available in your organization\'s app catalog.
+`-i, --id [id]`
+: ID of the Teams app to remove. Needs to be available in your organization\'s app catalog. Specify either `id` or `name`.
+
+`-n, --name [name]`
+: Name of the Teams app to remove. Needs to be available in your organization\'s app catalog. Specify either `id` or `name`.
 
 `-f, --force`
-: Don't prompt for confirming removing the app
+: Don't prompt for confirming removing the app.
 ```
 
 <Global />
@@ -28,16 +31,16 @@ You can only remove a Teams app as a global administrator.
 
 ## Examples
 
-Remove the Teams app with ID _83cece1e-938d-44a1-8b86-918cf6151957_ from the organization's app catalog. Will prompt for confirmation before actually removing the app.
+Remove the Teams app by ID from the organization's app catalog. Will prompt for confirmation before actually removing the app.
 
 ```sh
 m365 teams app remove --id 83cece1e-938d-44a1-8b86-918cf6151957
 ```
 
-Remove the Teams app with ID _83cece1e-938d-44a1-8b86-918cf6151957_ from the organization's app catalog. Don't prompt for confirmation.
+Remove the Teams app by name from the organization's app catalog. Don't prompt for confirmation.
 
 ```sh
-m365 teams app remove --id 83cece1e-938d-44a1-8b86-918cf6151957 --force
+m365 teams app remove --name HelloWorld --force
 ```
 
 ## Response

package/docs/docs/cmd/teams/channel/channel-member-add.mdx

@@ -25,10 +25,10 @@ m365 teams channel member add [options]
 `--channelName [channelName]`
 : The display name of the Microsoft Teams team channel. Specify either `channelId` or `channelName`, but not both.
 
-`--userId [userId]`
+`--userIds [userIds]`
 : The user's ID or principal name. You can also pass a comma-separated list of userIds.
 
-`--userDisplayName [userDisplayName]`
+`--userDisplayNames [userDisplayNames]`
 : The display name of a user. You can also pass a comma-separated list of display names.
 
 `--owner`
@@ -48,13 +48,13 @@ You can only add members and owners of a team to a private channel.
 Add members to a channel based on their id or user principal name
 
 ```sh
-m365 teams channel member add --teamId 47d6625d-a540-4b59-a4ab-19b787e40593 --channelId 19:586a8b9e36c4479bbbd378e439a96df2@thread.skype --userId "85a50aa1-e5b8-48ac-b8ce-8e338033c366,john.doe@contoso.com"
+m365 teams channel member add --teamId 47d6625d-a540-4b59-a4ab-19b787e40593 --channelId 19:586a8b9e36c4479bbbd378e439a96df2@thread.skype --userIds "85a50aa1-e5b8-48ac-b8ce-8e338033c366,john.doe@contoso.com"
 ```
 
 Add owners to a channel based on their display names
 
 ```sh
-m365 teams channel member add --teamName "Human Resources" --channelName "Private Channel" --userDisplayName "Anne Matthews,John Doe" --owner
+m365 teams channel member add --teamName "Human Resources" --channelName "Private Channel" --userDisplayNames "Anne Matthews,John Doe" --owner
 ```
 
 ## Response

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnp/cli-microsoft365",
-  "version": "7.0.0-beta.c2db9df",
+  "version": "7.0.0-beta.e15bb2d",
   "description": "Manage Microsoft 365 and SharePoint Framework projects on any platform",
   "license": "MIT",
   "main": "./dist/api.js",
@@ -144,6 +144,7 @@
     "Kesavanarayanan, Sudharsan <10280385+sudharsank@users.noreply.github.com>",
     "Khalil, Bassem <bk@bassems-air.home>",
     "Kirkham, Don <donkirkham@live.com>",
+    "Kornet, Michał <kornetmichal@gmail.com>",
     "Kumar, Shantha <34408892+ktskumar@users.noreply.github.com>",
     "Kurian, Cyril C <cyril.kurian2@gmail.com>",
     "Lamber, Patrick <patrick@nubo.eu>",