@pnp/cli-microsoft365 7.3.0 → 7.4.0-beta.2324d53

package/docs/docs/cmd/{aad → entra}/user/user-recyclebinitem-restore.mdx

@@ -2,12 +2,18 @@ import Global from '/docs/cmd/_global.mdx';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# aad user recyclebinitem restore
+# entra user recyclebinitem restore
 
 Restores a user from the recycle bin in the current tenant
 
 ## Usage
 
+```sh
+m365 entra user recyclebinitem restore [options]
+```
+
+## Alias
+
 ```sh
 m365 aad user recyclebinitem restore [options]
 ```
@@ -40,7 +46,7 @@ After running this command, it may take a minute before the user will reappear i
 Restore user from the recycle bin.
 
 ```sh
-m365 aad user recyclebinitem restore --id 990e2425-f595-43bc-85ed-b89a44093793
+m365 entra user recyclebinitem restore --id 990e2425-f595-43bc-85ed-b89a44093793
 ```
 
 ## Response

package/docs/docs/cmd/{aad → entra}/user/user-remove.mdx

@@ -1,11 +1,17 @@
 import Global from '/docs/cmd/_global.mdx';
 
-# aad user remove
+# entra user remove
 
 Removes a specific user
 
 ## Usage
 
+```sh
+m365 entra user remove [options]
+```
+
+## Alias
+
 ```sh
 m365 aad user remove [options]
 ```
@@ -50,13 +56,13 @@ After running this command, it may take a minute before the user is effectively
 Removes a specific user by id
 
 ```sh
-m365 aad user remove --id a33bd401-9117-4e0e-bb7b-3f61c1539e10
+m365 entra user remove --id a33bd401-9117-4e0e-bb7b-3f61c1539e10
 ```
 
 Removes a specific user by its UPN
 
 ```sh
-m365 aad user remove --userName john.doe@contoso.com
+m365 entra user remove --userName john.doe@contoso.com
 ```
 
 ## Response

package/docs/docs/cmd/{aad → entra}/user/user-set.mdx

@@ -1,11 +1,17 @@
 import Global from '/docs/cmd/_global.mdx';
 
-# aad user set
+# entra user set
 
 Updates information of the specified user
 
 ## Usage
 
+```sh
+m365 entra user set [options]
+```
+
+## Alias
+
 ```sh
 m365 aad user set [options]
 ```
@@ -87,48 +93,48 @@ If the user with the specified ID or username doesn't exist, or if the specified
 Update specific property _department_ of user with id _1caf7dcd-7e83-4c3a-94f7-932a1299c844_
 
 ```sh
-m365 aad user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --department IT
+m365 entra user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --department IT
 ```
 
 Update multiple properties of user by name
 ```sh
-m365 aad user set --userName steve@contoso.onmicrosoft.com --firstName John --lastName Doe --jobTitle "Sales Manager" --companyName Contoso --department Sales --officeLocation "New York"
+m365 entra user set --userName steve@contoso.onmicrosoft.com --firstName John --lastName Doe --jobTitle "Sales Manager" --companyName Contoso --department Sales --officeLocation "New York"
 ```
 
 Enable user with id _1caf7dcd-7e83-4c3a-94f7-932a1299c844_
 
 ```sh
-m365 aad user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --accountEnabled true
+m365 entra user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --accountEnabled true
 ```
 
 Disable user with id _1caf7dcd-7e83-4c3a-94f7-932a1299c844_
 
 ```sh
-m365 aad user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --accountEnabled false
+m365 entra user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --accountEnabled false
 ```
 
 Reset password of a given user by userName and require the user to change the password on the next sign in
 
 ```sh
-m365 aad user set --userName steve@contoso.onmicrosoft.com --resetPassword --newPassword 6NLUId79Lc24 --forceChangePasswordNextSignIn
+m365 entra user set --userName steve@contoso.onmicrosoft.com --resetPassword --newPassword 6NLUId79Lc24 --forceChangePasswordNextSignIn
 ```
 
 Change password of the currently logged in user
 
 ```sh
-m365 aad user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --currentPassword SLBF5gnRtyYc --newPassword 6NLUId79Lc24
+m365 entra user set --id 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --currentPassword SLBF5gnRtyYc --newPassword 6NLUId79Lc24
 ```
 
 Updates a user with a manager
 
 ```sh
-m365 aad user set --displayName "John Doe" --userName "john.doe@contoso.com" --managerUserName "adele@contoso.com"
+m365 entra user set --displayName "John Doe" --userName "john.doe@contoso.com" --managerUserName "adele@contoso.com"
 ```
 
 Updates a user by removing its manager
 
 ```sh
-m365 aad user set --userName "john.doe@contoso.com" --removeManager
+m365 entra user set --userName "john.doe@contoso.com" --removeManager
 ```
 
 ## Response

