@pnp/cli-microsoft365 6.0.0-beta.e031afa → 6.0.0-beta.e42aed1

package/docs/docs/cmd/spo/page/page-column-list.md

@@ -13,7 +13,7 @@ m365 spo page column list [options]
 `-u, --webUrl <webUrl>`
 : URL of the site where the page to retrieve is located
 
-`-n, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page to list columns of
 
 `-s, --section <sectionId>`
@@ -23,12 +23,12 @@ m365 spo page column list [options]
 
 ## Remarks
 
-If the specified name doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
 
 ## Examples
 
 List columns in the first section of a modern page with name _home.aspx_
 
 ```sh
-m365 spo page column list --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx --section 1
+m365 spo page column list --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx --section 1
 ```

package/docs/docs/cmd/spo/page/page-control-get.md

@@ -13,7 +13,7 @@ m365 spo page control get [options]
 `-i, --id <id>`
 : ID of the control to retrieve information for
 
-`-n, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page where the control is located
 
 `-u, --webUrl <webUrl>`
@@ -23,12 +23,12 @@ m365 spo page control get [options]
 
 ## Remarks
 
-If the specified `name` doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
 
 ## Examples
 
 Get information about the control with ID _3ede60d3-dc2c-438b-b5bf-cc40bb2351e1_ placed on a modern page with name _home.aspx_
 
 ```sh
-m365 spo page control get --id 3ede60d3-dc2c-438b-b5bf-cc40bb2351e1 --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx
+m365 spo page control get --id 3ede60d3-dc2c-438b-b5bf-cc40bb2351e1 --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx
 ```

package/docs/docs/cmd/spo/page/page-control-list.md

@@ -10,7 +10,7 @@ m365 spo page control list [options]
 
 ## Options
 
-`-n, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page to list controls of
 
 `-u, --webUrl <webUrl>`
@@ -20,12 +20,12 @@ m365 spo page control list [options]
 
 ## Remarks
 
-If the specified name doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
 
 ## Examples
 
 List controls on the modern page with name _home.aspx_
 
 ```sh
-m365 spo page control list --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx
+m365 spo page control list --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx
 ```

package/docs/docs/cmd/spo/page/page-control-set.md

@@ -13,7 +13,7 @@ m365 spo page control set [options]
 `-i, --id <id>`
 : ID of the control to update properties of
 
-`-n, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page where the control is located
 
 `-u, --webUrl <webUrl>`
@@ -29,20 +29,21 @@ m365 spo page control set [options]
 
 ## Remarks
 
-If the specified `name` doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
 
-When specifying the JSON string with web part properties on Windows, you have to escape double quotes in a specific way. Considering the following value for the _webPartProperties_ option: `{"Foo":"Bar"}`, you should specify the value as \`"{""Foo"":""Bar""}"\`. In addition, when using PowerShell, you should use the `--%` argument.
+!!! warning "Escaping JSON in PowerShell"
+    When using the `--webPartProperties` option it's possible to enter a JSON string. In PowerShell 5 to 7.2 [specific escaping rules](./../../../user-guide/using-cli.md#escaping-double-quotes-in-powershell) apply due to an issue. Remember that you can also use [file tokens](./../../../user-guide/using-cli.md#passing-complex-content-into-cli-options) instead.
 
 ## Examples
 
 Update web part data for the control with ID _3ede60d3-dc2c-438b-b5bf-cc40bb2351e1_ placed on a modern page with name _home.aspx_
 
 ```sh
-m365 spo page control set --id 3ede60d3-dc2c-438b-b5bf-cc40bb2351e1 --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx --webPartData '{"title":"New WP Title","properties": {"description": "New description"}}'
+m365 spo page control set --id 3ede60d3-dc2c-438b-b5bf-cc40bb2351e1 --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx --webPartData '{"title":"New WP Title","properties": {"description": "New description"}}'
 ```
 
 Update web part properties for the control with ID _3ede60d3-dc2c-438b-b5bf-cc40bb2351e1_ placed on a modern page with name _home.aspx_
 
 ```sh
