npm - @pnp/cli-microsoft365 - Versions diffs - 7.4.0-beta.ae3d33b → 7.4.0-beta.d2ff47d - Mend

@pnp/cli-microsoft365 7.4.0-beta.ae3d33b → 7.4.0-beta.d2ff47d

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

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/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.