npm - @pnp/cli-microsoft365 - Versions diffs - 7.3.0-beta.01256d2 → 7.3.0-beta.6062919 - Mend

@pnp/cli-microsoft365 7.3.0-beta.01256d2 → 7.3.0-beta.6062919

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 (360) hide show

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

@@ -40,7 +40,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.

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/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/meeting/meeting-transcript-list.mdx CHANGED Viewed

@@ -46,13 +46,13 @@ m365 teams meeting transcript list --userName garthf@contoso.com --meetingId MSo
 ## Remarks
-:::caution
+:::warning
 This command is based on a Microsoft Graph API that is currently in preview and is subject to change once the API reached general availability.
 :::
-:::caution
+:::warning
 To run this command with application permissions, tenant administrators must create an application access policy and grant it to a user. This authorizes the app configured in the policy to fetch online meetings and/or online meeting artifacts on behalf of that user. For more details, click [here](https://learn.microsoft.com/graph/cloud-communication-online-meeting-application-access-policy).

package/docs/docs/cmd/tenant/people/people-profilecardproperty-add.mdx CHANGED Viewed

@@ -38,7 +38,7 @@ You can specify localized values for the `displayName` as well. These can be ent
 :::
-:::caution
+:::warning
 When adding an attribute to a profile card, it takes up to 24 hours for the addition to be displayed.

package/docs/docs/cmd/tenant/people/people-profilecardproperty-remove.mdx CHANGED Viewed

@@ -32,7 +32,7 @@ To use this command you must be either **Tenant Administrator** or **Global Admi
 :::
-:::caution
+:::warning
 When removing an attribute from a profile card, it takes up to 24 hours for the change to be displayed.

package/docs/docs/cmd/tenant/people/people-profilecardproperty-set.mdx CHANGED Viewed

@@ -38,7 +38,7 @@ You can specify localized values for the `displayName` as well. These can be ent
 :::
-:::caution
+:::warning
 When updating an attribute to a profile card, it takes up to 24 hours for the addition to be displayed.

package/docs/docs/cmd/yammer/group/group-list.mdx CHANGED Viewed

@@ -26,7 +26,7 @@ m365 yammer group list [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/group/group-user-add.mdx CHANGED Viewed

@@ -27,7 +27,7 @@ m365 yammer group user add [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/group/group-user-remove.mdx CHANGED Viewed

@@ -27,7 +27,7 @@ m365 yammer group user remove [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/message/message-add.mdx CHANGED Viewed

@@ -35,7 +35,7 @@ m365 yammer message add [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/message/message-get.mdx CHANGED Viewed

@@ -23,7 +23,7 @@ m365 yammer message get [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/message/message-like-set.mdx CHANGED Viewed

@@ -27,7 +27,7 @@ m365 yammer message like set [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/message/message-list.mdx CHANGED Viewed

@@ -38,7 +38,7 @@ m365 yammer message list [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/message/message-remove.mdx CHANGED Viewed

@@ -24,7 +24,7 @@ m365 yammer message remove [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/network/network-list.mdx CHANGED Viewed

@@ -23,7 +23,7 @@ m365 yammer network list [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/user/user-get.mdx CHANGED Viewed

@@ -26,7 +26,7 @@ m365 yammer user get [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/user/user-list.mdx CHANGED Viewed

@@ -35,7 +35,7 @@ m365 yammer user list [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.

package/docs/docs/cmd/yammer/yammer-search.mdx CHANGED Viewed

@@ -29,7 +29,7 @@ m365 yammer search [options]
 ## Remarks
-:::caution
+:::warning
 In order to use this command, you need to grant the Azure AD application used by the CLI for Microsoft 365 the permission to the Yammer API. To do this, execute the `cli consent --service yammer` command.