-m365 spo page control set --id 3ede60d3-dc2c-438b-b5bf-cc40bb2351e1 --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx --webPartProperties '{"description": "New description"}'
+m365 spo page control set --id 3ede60d3-dc2c-438b-b5bf-cc40bb2351e1 --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx --webPartProperties '{"description": "New description"}'
 ```

package/docs/docs/cmd/spo/page/page-section-add.md

@@ -10,7 +10,7 @@ m365 spo page section add [options]
 
 ## Options
 
--n`, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page to add section to
 
 `-u, --webUrl <webUrl>`
@@ -26,12 +26,12 @@ m365 spo page section add [options]
 
 ## Remarks
 
-If the specified `name` doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
 
 ## Examples
 
 Add section to the modern page named _home.aspx_
 
 ```sh
-m365 spo page section add --name home.aspx --webUrl https://contoso.sharepoint.com/sites/newsletter  --sectionTemplate OneColumn --order 1
+m365 spo page section add --pageName home.aspx --webUrl https://contoso.sharepoint.com/sites/newsletter  --sectionTemplate OneColumn --order 1
 ```

package/docs/docs/cmd/spo/page/page-section-get.md

@@ -13,7 +13,7 @@ m365 spo page section get [options]
 `-u, --webUrl <webUrl>`
 : URL of the site where the page to retrieve is located
 
-`-n, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page to get section information of
 
 `-s, --section <sectionId>`
@@ -23,12 +23,12 @@ m365 spo page section get [options]
 
 ## Remarks
 
-If the specified name doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
 
 ## Examples
 
 Get information about the specified section of the modern page named _home.aspx_
 
 ```sh
-m365 spo page section get --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx --section 1
+m365 spo page section get --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx --section 1
 ```

package/docs/docs/cmd/spo/page/page-section-list.md

@@ -13,19 +13,19 @@ m365 spo page section list [options]
 `-u, --webUrl <webUrl>`
 : URL of the site where the page to retrieve is located
 
-`-n, --name <name>`
+`-n, --pageName <pageName>`
 : Name of the page to list sections of
 
 --8<-- "docs/cmd/_global.md"
 
 ## Remarks
 
-If the specified name doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
+If the specified `pageName` doesn't refer to an existing modern page, you will get a _File doesn't exists_ error.
 
 ## Examples
 
 List sections of a modern page named _home.aspx_
 
 ```sh
-m365 spo page section list --webUrl https://contoso.sharepoint.com/sites/team-a --name home.aspx
+m365 spo page section list --webUrl https://contoso.sharepoint.com/sites/team-a --pageName home.aspx
 ```

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

@@ -17,10 +17,13 @@ m365 spo page set [options]
 : URL of the site where the page to update is located
 
 `-l, --layoutType [layoutType]`
-: Layout of the page. Allowed values `Article`, `Home`, `SingleWebPartAppPage`, `RepostPage`,`HeaderlessSearchResults`, `Spaces`, `Topic`
+: Layout of the page. Allowed values `Article`, `Home`, `SingleWebPartAppPage`, `RepostPage`, `HeaderlessSearchResults`, `Spaces`, `Topic`
 
 `-p, --promoteAs [promoteAs]`
-: Update the page purpose. Allowed values `HomePage`, `NewsPage`
+: Update the page purpose. Allowed values `HomePage`, `NewsPage`, `Template`
+
+`--demoteFrom [demoteFrom]`
+: Update the page purpose back to a regular article. Allowed values `NewsPage`
 
 `--commentsEnabled [commentsEnabled]`
 : Set to `true`, to enable comments on the page. Allowed values `true`, `false`
@@ -65,6 +68,12 @@ Promote the existing article page as a template
 m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites/a-team --promoteAs Template
 ```
 