package/docs/docs/cmd/{aad → entra}/user/user-signin-list.mdx

@@ -2,12 +2,18 @@ import Global from '/docs/cmd/_global.mdx';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# aad user signin list
+# entra user signin list
 
-Retrieves the Azure AD user sign-ins for the tenant
+Retrieves the Entra ID user sign-ins for the tenant
 
 ## Usage
 
+```sh
+m365 entra user signin list [options]
+```
+
+## Alias
+
 ```sh
 m365 aad user signin list [options]
 ```
@@ -35,55 +41,55 @@ m365 aad user signin list [options]
 Get all user's sign-ins in your tenant
 
 ```sh
-m365 aad user signin list
+m365 entra user signin list
 ```
 
 Get all user's sign-ins filter by given user's UPN in the tenant
 
 ```sh
-m365 aad user signin list --userName 'johndoe@example.com'
+m365 entra user signin list --userName 'johndoe@example.com'
 ```
 
 Get all user's sign-ins filter by given user's Id in the tenant
 
 ```sh
-m365 aad user signin list --userId '11111111-1111-1111-1111-111111111111'
+m365 entra user signin list --userId '11111111-1111-1111-1111-111111111111'
 ```
 
 Get all user's sign-ins filter by given application display name in the tenant
 
 ```sh
-m365 aad user signin list --appDisplayName 'Graph explorer'
+m365 entra user signin list --appDisplayName 'Graph explorer'
 ```
 
 Get all user's sign-ins filter by given application identifier in the tenant
 
 ```sh
-m365 aad user signin list --appId '00000000-0000-0000-0000-000000000000'
+m365 entra user signin list --appId '00000000-0000-0000-0000-000000000000'
 ```
 
 Get all user's sign-ins filter by given user's UPN and application display name in the tenant
 
 ```sh
-m365 aad user signin list --userName 'johndoe@example.com' --appDisplayName 'Graph explorer'
+m365 entra user signin list --userName 'johndoe@example.com' --appDisplayName 'Graph explorer'
 ```
 
 Get all user's sign-ins filter by given user's Id and application display name in the tenant
 
 ```sh
-m365 aad user signin list --userId '11111111-1111-1111-1111-111111111111' --appDisplayName 'Graph explorer'
+m365 entra user signin list --userId '11111111-1111-1111-1111-111111111111' --appDisplayName 'Graph explorer'
 ```
 
 Get all user's sign-ins filter by given user's UPN and application identifier in the tenant
 
 ```sh
-m365 aad user signin list --userName 'johndoe@example.com' --appId '00000000-0000-0000-0000-000000000000'
+m365 entra user signin list --userName 'johndoe@example.com' --appId '00000000-0000-0000-0000-000000000000'
 ```
 
 Get all user's sign-ins filter by given user's Id and application identifier in the tenant
 
 ```sh
-m365 aad user signin list --userId '11111111-1111-1111-1111-111111111111' --appId '00000000-0000-0000-0000-000000000000'
+m365 entra user signin list --userId '11111111-1111-1111-1111-111111111111' --appId '00000000-0000-0000-0000-000000000000'
 ```
 
 ## Response
@@ -178,13 +184,13 @@ m365 aad user signin list --userId '11111111-1111-1111-1111-111111111111' --appI
   <TabItem value="Markdown">
 
   ```md
-  # aad user signin list
+  # entra user signin list
 
   Date: 2023-06-02
 
   Property | Value
   ---------|-------
-  # aad user signin list
+  # entra user signin list
 
   Date: 2023-06-02
 

package/docs/docs/cmd/graph/schemaextension/schemaextension-add.mdx

@@ -49,7 +49,7 @@ The schema extension owner is the ID of the Azure AD application that is the own
 
 The target types are the set of Microsoft Graph resource types (that support schema extensions) that this schema extension definition can be applied to. This option is specified as a comma-separated list
 
-:::warning Escaping JSON in PowerShell
+:::warning[Escaping JSON in PowerShell]
 
 When using the `--properties` 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/graph/schemaextension/schemaextension-set.mdx

@@ -40,7 +40,7 @@ The lifecycle state of the schema extension. The initial state upon creation is
 Possible states transitions are from `InDevelopment` to `Available` and `Available` to `Deprecated`.
 The target types are the set of Microsoft Graph resource types (that support schema extensions) that this schema extension definition can be applied to. This option is specified as a comma-separated list.
 
-:::warning Escaping JSON in PowerShell
+:::warning[Escaping JSON in PowerShell]
 
 When using the `--properties` 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/pa/app/app-get.mdx

@@ -20,6 +20,12 @@ m365 pa app get [options]
 
 `-d, --displayName [displayName]`
 : The display name of the Microsoft Power App to get information about.
+
+`--asAdmin`
+: Run the command as admin for apps you don't have permission to.
+
+`-e, --environmentName [environmentName]`
+: The name of the environment. Required when using `asAdmin`.
 ```
 
 <Global />
