npm - @pnp/cli-microsoft365 - Versions diffs - 7.3.0-beta.73848f3 → 7.3.0-beta.9479ed4 - Mend

@pnp/cli-microsoft365 7.3.0-beta.73848f3 → 7.3.0-beta.9479ed4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (444) hide show

package/docs/docs/cmd/spo/commandset/commandset-add.mdx CHANGED Viewed

@@ -49,7 +49,7 @@ m365 spo commandset add --webUrl https://contoso.sharepoint.com/sites/test --tit
 Note, how the clientSideComponentProperties option (-p) has escaped double quotes `'{\"testMessage\":\"Test message\"}'` compared to execution from bash `'{"testMessage":"Test message"}'`.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/commandset/commandset-set.mdx CHANGED Viewed

@@ -56,7 +56,7 @@ m365 spo commandset set --webUrl https://contoso.sharepoint.com/sites/test --tit
 Note, how the clientSideComponentProperties option has escaped double quotes `'{\"testMessage\":\"Test message\"}'` compared to execution from bash `'{"testMessage":"Test message"}'`.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/contenttype/contenttype-set.mdx CHANGED Viewed

@@ -39,7 +39,7 @@ m365 spo contenttype set [options]
 ## Remarks
-:::caution Updating child content types
+:::warning Updating child content types
 When specifying the `--updateChildren` flag, SharePoint will only propagate the changes that are made in the current request. If you want to know more about updating a content type and propagating changes to child content types, be sure to [read more here](https://learn.microsoft.com/previous-versions/office/developer/sharepoint-2010/ms442695(v=office.14)#considerations-when-updating-child-content-types).

package/docs/docs/cmd/spo/customaction/customaction-add.mdx CHANGED Viewed

@@ -82,7 +82,7 @@ Note, how the clientSideComponentProperties option (-p) has escaped double quote
 The `--rights` option accepts **case sensitive** values.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/customaction/customaction-set.mdx CHANGED Viewed

@@ -85,7 +85,7 @@ 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.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/eventreceiver/eventreceiver-remove.mdx CHANGED Viewed

@@ -42,7 +42,7 @@ m365 spo eventreceiver remove [options]
 ## Remarks
-:::caution
+:::warning
 You can only remove an event receiver if it has been registered by an app with the same ID.

package/docs/docs/cmd/spo/field/field-set.mdx CHANGED Viewed

@@ -41,7 +41,7 @@ m365 spo field set [options]
 Specify properties to update using their names, eg. `--Title 'New Title' --JSLink jslink.js`.
-:::caution Escaping JSON in PowerShell
+:::warning Escaping JSON in PowerShell
 When updating column formatting for a field with the `--CustomFormatter` 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.

package/docs/docs/cmd/spo/list/list-sensitivitylabel-ensure.mdx CHANGED Viewed

@@ -36,7 +36,7 @@ m365 spo list sensitivitylabel ensure [options]
 ## Remarks
-:::caution
+:::warning
 This command is based on an API that is currently in preview and is subject to change once the API reaches general availability.

package/docs/docs/cmd/spo/list/list-view-set.mdx CHANGED Viewed

@@ -42,7 +42,7 @@ Specify properties to update using their names, eg. `--Title 'New Title' --JSLin
 When updating list formatting, the value of the CustomFormatter property must be XML-escaped, eg. `&lt;` instead of `<`.
-:::caution Escaping JSON in PowerShell
+:::warning Escaping JSON in PowerShell
 When updating list view formatting for a view with the `--CustomFormatter` 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.

package/docs/docs/cmd/spo/listitem/listitem-add.mdx CHANGED Viewed

@@ -38,7 +38,7 @@ m365 spo listitem add [options]
 ## Remarks
-:::caution When using DateTime fields
+:::warning When using DateTime fields
 When creating a list item with a DateTime field, use the timezone and the format that the site expects, based on its regional settings. Alternatively, a format which works on all regions is the following: `yyyy-MM-dd HH:mm:ss`. However, you should use the local timezone in all situations. UTC date/time or ISO 8601 formatted date/time is not supported.

package/docs/docs/cmd/spo/listitem/listitem-batch-add.mdx CHANGED Viewed

@@ -13,12 +13,15 @@ m365 spo listitem batch add [options]
 ## Options
 ```md definition-list
-`-p, --filePath <filePath>`
-: The absolute or relative path to a flat file containing the list items.
 `-u, --webUrl <webUrl>`
 : URL of the site.
+`-p, --filePath [filePath]`
+: The absolute or relative path to a flat file containing the list items. Specify `filePath` or `csvContent`, but not both.
+`-c, --csvContent [csvContent]`
+: A string content in CSV-format containing the list items. Specify `filePath` or `csvContent`, but not both.
 `-l, --listId [listId]`
 : ID of the list. Specify either `listTitle`, `listId` or `listUrl`, but not multiple.
@@ -40,7 +43,7 @@ ContentType,Title,SingleChoiceField,MultiChoiceField,SingleMetadataField,MultiMe
 Item,Title A,Choice 1,Choice 1;#Choice 2,Engineering|4a3cc5f3-a4a6-433e-a07a-746978ff1760;,Engineering|4a3cc5f3-a4a6-433e-a07a-746978ff1760;Finance|f994a4ac-cf34-448e-a22c-2b35fd9bbffa;,[{'Key':'i:0#.f|membership|markh@contoso.com'}],"[{'Key':'i:0#.f|membership|markh@contoso.com'},{'Key':'i:0#.f|membership|john.doe@contoso.com'}]","https://bing.com, URL",5,2023-01-01 10:00:00
 ```
-:::caution When using DateTime fields
+:::warning When using DateTime fields
 When creating list items with a DateTime field, use the timezone and the format that the site expects, based on its regional settings. Alternatively, a format which works on all regions is the following: `yyyy-MM-dd HH:mm:ss`. However, you should use the local timezone in all situations. UTC date/time or ISO 8601 formatted date/time is not supported.
@@ -54,6 +57,25 @@ Add a batch of items to a list retrieved by title in a specific site
 m365 spo listitem batch add --filePath "C:\Path\To\Csv\CsvFile.csv" --webUrl https://contoso.sharepoint.com/sites/project-x --listTitle "Demo List"
 ```
+Add a batch of items to a list retrieved by title in a specific site using csv content
+```sh
+$obj = @(
+  [PSCustomObject]@{
+    Title = "Item A"
+    Age = 10
+  },
+  [PSCustomObject]@{
+    Title = "Item B"
+    Age = 20
+  }
+)
+$csvContent = $obj | ConvertTo-Csv -NoTypeInformation -Delimiter "," | Out-String | ForEach-Object { $_.Replace('"','\"') }
+m365 spo listitem batch add --csvContent $csvContent --webUrl https://contoso.sharepoint.com/sites/project-x --listTitle "Demo List"
+```
 Add a batch of items to a list retrieved by Id in a specific site
 ```sh

package/docs/docs/cmd/spo/listitem/listitem-set.mdx CHANGED Viewed

@@ -41,7 +41,7 @@ m365 spo listitem set [options]
 ## Remarks
-:::caution When using DateTime fields
+:::warning When using DateTime fields
 When updating a list item with a DateTime field, use the timezone and the format that the site expects, based on its regional settings. Alternatively, a format which works on all regions is the following: `yyyy-MM-dd HH:mm:ss`. However, you should use the local timezone in all situations. UTC date/time or ISO 8601 formatted date/time is not supported.

package/docs/docs/cmd/spo/page/page-clientsidewebpart-add.mdx CHANGED Viewed

@@ -49,7 +49,7 @@ If the specified `pageName` doesn't refer to an existing modern page, you will g
 To add a standard web part to the page, specify one of the following values: _ContentRollup, BingMap, ContentEmbed, DocumentEmbed, Image, ImageGallery, LinkPreview, NewsFeed, NewsReel, PowerBIReportEmbed, QuickChart, SiteActivity, VideoEmbed, YammerEmbed, Events, GroupCalendar, Hero, List, PageTitle, People, QuickLinks, CustomMessageRegion, Divider, MicrosoftForms, Spacer_.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/page/page-control-set.mdx CHANGED Viewed

@@ -35,7 +35,7 @@ m365 spo page control set [options]
 If the specified `pageName` doesn't refer to an existing modern page, you will get a `File doesn't exists` error.
-:::caution Escaping JSON in PowerShell
+:::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.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.

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

@@ -63,7 +63,7 @@ m365 spo page set --name page.aspx --webUrl https://contoso.sharepoint.com/sites
 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
+:::warning 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.

package/docs/docs/cmd/spo/report/report-activityfilecounts.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report activityfilecounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-activitypages.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report activitypages [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-activityusercounts.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report activityusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-activityuserdetail.mdx CHANGED Viewed

@@ -20,9 +20,6 @@ m365 spo report activityuserdetail [options]
 `-p, --period [period]`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`. Specify either `date` or `period`, but not both.
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams device usage by user report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagedetail.mdx CHANGED Viewed

@@ -20,9 +20,6 @@ m365 spo report siteusagedetail [options]
 `-p, --period [period]`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`. Specify either `date` or `period`, but not both.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagefilecounts.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report siteusagefilecounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagepages.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report siteusagepages [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagesitecounts.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report siteusagesitecounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagestorage.mdx CHANGED Viewed

@@ -17,9 +17,6 @@ m365 spo report siteusagestorage [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 <Global />

package/docs/docs/cmd/spo/site/site-groupify.mdx CHANGED Viewed

@@ -41,7 +41,7 @@ m365 spo site groupify [options]
 ## Remarks
-:::caution
+:::warning
 This command is based on a SharePoint API that is currently in preview and is subject to change once the API reached general availability.

package/docs/docs/cmd/spo/site/site-recyclebinitem-clear.mdx CHANGED Viewed

@@ -27,7 +27,7 @@ m365 spo site recyclebinitem clear [options]
 ## Remarks
-:::caution
+:::warning
 Items in the recycle bin will be permanently removed without the ability to restore them.

package/docs/docs/cmd/spo/site/site-recyclebinitem-remove.mdx CHANGED Viewed

@@ -27,7 +27,7 @@ m365 spo site recyclebinitem remove [options]
 ## Remarks
-:::caution
+:::warning
 Items in the recycle bin will be permanently removed without the ability to restore them.

package/docs/docs/cmd/spo/tenant/tenant-applicationcustomizer-add.mdx CHANGED Viewed

@@ -38,7 +38,7 @@ m365 spo tenant applicationcustomizer add --title "YourAppCustomizer" --clientSi
 Note, how the clientSideComponentProperties option has escaped double quotes `'{\"testMessage\":\"Test message\"}'` compared to execution from bash `'{"testMessage":"Test message"}'`.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/tenant/tenant-applicationcustomizer-set.mdx CHANGED Viewed

@@ -47,7 +47,7 @@ m365 spo tenant applicationcustomizer set --id 3 --clientSideComponentProperties
 Note, how the clientSideComponentProperties option (--clientSideComponentProperties) has escaped double quotes `'{\"someProperty\":\"Some value\"}'` compared to execution from bash `'{"someProperty": "Some value"}'`.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/tenant/tenant-commandset-add.mdx CHANGED Viewed

@@ -46,7 +46,7 @@ m365 spo tenant commandset add --title "YourAppCustomizer" --clientSideComponent
 Note, how the clientSideComponentProperties option has escaped double quotes `'{\"testMessage\":\"Test message\"}'` compared to execution from bash `'{"testMessage":"Test message"}'`.
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/tenant/tenant-commandset-set.mdx CHANGED Viewed

@@ -45,7 +45,7 @@ m365 spo tenant commandset set [options]
 ## Remarks
-:::caution Escaping JSON in PowerShell
+:::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.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.

package/docs/docs/cmd/spo/term/term-add.mdx CHANGED Viewed

@@ -53,7 +53,7 @@ m365 spo term add [options]
 ## Remarks
-:::caution Escaping JSON in PowerShell
+:::warning Escaping JSON in PowerShell
 When using the `--customProperties` and/or `--localCustomProperties` options 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.

package/docs/docs/cmd/spo/term/term-group-add.mdx CHANGED Viewed

@@ -32,7 +32,7 @@ m365 spo term group add [options]
 ## Remarks
-:::caution
+:::warning
 To use this command without the `--webUrl` option you must have permissions to access the tenant admin site.

package/docs/docs/cmd/spo/term/term-set-add.mdx CHANGED Viewed

@@ -41,7 +41,7 @@ m365 spo term set add [options]
 ## Remarks
-:::caution Escaping JSON in PowerShell
+:::warning Escaping JSON in PowerShell
 When using the `--customProperties` 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.

package/docs/docs/cmd/teams/app/app-install.mdx CHANGED Viewed

@@ -13,8 +13,11 @@ m365 teams app install [options]
 ## Options
 ```md definition-list
-`--id <id>`
-: The ID of the app to install
+`-i, --id [id]`
+: ID of the app to update. Specify either id or name, but not both
+`-n, --name [name]`
+: The display name of the app to update. Specify either id or name, but not both
 `--teamId [teamId]`
 : The ID of the Microsoft Teams team to which to install the app
@@ -52,6 +55,12 @@ Install a personal app for the user specified using their ID
 m365 teams app install --id 4440558e-8c73-4597-abc7-3644a64c4bce --userId 2609af39-7775-4f94-a3dc-0dd67657e900
 ```
+Install an app with name _Test app_ from the catalog in a Microsoft Teams team
+```sh
+m365 teams app install --name "Test app" --teamId 2609af39-7775-4f94-a3dc-0dd67657e900
+```
 ## Response
 The command won't return a response on success.