+Demote the existing newspage
+
+```sh
+m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites/a-team --demoteFrom NewsPage
+```
+
 Change the page's layout to Home and set it as the site's home page
 
 ```sh
@@ -88,3 +97,7 @@ Set page description
 ```sh
 m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites/a-team --description "Description to add for the page"
 ```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/spo/roledefinition/roledefinition-add.md

@@ -0,0 +1,43 @@
+# spo roledefinition add
+
+Adds a new roledefinition to web
+
+## Usage
+
+```sh
+m365 spo roledefinition add [options]
+```
+
+## Options
+
+`-u, --webUrl <webUrl>`
+: URL of the site to which role should be added
+
+`-n, --name <name>`
+: role definition name
+
+`-d, --description [description]`
+: role definition description
+
+`--rights [rights]`
+: A case-sensitive string array that contain the permissions needed for the custom action. Allowed values `EmptyMask,ViewListItems,AddListItems,EditListItems,DeleteListItems,ApproveItems,OpenItems,ViewVersions,DeleteVersions,CancelCheckout,ManagePersonalViews,ManageLists,ViewFormPages,AnonymousSearchAccessList,Open,ViewPages,AddAndCustomizePages,ApplyThemeAndBorder,ApplyStyleSheets,ViewUsageData,CreateSSCSite,ManageSubwebs,CreateGroups,ManagePermissions,BrowseDirectories,BrowseUserInfo,AddDelPrivateWebParts,UpdatePersonalWebParts,ManageWeb,AnonymousSearchAccessWebLists,UseClientIntegration,UseRemoteAPIs,ManageAlerts,CreateAlerts,EditMyUserInfo,EnumeratePermissions,FullMask`. Default `EmptyMask`
+
+--8<-- "docs/cmd/_global.md"
+
+## Remarks
+
+The `--rights` option accepts **case-sensitive** values.
+
+## Examples
+
+Adds the role definition for site _https://contoso.sharepoint.com/sites/project-x_ with name _test_
+
+```sh
+m365 spo roledefinition add --webUrl https://contoso.sharepoint.com/sites/project-x --name test
+```
+
+Adds the role definition for site _https://contoso.sharepoint.com/sites/project-x_ with name _test_ and description _test description_ and rights _ViewListItems,AddListItems,EditListItems,DeleteListItems_
+
+```sh
+m365 spo roledefinition add --webUrl https://contoso.sharepoint.com/sites/project-x --name test --description "test description" --rights "ViewListItems,AddListItems,EditListItems,DeleteListItems"
+```

package/docs/docs/cmd/spo/roledefinition/roledefinition-get.md

@@ -1,6 +1,6 @@
 # spo roledefinition get
 
-Gets specified role definition from web by id
+Gets specified role definition from web
 
 ## Usage
 

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-grant-add.md

@@ -24,8 +24,10 @@ m365 spo sp grant add
 
 --8<-- "docs/cmd/_global.md"
 
+## Remarks
+
 !!! important
-    To use this command you have to have permissions to access the tenant admin site.
+    To use this command you must be a Global administrator.
 
 ## Examples
 

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-grant-list.md

@@ -18,8 +18,10 @@ m365 spo sp grant list
 
 --8<-- "docs/cmd/_global.md"
 
+## Remarks
+
 !!! important
-    To use this command you have to have permissions to access the tenant admin site.
+    To use this command you must be a Global administrator.
 
 ## Examples
 

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-grant-revoke.md

@@ -16,16 +16,16 @@ m365 spo sp grant revoke
 
 ## Options
 
-`-i, --grantId <grantId>`
+`-i, --id <id>`
 : `ObjectId` of the permission grant to revoke
 
 --8<-- "docs/cmd/_global.md"
 
-!!! important
-    To use this command you have to have permissions to access the tenant admin site.
-
 ## Remarks
 
+!!! important
+    To use this command you must be a Global administrator.
+
 The permission grant you want to revoke is denoted using its `ObjectId`. You can retrieve it using the [spo serviceprincipal grant list](./serviceprincipal-grant-list.md) command.
 
 ## Examples
@@ -33,5 +33,5 @@ The permission grant you want to revoke is denoted using its `ObjectId`. You can
 Revoke permission grant with ObjectId _50NAzUm3C0K9B6p8ORLtIsQccg4rMERGvFGRtBsk2fA_
 
 ```sh