@@ -32,6 +38,9 @@ This command is based on an API that is currently in preview and is subject to c
 
 :::
 
+As a maker, you are able to retrieve the Power Apps you have permission to. As an administrator, you are also able to retrieve Power Apps from other users you don't have permission to. To get the app from another user, use the `asAdmin` option and make sure to specify the `environment` option as well.
+
+
 If you try to retrieve a non-existing Microsoft Power App, you will get the `Request failed with status code 404` error.
 
 ## Examples
@@ -48,6 +57,12 @@ Get information about the specified Microsoft Power App by the app's display nam
 m365 pa app get --displayName App
 ```
 
+Get information about the specific app you do not have access to.
+
+```sh
+m365 pa app get --name 3989cb59-ce1a-4a5c-bb78-257c5c39381d --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --asAdmin
+```
+
 ## Response
 
 <Tabs>

package/docs/docs/cmd/pa/app/app-remove.mdx

@@ -18,6 +18,12 @@ m365 pa app remove [options]
 
 `-f, --force`
 : Don't prompt for confirmation
+
+`--asAdmin`
+: Run the command as admin for apps you don't own.
+
+`-e, --environmentName [environmentName]`
+: The name of the environment. Required when using `asAdmin`.
 ```
 
 <Global />
@@ -26,6 +32,8 @@ m365 pa app remove [options]
 
 By default, the command will try to remove a Power App. As maker, you are able to delete the Power Apps you own. As administrator, you are also able to delete Power Apps from other users.
 
+To remove an app you do not own, use the `asAdmin` option and make sure to specify the `environmentName` option as well.
+
 To remove a model-driven Power App you need administrator permissions.
 
 If the Power App with the name you specified doesn't exist, you will get the `Error: App 'abc' does not exist` error.
@@ -44,6 +52,12 @@ Removes the specified Power App without confirmation
 m365 pa app remove --name 3989cb59-ce1a-4a5c-bb78-257c5c39381d --force
 ```
 
+Removes the specified Power App you don't own
+
+```sh
+m365 pa app remove --name 3989cb59-ce1a-4a5c-bb78-257c5c39381d --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --asAdmin
+```
+
 ## Response
 
 The command won't return a response on success.

package/docs/docs/cmd/planner/plan/plan-add.mdx

@@ -38,7 +38,7 @@ m365 planner plan add [options]
 
 ## Remarks
 
-- Related to the options `--shareWithUserIds` and `--shareWithUserNames`. If you are leveraging Microsoft 365 groups, use the `aad m365group user` commands to manage group membership to share the [group's](https://pnp.github.io/cli-microsoft365/cmd/aad/m365group/m365group-user-add/) plan. You can also add existing members of the group to this collection though it is not required for them to access the plan owned by the group.
+- Related to the options `--shareWithUserIds` and `--shareWithUserNames`. If you are leveraging Microsoft 365 groups, use the `entra m365group user` commands to manage group membership to share the [group's](https://pnp.github.io/cli-microsoft365/cmd/entra/m365group/m365group-user-add/) plan. You can also add existing members of the group to this collection though it is not required for them to access the plan owned by the group.
 
 - Hint: Unlike for groups, a Planner Roster can contain only 1 plan.
 

package/docs/docs/cmd/spo/applicationcustomizer/applicationcustomizer-add.mdx

@@ -41,7 +41,7 @@ m365 spo applicationcustomizer add --webUrl https://contoso.sharepoint.com/sites
 
 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/applicationcustomizer/applicationcustomizer-set.mdx

@@ -47,7 +47,7 @@ m365 spo applicationcustomizer set --webUrl https://contoso.sharepoint.com/sites
 
 Note, how the clientSideComponentProperties option (--clientSideComponentProperties) 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/commandset/commandset-add.mdx

@@ -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"}'`.
 
-:::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/commandset/commandset-set.mdx

@@ -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"}'`.
 
-:::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/contenttype/contenttype-set.mdx

@@ -39,7 +39,7 @@ m365 spo contenttype set [options]
 
 ## Remarks
 
-:::warning 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

@@ -82,7 +82,7 @@ Note, how the clientSideComponentProperties option (-p) has escaped double quote
 
 The `--rights` option accepts **case sensitive** values.
 
-:::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/customaction/customaction-set.mdx

@@ -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.
 
-:::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/field/field-set.mdx

@@ -41,7 +41,7 @@ m365 spo field set [options]
 
 Specify properties to update using their names, eg. `--Title 'New Title' --JSLink jslink.js`.
 
-:::warning 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-view-set.mdx

@@ -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 `<`.
 
-:::warning 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

@@ -38,7 +38,7 @@ m365 spo listitem add [options]
 
 ## Remarks
 
-:::warning 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

@@ -43,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
 ```
 
-:::warning 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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

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