@pnp/cli-microsoft365 6.0.0-beta.27b9708 → 6.0.0-beta.291f17c

package/docs/docs/cmd/spfx/package/package-generate.md

@@ -56,3 +56,7 @@ Generate a web part that shows the weather for Amsterdam. Load web part contents
 ```sh
 m365 spfx package generate --webPartTitle "Amsterdam weather" --webPartDescription "Shows weather in Amsterdam" --name amsterdam-weather --html @amsterdam-weather.html --allowTenantWideDeployment --enableForTeams all
 ```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/spfx/project/project-doctor.md

@@ -62,3 +62,95 @@ Validate if your project is correctly set up and get instructions to fix any iss
 ```sh
 m365 spfx project doctor --output tour
 ```
+
+## Response
+
+### Response with no issues
+
+=== "JSON"
+
+    ```json
+    []
+    ```
+
+=== "Text"
+
+    ```text
+    ✅ CLI for Microsoft 365 has found no issues in your project
+    ```
+
+=== "Markdown"
+
+    ````md
+    # Validate project spfx-solution
+
+    Date: 11/7/2022
+
+    ## Findings
+
+    ✅ CLI for Microsoft 365 has found no issues in your project
+    ````
+
+### Response with issues reported
+
+When the npm packages related issues are reported. 
+
+=== "JSON"
+
+    ```json
+    [
+      {
+        "description": "Install supported version of the office-ui-fabric-react package",
+        "id": "FN001022",
+        "file": "./package.json",
+        "position": {
+          "line": 24,
+          "character": 5
+        },
+        "resolution": "npm i -SE office-ui-fabric-react@7.174.1",
+        "resolutionType": "cmd",
+        "severity": "Required",
+        "title": "office-ui-fabric-react"
+      }
+    ]
+    ```
+
+=== "Text"
+
+    ```text
+    Execute in command line
+    -----------------------
+    npm i -SE office-ui-fabric-react@7.174.1
+    ```
+
+=== "Markdown"
+
+    ````md
+    # Validate project react-page-navigator
+
+    Date: 11/15/2022
+
+    ## Findings
+
+    Following is the list of issues found in your project. [Summary](#Summary) of the recommended fixes is included at the end of the report.
+
+    ### FN001022 office-ui-fabric-react | Required
+
+    Install supported version of the office-ui-fabric-react package
+
+    Execute the following command:
+
+    ```sh
+    npm i -SE office-ui-fabric-react@7.174.1
+    ```
+
+    File: [./package.json:24:5](./package.json)
+
+    ## Summary
+
+    ### Execute script
+
+    ```sh
+    npm i -SE office-ui-fabric-react@7.174.1
+    ```
+    ````

package/docs/docs/cmd/spfx/project/project-externalize.md

@@ -40,6 +40,8 @@ The `spfx project externalize` command helps you externalize your SharePoint Fra
 
 This command doesn't change your project files. Instead, it gives you a report with all steps necessary to externalize your project dependencies. Externalizing project dependencies 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 changes and verify that everything is working as expected.
 
+Supported SharePoint Framework versions are 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.3, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.3.4, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.7.1, 1.8.0, 1.8.1, 1.8.2, 1.9.1.
+
 ## Examples
 
 Get instructions to externalize the current SharePoint Framework project dependencies and save the findings in a Markdown file
@@ -53,3 +55,117 @@ Get instructions to externalize the current SharePoint Framework project depende
 ```sh
 m365 spfx project externalize
 ```
+
+## Response
+
+Below output will be produced to externalize the SharePoint Framework project dependencies.
+
+=== "JSON"
+
+    ```json
+    {
+      "externalConfiguration": {
+        "externals": {
+          "@pnp/sp": {
+            "path": "https://unpkg.com/@pnp/sp@^1.3.11/dist/sp.es5.umd.min.js",
+            "globalName": "pnp.sp",
+            "globalDependencies": [
+              "@pnp/logging",
+              "@pnp/common",
+              "@pnp/odata",
+              "tslib"
+            ]
+          },
+          "tslib": {
+            "path": "https://unpkg.com/tslib@^1.10.0/tslib.js",
+            "globalName": "tslib"
+          }
+        }
+      },
+      "edits": [
+        {
+          "action": "add",
+          "path": "C:\\react-global-news-sp2019\\src\\webparts\\news\\NewsWebPart.ts",
+          "targetValue": "require(\"tslib\");"
+        }
+      ]
+    }
+    ```
+
+
+=== "Text"
+
+    ```text
+    In the config/config.json file update the externals property to:
+
+    {
+      "externalConfiguration": {
+        "externals": {
+          "@pnp/sp": {
+            "path": "https://unpkg.com/@pnp/sp@^1.3.11/dist/sp.es5.umd.min.js",
+            "globalName": "pnp.sp",
+            "globalDependencies": [
+              "@pnp/logging",
+              "@pnp/common",
+              "@pnp/odata",
+              "tslib"
+            ]
+          },
+          "tslib": {
+            "path": "https://unpkg.com/tslib@^1.10.0/tslib.js",
+            "globalName": "tslib"
+          }
+        }
+      },
+      "edits": [
+        {
+          "action": "add",
+          "path": "C:\\react-global-news-sp2019\\src\\webparts\\news\\NewsWebPart.ts",
+          "targetValue": "require(\"tslib\");"
+        }
+      ]
+    }
+    ```
+
+=== "Markdown"
+
+    ````md
+    # Externalizing dependencies of project react-global-news-sp2019
+
+    Date: 11/7/2022
+
+    ## Findings
+
+    ### Modify files
+
+    #### [config.json](config/config.json)
+
+    Replace the externals property (or add if not defined) with
+    
+    ```json
+    {
+      "externals": {
+        "@pnp/sp": {
+          "path": "https://unpkg.com/@pnp/sp@^1.3.11/dist/sp.es5.umd.min.js",
+          "globalName": "pnp.sp",
+          "globalDependencies": [
+            "@pnp/logging",
+            "@pnp/common",
+            "@pnp/odata",
+            "tslib"
+          ]
+        },
+        "tslib": {
+          "path": "https://unpkg.com/tslib@^1.10.0/tslib.js",
+          "globalName": "tslib"
+        }
+      }
+    }
+    ```
+    
+    #### [C:\react-global-news-sp2019\src\webparts\news\NewsWebPart.ts](C:\react-global-news-sp2019\src\webparts\news\NewsWebPart.ts)
+    add
+    ```JavaScript
+    require("tslib");
+    ```
+    ````

package/docs/docs/cmd/spfx/project/project-rename.md

@@ -16,26 +16,13 @@ m365 spfx project rename [options]
 `--generateNewId`
 : Generate a new solution ID for the project
 
-`-h, --help`
-: output usage information
+--8<-- "docs/cmd/_global.md"
 
-`--query [query]`
-: JMESPath query string. See [http://jmespath.org/](http://jmespath.org/) for more information and examples
-
-`-o, --output [output]`
-: Output type. `json,text,csv,md`. Default `json`
-
-`--verbose`
-: Runs command with verbose logging
-
-`--debug`
-: Runs command with debug logging
+## Remarks
 
 !!! important
     Run this command in the folder where the project that you want to rename is located.
 
-## Remarks
-
 This command will update the project name in: _package.json_, _.yo-rc.json_, _package-solution.json_, _deploy-azure-storage.json_ and _README.md_.
 
 ## Examples
@@ -51,3 +38,7 @@ Renames SharePoint Framework project to contoso with new solution ID
 ```sh
 m365 spfx project rename --newName contoso --generateNewId
 ```
+
+## Response
+
+The command won't return a response on success.

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

@@ -32,7 +32,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.16.0-beta.1).
+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.16.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.
 
@@ -85,3 +85,103 @@ Get instructions to upgrade the current SharePoint Framework project to the late
 ```sh
 m365 spfx project upgrade --output tour
 ```
+
+## Response
+
+When upgrading an SPFx project built using version 1.15.0 to SPFx version 1.15.2, you'll get output similar to following (output is truncated):
+
+=== "JSON"
+
+    ```json
+    [
+      {
+        "description": "Upgrade SharePoint Framework dependency package @microsoft/sp-core-library",
+        "id": "FN001001",
+        "file": "./package.json",
+        "position": {
+          "line": 15,
+          "character": 5
+        },
+        "resolution": "npm i -SE @microsoft/sp-core-library@1.15.2",
+        "resolutionType": "cmd",
+        "severity": "Required",
+        "title": "@microsoft/sp-core-library"
+      },
+      {
+        "description": "Update version in .yo-rc.json",
+        "id": "FN010001",
+        "file": "./.yo-rc.json",
+        "position": {
+          "line": 5,
+          "character": 5
+        },
+        "resolution": "{\\\n  \"@microsoft/generator-sharepoint\": {\\\n    \"version\": \"1.15.2\"\\\n  }\\\n}",
+        "resolutionType": "json",
+        "severity": "Recommended",
+        "title": ".yo-rc.json version"
+      }
+    ]
+    ```
+
+=== "Text"
+
+    ```text
+    Execute in bash
+    -----------------------
+    npm i -SE @microsoft/sp-core-library@1.15.2
+
+    ./.yo-rc.json
+    -------------
+    Update version in .yo-rc.json:
+    {
+      "@microsoft/generator-sharepoint": {
+        "version": "1.15.2"
+      }
+    }
+    ```
+
+=== "Markdown"
+
+    ````md
+    # Upgrade project HelloWorld to v1.15.2
+
+    Date: 20/11/2022
+
+    ## Findings
+
+    Following is the list of steps required to upgrade your project to SharePoint Framework version 1.15.2. [Summary](#Summary) of the modifications is included at the end of the report.
+
+    ### FN001001 @microsoft/sp-core-library | Required
+
+    Upgrade SharePoint Framework dependency package @microsoft/sp-core-library
+
+    Execute the following command:
+
+    ```sh
+    npm i -SE @microsoft/sp-core-library@1.15.2
+    ```
+
+    File: [./package.json:17:5](./package.json)
+
+    ## Summary
+
+    ### Execute script
+
+    ```sh
+    npm i -SE @microsoft/sp-core-library@1.15.2
+    ```
+
+    ### Modify files
+
+    #### [./.yo-rc.json](./.yo-rc.json)
+
+    Update version in .yo-rc.json:
+
+    ```json
+    {
+      "@microsoft/generator-sharepoint": {
+        "version": "1.15.2"
+      }
+    }
+    ```
+    ````

package/docs/docs/cmd/spfx/spfx-doctor.md

@@ -13,6 +13,9 @@ m365 spfx doctor [options]
 `-e, --env [env]`
 : Version of SharePoint for which to check compatibility: `sp2016|sp2019|spo`
 
+`-v, --spfxVersion [spfxVersion]`
+: Version of the SharePoint Framework Yeoman generator to check compatibility for without `v`, eg. `1.11.0`
+
 `-h, --help`
 : output usage information
 
@@ -48,7 +51,7 @@ Next to verifying the readiness of your environment to use a particular version
 
 ## Examples
 
-Verify if your environment meets the requirements to work with the SharePoint Framework
+Verify if your environment meets the requirements to work with SharePoint Framework based on the globally installed version of the SharePoint Framework Yeoman generator or the current project
 
 ```sh
 m365 spfx doctor --output text
@@ -59,3 +62,47 @@ Verify if your environment meets the requirements to work with the SharePoint Fr
 ```sh
 m365 spfx doctor --env sp2019 --output text
 ```
+
+Verify if your environment meets the requirements to work with SharePoint Framework v1.11.0
+
+```sh
+m365 spfx doctor --spfxVersion 1.11.0 --output text
+```
+
+## Response
+
+### Response with no issues
+
+=== "Text"
+
+    ```text
+    CLI for Microsoft 365 SharePoint Framework doctor
+    Verifying configuration of your system for working with the SharePoint Framework
+
+    √ SharePoint Framework v1.15.0
+    √ Node v16.13.0    
+    √ yo v4.3.0
+    √ gulp-cli v2.3.0
+    √ bundled typescript used
+    ```
+
+### Response with issues reported
+
+When the installed version of Yeoman is lower than expected to run SharePoint Framework v1.15.0
+
+=== "Text"
+
+    ```text
+    CLI for Microsoft 365 SharePoint Framework doctor
+    Verifying configuration of your system for working with the SharePoint Framework
+
+    √ SharePoint Framework v1.15.0
+    √ Node v16.16.0
+    × yo v3.1.1 found, v^4 required
+    √ gulp-cli v2.3.0
+    √ bundled typescript used
+
+    Recommended fixes:
+
+    - npm i -g yo@4
+    ```

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

@@ -14,7 +14,13 @@ m365 spo contenttype add [options]
 : Absolute URL of the site where the content type should be created
 
 `-l, --listTitle [listTitle]`
-: Title of the list where the content type should be created (if it should be created as a list content type)
+: Title of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listId [listId]`
+: ID of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listUrl [listUrl]`
+: Server- or site-relative URL of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
 
 `-i, --id <id>`
 : The ID of the content type. Determines the parent content type
@@ -44,12 +50,24 @@ Create a site content type that inherits from the List item content type
 m365 spo contenttype add --webUrl https://contoso.sharepoint.com/sites/contoso-sales --name 'PnP Alert' --id 0x01007926A45D687BA842B947286090B8F67D --group 'PnP Content Types'
 ```
 
-Create a list content type that inherits from the List item content type
+Create a list (retrieved by Title) content type that inherits from the List item content type
 
 ```sh
 m365 spo contenttype add --webUrl https://contoso.sharepoint.com/sites/contoso-sales --listTitle Alerts --name 'PnP Alert' --id 0x01007926A45D687BA842B947286090B8F67D
 ```
 
+Create a list (retrieved by ID) content type that inherits from the List item content type
+
+```sh
+m365 spo contenttype add --webUrl https://contoso.sharepoint.com/sites/contoso-sales --listId '8c7a0fcd-9d64-4634-85ea-ce2b37b2ec0c' --name 'PnP Alert' --id 0x01007926A45D687BA842B947286090B8F67D
+```
+
+Create a list (retrieved by URL) content type that inherits from the List item content type
+
+```sh
+m365 spo contenttype add --webUrl https://contoso.sharepoint.com/sites/contoso-sales --listUrl '/Shared Documents' --name 'PnP Alert' --id 0x01007926A45D687BA842B947286090B8F67D
+```
+
 ## More information
 
 - Content Type IDs: [https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/aa543822(v%3Doffice.14)](https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/aa543822(v%3Doffice.14))

package/docs/docs/cmd/spo/contenttype/contenttype-field-remove.md

@@ -14,7 +14,13 @@ m365 spo contenttype field remove [options]
 : Absolute URL of the site where the content type is located
 
 `-l, --listTitle [listTitle]`
-: Title of the list where the content type is located (if it is a list content type)
+: Title of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listId [listId]`
+: ID of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listUrl [listUrl]`
+: Server- or site-relative URL of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
 
 `-i, --contentTypeId <contentTypeId>`
 : The ID of the content type to remove the column from
@@ -32,20 +38,32 @@ m365 spo contenttype field remove [options]
 
 ## Examples
 
-Remove column with ID _2c1ba4c4-cd9b-4417-832f-92a34bc34b2a_ from content type with ID _0x0100CA0FA0F5DAEF784494B9C6020C3020A6_ from web with URL _https://contoso.sharepoint.com_
+Remove column with a specific ID from a content type with a specific ID from a specific site.
 
 ```sh
 m365 spo contenttype field remove  --contentTypeId "0x0100CA0FA0F5DAEF784494B9C6020C3020A6" --fieldLinkId "880d2f46-fccb-43ca-9def-f88e722cef80" --webUrl https://contoso.sharepoint.com --confirm
 ```
 
-Remove column with ID _2c1ba4c4-cd9b-4417-832f-92a34bc34b2a_ from content type with ID _0x0100CA0FA0F5DAEF784494B9C6020C3020A6_ from web with URL _https://contoso.sharepoint.com_ updating child content types
+Remove column with a specific ID from a content type with a specific ID from a specific site and updating the child content types
 
 ```sh
 m365 spo contenttype field remove  --contentTypeId "0x0100CA0FA0F5DAEF784494B9C6020C3020A6" --fieldLinkId "880d2f46-fccb-43ca-9def-f88e722cef80" --webUrl https://contoso.sharepoint.com --updateChildContentTypes
 ```
 
-Remove fieldLink with ID _2c1ba4c4-cd9b-4417-832f-92a34bc34b2a_ from list content type with ID _0x0100CA0FA0F5DAEF784494B9C6020C3020A6_ from web with URL _https://contoso.sharepoint.com_
+Remove fieldLink with a specific ID from a list (obtained by Title) content type with a specific ID on a spefici site.
 
 ```sh
 m365 spo contenttype field remove  --contentTypeId "0x0100CA0FA0F5DAEF784494B9C6020C3020A60062F089A38C867747942DB2C3FC50FF6A" --fieldLinkId "880d2f46-fccb-43ca-9def-f88e722cef80" --webUrl https://contoso.sharepoint.com --listTitle "Documents"
 ```
+
+Remove fieldLink with a specific ID from a list (obtained by ID) content type with a specific ID on a spefici site.
+
+```sh
+m365 spo contenttype field remove  --contentTypeId "0x0100CA0FA0F5DAEF784494B9C6020C3020A60062F089A38C867747942DB2C3FC50FF6A" --fieldLinkId "880d2f46-fccb-43ca-9def-f88e722cef80" --webUrl https://contoso.sharepoint.com --listId "8c7a0fcd-9d64-4634-85ea-ce2b37b2ec0c"
+```
+
+Remove fieldLink with a specific ID from a list (obtained by URL) content type with a specific ID on a spefici site.
+
+```sh
+m365 spo contenttype field remove  --contentTypeId "0x0100CA0FA0F5DAEF784494B9C6020C3020A60062F089A38C867747942DB2C3FC50FF6A" --fieldLinkId "880d2f46-fccb-43ca-9def-f88e722cef80" --webUrl https://contoso.sharepoint.com --listUrl "/shared documents"
+```

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

@@ -14,7 +14,13 @@ m365 spo contenttype get [options]
 : Absolute URL of the site where the content type is located
 
 `-l, --listTitle [listTitle]`
-: Title of the list where the content type is located (if it is a list content type)
+: Title of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listId [listId]`
+: ID of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listUrl [listUrl]`
+: Server- or site-relative URL of the list (if it is a list content type). Specify either `listTitle`, `listId` or `listUrl`.
 
 `-i, --id [id]`
 : The ID of the content type to retrieve. Specify either id or name but not both
@@ -39,11 +45,23 @@ m365 spo contenttype get --webUrl https://contoso.sharepoint.com/sites/contoso-s
 Retrieve site content type by name
 
 ```sh
-m365 spo contenttype get --webUrl https://contoso.sharepoint.com/sites/contoso-sales --name "Document"
+m365 spo contenttype get --webUrl https://contoso.sharepoint.com/sites/contoso-sales --name 'Document'
 ```
 
-Retrieve list content type
+Retrieve list (retrieved by Title) content type 
 
 ```sh
 m365 spo contenttype get --webUrl https://contoso.sharepoint.com/sites/contoso-sales --listTitle Events --id 0x0100558D85B7216F6A489A499DB361E1AE2F
 ```
+
+Retrieve list (retrieved by ID) content type 
+
+```sh
+m365 spo contenttype get --webUrl https://contoso.sharepoint.com/sites/contoso-sales --listId '8c7a0fcd-9d64-4634-85ea-ce2b37b2ec0c' --id 0x0100558D85B7216F6A489A499DB361E1AE2F
+```
+
+Retrieve list (retrieved by URL) content type 
+
+```sh
+m365 spo contenttype get --webUrl https://contoso.sharepoint.com/sites/contoso-sales --listUrl '/Shared Documents' --id 0x0100558D85B7216F6A489A499DB361E1AE2F
+```

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

@@ -0,0 +1,45 @@
+# spo contenttype set
+
+Update existing content type
+
+## Usage
+
+```sh
+m365 spo contenttype set [options]
+```
+
+## Options
+
+`-u, --webUrl <webUrl>`
+: URL of the site where the content type to update is defined.
+
+`-i, --id [id]`
+: ID of the content type to update. Specify `id` or `name` but not both, one is required.
+
+`-n, name [name]`
+: Name of the content type to update. Specify the `id` or the `name` but not both, one is required.
+
+`--listTitle [listTitle]`
+: Title of the list if you want to update a list content type. Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listId [listId]`
+: ID of the list if you want to update a list content type. Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listUrl [listUrl]`
+: URL of the list if you want to update a list content type. Specify either `listTitle`, `listId` or `listUrl`.
+
+--8<-- "docs/cmd/_global.md"
+
+## Examples
+
+Move site content type to a different group
+
+```sh
+m365 spo contenttype set --id 0x001001 --webUrl https://contoso.sharepoint.com --Group "My group"
+```
+
+Rename list content type
+
+```sh
+m365 spo contenttype set --name "My old item" --webUrl https://contoso.sharepoint.com --listTitle "My list" --Name "My item"
+```

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

@@ -78,6 +78,9 @@ Note, how the clientSideComponentProperties option (-p) has escaped double quote
 
 The `--rights` option accepts **case sensitive** values.
 
+!!! warning "Escaping JSON in PowerShell"
+    When using the `--clientSideComponentProperties` 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
 
 Adds tenant-wide SharePoint Framework Application Customizer extension in site _https://contoso.sharepoint.com/sites/test_

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

@@ -77,12 +77,13 @@ Running this command from the Windows Command Shell (cmd.exe) or PowerShell for
 m365 spo customaction set --webUrl https://contoso.sharepoint.com/sites/test --id 058140e3-0e37-44fc-a1d3-79c487d371a3 --clientSideComponentProperties '{\"testMessage\":\"Test message\"}'
 ```
 
-Note, how the `clientSideComponentProperties` option (-p) has escaped double quotes `'{\"testMessage\":\"Test message\"}'` compared to execution from bash `'{"testMessage":"Test message"}'`.
-
 The `--rights` option accepts **case-sensitive** values.
 
 Note, specifying the scope option might speed up the execution of the command, but would not update the scope. If the scope has to be changed, then the existing custom action should be removed and new should be added with different scope.
 
+!!! warning "Escaping JSON in PowerShell"
+    When using the `--clientSideComponentProperties` 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
 
 Updates tenant-wide SharePoint Framework Application Customizer extension properties in site _https://contoso.sharepoint.com/sites/test_