-m365 spo serviceprincipal grant revoke --grantId 50NAzUm3C0K9B6p8ORLtIsQccg4rMERGvFGRtBsk2fA
+m365 spo serviceprincipal grant revoke --id 50NAzUm3C0K9B6p8ORLtIsQccg4rMERGvFGRtBsk2fA
 ```

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-permissionrequest-approve.md

@@ -16,16 +16,16 @@ m365 spo sp permissionrequest approve
 
 ## Options
 
-`-i, --requestId <requestId>`
+`-i, --id <id>`
 : ID of the permission request to approve
 
 --8<-- "docs/cmd/_global.md"
 
-!!! important
-    To use this command you have to have permissions to access the tenant admin site.
-
 ## Remarks
 
+!!! important
+    The admin role that's required to approve permissions depends on the API. To approve permissions to any of the third-party APIs registered in the tenant, the application administrator role is sufficient. To approve permissions for Microsoft Graph or any other Microsoft API, the Global Administrator role is required.
+
 The permission request you want to approve is denoted using its `ID`. You can retrieve it using the [spo serviceprincipal permissionrequest list](./serviceprincipal-permissionrequest-list.md) command.
 
 ## Examples
@@ -33,5 +33,5 @@ The permission request you want to approve is denoted using its `ID`. You can re
 Approve permission request with id _4dc4c043-25ee-40f2-81d3-b3bf63da7538_
 
 ```sh
-m365 spo serviceprincipal permissionrequest approve --requestId 4dc4c043-25ee-40f2-81d3-b3bf63da7538
+m365 spo serviceprincipal permissionrequest approve --id 4dc4c043-25ee-40f2-81d3-b3bf63da7538
 ```

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-permissionrequest-deny.md

@@ -16,16 +16,16 @@ m365 spo sp permissionrequest deny
 
 ## Options
 
-`-i, --requestId <requestId>`
+`-i, --id <id>`
 : ID of the permission request to deny
 
 --8<-- "docs/cmd/_global.md"
 
-!!! important
-    To use this command you have to have permissions to access the tenant admin site.
-
 ## Remarks
 
+!!! important
+    The admin role that's required to deny permissions depends on the API. To approve permissions to any of the third-party APIs registered in the tenant, the application administrator role is sufficient. To approve permissions for Microsoft Graph or any other Microsoft API, the Global Administrator role is required.
+
 The permission request you want to approve is denoted using its `ID`. You can retrieve it using the [spo serviceprincipal permissionrequest list](./serviceprincipal-permissionrequest-list.md) command.
 
 ## Examples
@@ -33,5 +33,5 @@ The permission request you want to approve is denoted using its `ID`. You can re
 Deny permission request with id _4dc4c043-25ee-40f2-81d3-b3bf63da7538_
 
 ```sh
