npm - @pnp/cli-microsoft365 - Versions diffs - 7.4.0-beta.fce7b64 → 7.5.0-beta.0ae7da4 - Mend

@pnp/cli-microsoft365 7.4.0-beta.fce7b64 → 7.5.0-beta.0ae7da4

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

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

@@ -41,7 +41,7 @@ m365 spo listitem set [options]
 ## Remarks
-:::warning 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_.
-:::warning 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.
-:::warning 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,9 +63,9 @@ 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>"}]'`.
-:::warning 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.
+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-add.mdx CHANGED Viewed

@@ -101,7 +101,7 @@ Deleting and creating classic site collections is by default asynchronous and de
 The `--owners` option is mandatory for creating `CommunicationSite` sites with app-only permissions.
-When trying to create a team site using app-only permissions, you will get an _Insufficient privileges to complete the operation._ error. As a workaround, you can use the [`aad m365group add`](../../aad/m365group/m365group-add.mdx) command, followed by [`spo site set`](./site-set.mdx) to further configure the Team site.
+When trying to create a team site using app-only permissions, you will get an _Insufficient privileges to complete the operation._ error. As a workaround, you can use the [`entra m365group add`](../../entra/m365group/m365group-add.mdx) command, followed by [`spo site set`](./site-set.mdx) to further configure the Team site.
 ## Examples

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"}'`.
-:::warning 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"}'`.
-:::warning 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"}'`.
-:::warning 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
-:::warning 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
-:::warning 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
-:::warning
+:::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
-:::warning 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/spo/user/user-ensure.mdx CHANGED Viewed

@@ -18,24 +18,27 @@ m365 spo user ensure [options]
 `-u, --webUrl <webUrl>`
 : Absolute URL of the site.
+`--entraId [--entraId]`
+: Id of the user in Entra. Specify either `aadId`, `entraId`, or `userName`.
 `--aadId [--aadId]`
-: Id of the user in Azure AD. Specify either `aadId` or `userName` but not both.
+: (deprecated. Use `entraId` instead) Id of the user in Azure AD. Specify either `aadId`, `entraId`, or `userName`.
 `--userName [userName]`
-: User's UPN (user principal name, e.g. john@contoso.com). Specify either `aadId` or `userName` but not both.
+: User's UPN (user principal name, e.g. john@contoso.com). Specify either `aadId`, `entraId`, or `userName`.
 ```
 <Global />
 ## Examples
-Ensures a user by its Azure AD Id
+Ensures a user by its Entra Id.
 ```sh
-m365 spo user ensure --webUrl https://contoso.sharepoint.com/sites/project --aadId e254750a-eaa4-44f6-9517-b74f65cdb747
+m365 spo user ensure --webUrl https://contoso.sharepoint.com/sites/project --entraId e254750a-eaa4-44f6-9517-b74f65cdb747
 ```
-Ensures a user by its user principal name
+Ensures a user by its user principal name.
 ```sh
 m365 spo user ensure --webUrl https://contoso.sharepoint.com/sites/project --userName john@contoso.com

package/docs/docs/cmd/teams/team/team-add.mdx CHANGED Viewed

@@ -32,7 +32,7 @@ m365 teams team add [options]
 ## Remarks
-If you want to add a Team to an existing Microsoft 365 Group use the [aad m365group teamify](../../aad/m365group/m365group-teamify.mdx) command instead.
+If you want to add a Team to an existing Microsoft 365 Group use the [entra m365group teamify](../../entra/m365group/m365group-teamify.mdx) command instead.
 This command will return different responses based on the presence of the `--wait` option. If present, the command will return a `group` resource in the response. If not present, the command will return a `teamsAsyncOperation` resource in the response.

package/docs/docs/cmd/teams/user/user-app-add.mdx CHANGED Viewed

@@ -13,8 +13,11 @@ m365 teams user app add [options]
 ## Options
 ```md definition-list
-`--id <id>`
-: The ID of the app to install.
+`--id [id]`
+: The ID of the app to install. Specify either `id` or `name` but not both.
+`--name [name]`
+: Name of the app to install. Specify either `id` or `name` but not both.
 `--userId [userId]`
 : The ID of the user to install the app for. Specify either `userId` or `userName` but not both.
@@ -31,16 +34,16 @@ The `id` has to be the ID of the app from the Microsoft Teams App Catalog. Do no
 ## Examples
-Install an app from the catalog for the specified user by id.
+Install an app by id from the catalog for the specified user by id.
 ```sh
 m365 teams user app add --id 4440558e-8c73-4597-abc7-3644a64c4bce --userId 2609af39-7775-4f94-a3dc-0dd67657e900
 ```
-Install an app from the catalog for the specified user by name.
+Install an app by name from the catalog for the specified user by name.
 ```sh
-m365 teams user app add --id 4440558e-8c73-4597-abc7-3644a64c4bce --userName admin@contoso.com
+m365 teams user app add --name HelloWorld --userName admin@contoso.com
 ```
 ## Response