-m365 spo serviceprincipal permissionrequest deny --requestId 4dc4c043-25ee-40f2-81d3-b3bf63da7538
+m365 spo serviceprincipal permissionrequest deny --id 4dc4c043-25ee-40f2-81d3-b3bf63da7538
 ```

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-permissionrequest-list.md

@@ -18,8 +18,10 @@ m365 spo sp permissionrequest list
 
 --8<-- "docs/cmd/_global.md"
 
+## Remarks
+
 !!! important
-    To use this command you have to have permissions to access the tenant admin site.
+    The admin role that's required to list permissions depends on the API. To approve permissions to any of the third-party APIs registered in the tenant, the application administrator role is sufficient. To approve permissions for Microsoft Graph or any other Microsoft API, the Global Administrator role is required.
 
 ## Examples
 

package/docs/docs/cmd/spo/serviceprincipal/serviceprincipal-set.md

@@ -24,11 +24,11 @@ m365 spo sp set
 
 --8<-- "docs/cmd/_global.md"
 
-!!! important
-    To use this command you have to have permissions to access the tenant admin site.
-
 ## Remarks
 
+!!! important
+    To use this command you must be a Global administrator.
+
 Using the `-e, --enabled` option you can specify whether the service principal should be enabled or disabled. Use `true` to enable the service principal and `false` to disable it.
 
 ## Examples

package/docs/docs/cmd/spo/site/site-add.md

@@ -46,9 +46,6 @@ m365 spo site add [options]
 `--siteDesignId [siteDesignId]`
 : Id of the custom site design to use to create the site. When creating a communication site, specify either `siteDesign` or `siteDesignId` (applies to type CommunicationSite)
 
-`--allowFileSharingForGuestUsers`
-: (deprecated. Use `shareByEmailEnabled` instead) Determines whether it's allowed to share file with guests (applies to type CommunicationSite)
-
 `--shareByEmailEnabled`
 : Determines whether it's allowed to share file with guests (applies to type CommunicationSite)
 
@@ -87,9 +84,9 @@ The value of the `--storageQuota` option must not exceed the company's available
 
 The value of the `--storageQuotaWarningLevel` option must not exceed the the value of the `--storageQuota` option.
 
-If you try to create a site with the same URL as a site that has been previously moved to the recycle bin, you will get an error. To avoid this error, you can use the `--removeDeletedSite` option. Prior to creating the site, the spo site classic add command will check if the site with the specified URL has been previously moved to the recycle bin and if so, will remove it. Because removing sites from the recycle bin might take a moment, it should be used in conjunction with the `--wait` option so that the new site is not created before the old site is fully removed.
+If you try to create a site with the same URL as a site that has been previously moved to the recycle bin, you will get an error. To avoid this error, you can use the `--removeDeletedSite` option. Prior to creating the site, the spo site add command will check if the site with the specified URL has been previously moved to the recycle bin and if so, will remove it. Because removing sites from the recycle bin might take a moment, it should be used in conjunction with the `--wait` option so that the new site is not created before the old site is fully removed.
 
-Deleting and creating classic site collections is by default asynchronous and depending on the current state of Office 365, might take up to few minutes. If you're building a script with steps that require the site to be fully provisioned, you should use the `--wait` flag. When using this flag, the spo site classic add command will keep running until it received confirmation from Office 365 that the site has been fully provisioned.
+Deleting and creating classic site collections is by default asynchronous and depending on the current state of Office 365, might take up to few minutes. If you're building a script with steps that require the site to be fully provisioned, you should use the `--wait` flag. When using this flag, the spo site add command will keep running until it received confirmation from Office 365 that the site has been fully provisioned.
 
 ## Remarks for modern sites
 

package/docs/docs/cmd/spo/site/site-appcatalog-add.md

@@ -10,7 +10,7 @@ m365 spo site appcatalog add [options]
 
 ## Options
 
-`-u, --url <url>`
+`-u, --siteUrl <siteUrl>`
 : URL of the site collection where the app catalog should be added
 
 --8<-- "docs/cmd/_global.md"
@@ -23,7 +23,7 @@ m365 spo site appcatalog add [options]
 Add a site collection app catalog to the specified site
 
 ```sh
-m365 spo site appcatalog add --url https://contoso.sharepoint/sites/site
+m365 spo site appcatalog add --siteUrl https://contoso.sharepoint/sites/site
 ```
 
 ## More information

package/docs/docs/cmd/spo/site/site-appcatalog-remove.md

@@ -10,7 +10,7 @@ m365 spo site appcatalog remove [options]
 
 ## Options
 
-`-u, --url <url>`
+`-u, --siteUrl <siteUrl>`
 : URL of the site collection containing the app catalog to disable
 
 --8<-- "docs/cmd/_global.md"
@@ -27,7 +27,7 @@ While the command uses the term *'remove'*, like its equivalent PowerShell cmdle
 Remove the site collection app catalog from specified site
 
 ```sh
-m365 spo site appcatalog remove --url https://contoso.sharepoint/sites/site
+m365 spo site appcatalog remove --siteUrl https://contoso.sharepoint/sites/site
 ```
 
 ## More information

package/docs/docs/cmd/spo/site/site-apppermission-add.md

@@ -14,7 +14,7 @@ m365 spo site apppermission add [options]
 : URL of the site collection to add the permission
 
 `-p, --permission <permission>`
-: Permission to site (`read`, `write`, `read,write`). If multiple permissions have to be granted, they have to be comma separated ex. `read,write`
+: Permission to site (`read`, `write`, `manage` or `fullcontrol`)
 
 `-i, --appId [appId]`
 : Client ID of the Azure AD app for which to grant permissions

package/docs/docs/cmd/spo/site/site-apppermission-get.md

@@ -13,7 +13,7 @@ m365 spo site apppermission get [options]
 `-u, --siteUrl <siteUrl>`
 : URL of the site collection where the permission to retrieve is located
 
-`-i, --permissionId <permissionId>`
+`-i, --id <id>`
 : ID of the permission to retrieve
 
 --8<-- "docs/cmd/_global.md"
@@ -23,5 +23,5 @@ m365 spo site apppermission get [options]
 Return a specific application permissions for the _https://contoso.sharepoint.com/sites/project-x_ site collection with permission id _aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0_
 
 ```sh
-m365 spo site apppermission get --siteUrl https://contoso.sharepoint.com/sites/project-x --permissionId aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0
+m365 spo site apppermission get --siteUrl https://contoso.sharepoint.com/sites/project-x --id aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0
 ```

package/docs/docs/cmd/spo/site/site-apppermission-remove.md

@@ -19,7 +19,7 @@ m365 spo site apppermission remove [options]
 `-n, --appDisplayName [appDisplayName]`
 : App display name
 
-`-i, --permissionId [permissionId]`
+`-i, --id [id]`
 : ID of the permission to remove
 
 `--confirm`
@@ -44,5 +44,5 @@ m365 spo site apppermission remove --siteUrl https://contoso.sharepoint.com/site
 Removes the application permission with the specified ID on site _https://contoso.sharepoint.com/sites/project-x_
 
 ```sh
-m365 spo site apppermission remove --siteUrl https://contoso.sharepoint.com/sites/project-x --permissionId aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0
+m365 spo site apppermission remove --siteUrl https://contoso.sharepoint.com/sites/project-x --id aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0
 ```

package/docs/docs/cmd/spo/site/site-apppermission-set.md

@@ -13,17 +13,17 @@ m365 spo site apppermission set [options]
 `-u, --siteUrl <siteUrl>`
 : URL of the site collection where the permission to retrieve is located
 
-`-i, --permissionId [permissionId]`
-: ID of the permission to update. Specify `permissionId`, `appId` or `appDisplayName`
+`-i, --id [id]`
+: ID of the permission to update. Specify `id`, `appId` or `appDisplayName`
 
 `--appId [appId]`
-: Client ID of the Azure AD app for which to update permissions. Specify `permissionId`, `appId` or `appDisplayName`
+: Client ID of the Azure AD app for which to update permissions. Specify `id`, `appId` or `appDisplayName`
 
 `-n, --appDisplayName [appDisplayName]`
-: Display name of the Azure AD app for which to update permissions. Specify `permissionId`, `appId` or `appDisplayName`
+: Display name of the Azure AD app for which to update permissions. Specify `id`, `appId` or `appDisplayName`
 
 `-p, --permission <permission>`
-: Permission to site (`read`, `write`, `read,write`). If multiple permissions have to be granted, they have to be comma separated ex. `read,write`
+: Permission to site (`read`, `write`, `manage` or `fullcontrol`)
 
 --8<-- "docs/cmd/_global.md"
 
@@ -32,7 +32,7 @@ m365 spo site apppermission set [options]
 Updates a specific application permission to _read_ for the _https://contoso.sharepoint.com/sites/project-x_ site collection with permission id _aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0_
 
 ```sh
-m365 spo site apppermission set --siteUrl https://contoso.sharepoint.com/sites/project-x --permissionId aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0 --permission read
+m365 spo site apppermission set --siteUrl https://contoso.sharepoint.com/sites/project-x --id aTowaS50fG1zLnNwLmV4dHw4OWVhNWM5NC03NzM2LTRlMjUtOTVhZC0zZmE5NWY2MmI2NmVAZGUzNDhiYzctMWFlYi00NDA2LThjYjMtOTdkYjAyMWNhZGI0 --permission read
 ```
 
 Updates a specific application permission to _read_ for the _https://contoso.sharepoint.com/sites/project-x_ site collection with an application called _Foo_

package/docs/docs/cmd/spo/site/site-chrome-set.md

@@ -10,7 +10,7 @@ m365 spo site chrome set [options]
 
 ## Options
 
-`-u, --url <url>`
+`-u, --siteUrl <siteUrl>`
 : URL of the site collection to which you want to change the chrome header/footer
 
 `--headerLayout [headerLayout]`
@@ -42,17 +42,17 @@ m365 spo site chrome set [options]
 Show site header in compact mode
 
 ```sh
-m365 spo site chrome set --url https://contoso.sharepoint.com/sites/project-x --headerLayout Compact
+m365 spo site chrome set --siteUrl https://contoso.sharepoint.com/sites/project-x --headerLayout Compact
 ```
 
 Show site header in extended mode and display the logo on the right
 
 ```sh
-m365 spo site chrome set --url https://contoso.sharepoint.com/sites/project-x  --headerLayout Extended --logoAlignment Right
+m365 spo site chrome set --siteUrl https://contoso.sharepoint.com/sites/project-x  --headerLayout Extended --logoAlignment Right
 ```
 
 Disable the footer on the site
 
 ```sh
-m365 spo site chrome set --url https://contoso.sharepoint.com/sites/project-x --disableFooter true
+m365 spo site chrome set --siteUrl https://contoso.sharepoint.com/sites/project-x --disableFooter true
 ```

package/docs/docs/cmd/spo/site/site-groupify.md

@@ -11,15 +11,9 @@ Connects site collection to an Microsoft 365 Group
 m365 spo site groupify [options]
 ```
 
-## Alias
-
-```sh
-m365 spo site groupify
-```
-
 ## Options
 
-`-u, --siteUrl <siteUrl>`
+`-u, --url <url>`
 : URL of the site collection being connected to new Microsoft 365 Group
 
 `-a, --alias <alias>`
@@ -51,25 +45,25 @@ When connecting site collection to an Microsoft 365 Group, SharePoint will creat
 Connect site collection to an Microsoft 365 Group
 
 ```sh
-m365 spo site groupify --siteUrl https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A'
+m365 spo site groupify --url https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A'
 ```
 
 Connect site collection to an Microsoft 365 Group and make the group public
 
 ```sh
-m365 spo site groupify --siteUrl https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A' --isPublic
+m365 spo site groupify --url https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A' --isPublic
 ```
 
 Connect site collection to an Microsoft 365 Group and set the group classification
 
 ```sh
-m365 spo site groupify --siteUrl https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A' --classification HBI
+m365 spo site groupify --url https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A' --classification HBI
 ```
 
 Connect site collection to an Microsoft 365 Group and keep the old home page
 
 ```sh
-m365 spo site groupify --siteUrl https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A' --keepOldHomepage
+m365 spo site groupify --url https://contoso.sharepoin.com/sites/team-a --alias team-a --displayName 'Team A' --keepOldHomepage
 ```
 
 ## More information