@pnp/cli-microsoft365 7.4.0-beta.fce7b64 → 7.5.0-beta.23612bc

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/external/connection/connection-urltoitemresolver-add.mdx

@@ -0,0 +1,47 @@
+import Global from '/docs/cmd/_global.mdx';
+
+# external connection urltoitemresolver add
+
+Adds a URL to item resolver to an external connection
+
+## Usage
+
+```sh
+m365 external connection urltoitemresolver add [options]
+```
+
+## Options
+
+```md definition-list
+`-c, --externalConnectionId <externalConnectionId>`
+: The ID of the external connection to which to add the resolver
+
+`--baseUrls <baseUrls>`
+: Comma-separated list of base URLs
+
+`--urlPattern <urlPattern>`
+: Regex pattern to match URLs
+
+`-i, --itemId <itemId>`
+: Pattern that matches captured matches from the URL with the external item ID
+
+`-p, --priority <priority>`
+: Integer that defines the resolution order
+```
+<Global />
+
+## Examples
+
+Adds a URL to item resolver to an existing connection
+
+```sh
+m365 external connection urltoitemresolver add --externalConnectionId "samplesolutiongallery" --baseUrls "https://adoption.microsoft.com" --urlPattern "/sample-solution-gallery/sample/(?<sampleId>[^/]+)" --itemId "{sampleId}" --priority 1
+```
+
+## Response
+
+The command won't return a response on success.
+
+## More information
+
+- Microsoft Graph external connection activitySettings: [https://learn.microsoft.com/graph/api/resources/externalconnectors-activitysettings?view=graph-rest-1.0](https://learn.microsoft.com/graph/api/resources/externalconnectors-activitysettings?view=graph-rest-1.0)

package/docs/docs/cmd/flow/run/run-get.mdx

@@ -25,7 +25,14 @@ m365 flow run get [options]
 : The name of the environment where the flow is located
 
 `--includeTriggerInformation`
+: (deprecated. Use option `withTrigger` instead) If specified, include information about the trigger details
+
+`--withTrigger`
 : If specified, include information about the trigger details
+
+`--withActions [withActions]`
+: If specified, include information about all actions when no action names are specified, or provide a specified list of actions separated by commas to include only the relevant action details
+
 ```
 
 <Global />
@@ -44,7 +51,7 @@ If the Microsoft Flow with the name you specified doesn't exist, you will get th
 
 If the run with the name you specified doesn't exist, you will get the `The provided workflow run name is not valid.` error.
 
-If the option `includeTriggerInformation` is specified, but the trigger does not contain an outputsLink such as for example with a `Recurrence` trigger, this option will be ignored.
+If the option `withTrigger` is specified, but the trigger does not contain an outputsLink such as for example with a `Recurrence` trigger, this option will be ignored.
 
 ## Examples
 
@@ -57,7 +64,19 @@ m365 flow run get --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5
 Get information about the given run of the specified Power Automate flow including trigger information
 
 ```sh
-m365 flow run get --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --flowName 5923cb07-ce1a-4a5c-ab81-257ce820109a --name 08586653536760200319026785874CU62 --includeTriggerInformation
+m365 flow run get --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --flowName 5923cb07-ce1a-4a5c-ab81-257ce820109a --name 08586653536760200319026785874CU62 --withTrigger
+```
+
+Get information about the given run of the specified Power Automate flow including details about all associated actions.
+
+```sh
+m365 flow run get --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --flowName 5923cb07-ce1a-4a5c-ab81-257ce820109a --name 08586653536760200319026785874CU62 --withActions
+```
+
+Get information about the given run of the specified Power Automate flow including exclusively the details of 'Action_Internal_Name1' and 'Action_Internal_Name2' actions
+
+```sh
+m365 flow run get --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --flowName 5923cb07-ce1a-4a5c-ab81-257ce820109a --name 08586653536760200319026785874CU62 --withActions "Action_Internal_Name1,Action_Internal_Name2"
 ```
 
 ## Response
@@ -157,9 +176,9 @@ m365 flow run get --environmentName Default-d87a7535-dd31-4437-bfe1-95340acd55c5
   </TabItem>
 </Tabs>
 
-### `includeTriggerInformation` response
+### `withTrigger` response
 
-When using the option `includeTriggerInformation`, the response for the json-output will differ.
+When using the option `withTrigger`, the response for the json-output will differ.
 
 <Tabs>
   <TabItem value="JSON">
@@ -233,3 +252,147 @@ When using the option `includeTriggerInformation`, the response for the json-out
   </TabItem>
 </Tabs>
 
+### `withActions` response
+
+When using the option `withActions`, the response for the json-output will differ.
+
+<Tabs>
+  <TabItem value="JSON">
+
+  ```json
+  {
+    "name": "08585236861638480597867166179CU104",
+    "id": "/providers/Microsoft.ProcessSimple/environments/Default-e1dd4023-a656-480a-8a0e-c1b1eec51e1d/flows/24335774-daf6-4183-acb7-f5155c2cd2fe/runs/08585236861638480597867166179CU104",
+    "type": "Microsoft.ProcessSimple/environments/flows/runs",
+    "properties": {
+      "actions":{
+        "Compose": {
+          "input": "Test",
+          "inputsLink": {
+            "uri": "https://prod-255.westeurope.logic.azure.com:443/workflows/88b5146587d144ea85efb15683c4e58f/runs/08586652586741142222645090602CU35/actions/Compose/contents/ActionInputs?api-version=2016-06-01&se=2023-12-14T19%3A00%3A00.0000000Z&sp=%2Fruns%2F08586652586741142222645090602CU35%2Factions%2FCompose%2Fcontents%2FActionInputs%2Fread&sv=1.0&sig=wYD6bMHjdoOawYAMTHqpmyILowLKRCkFEfsNxi1NFzw",
+            "contentVersion": "test==",
+            "contentSize": 6,
+            "contentHash": {
+              "algorithm": "md5",
+              "value": "test=="
+            }
+          },
+          "output": "Test",
+          "outputsLink": {
+            "uri": "https://prod-255.westeurope.logic.azure.com:443/workflows/88b5146587d144ea85efb15683c4e58f/runs/08586652586741142222645090602CU35/actions/Compose/contents/ActionOutputs?api-version=2016-06-01&se=2023-12-14T19%3A00%3A00.0000000Z&sp=%2Fruns%2F08586652586741142222645090602CU35%2Factions%2FCompose%2Fcontents%2FActionOutputs%2Fread&sv=1.0&sig=KoI4_RAEVNFUgymktOFxvfb5mCoIKR2WCYGwexjD7kY",
+            "contentVersion": "test==",
+            "contentSize": 6,
+            "contentHash": {
+              "algorithm": "md5",
+              "value": "test=="
+            }
+          },
+          "startTime": "2023-11-17T21:06:14.466889Z",
+          "endTime": "2023-11-17T21:06:14.4676104Z",
+          "correlation": {
+            "actionTrackingId": "dabed750-0ec4-4c34-98f5-cc3695e0811e",
+            "clientTrackingId": "08585013686846794051719443325CU251",
+            "clientKeywords": [
+              "resubmitFlow"
+            ]
+          },
+          "status": "Succeeded",
+          "code": "OK"
+        }
+      },
+      "startTime": "2023-03-04T09:05:21.8066368Z",
+      "endTime": "2023-03-04T09:05:22.5880202Z",
+      "status": "Succeeded",
+      "correlation": {
+        "clientTrackingId": "08585236861638480598867166179CU131"
+      },
+      "trigger": {
+        "name": "When_an_email_is_flagged_(V4)",
+        "inputsLink": {
+          "uri": "https://prod-130.westeurope.logic.azure.com:443/workflows/3ebadb794f6641e0b7f4fda131cdfb0b/runs/08585236861638480597867166179CU104/contents/TriggerInputs?api-version=2016-06-01&se=2023-03-04T14%3A00%3A00.0000000Z&sp=%2Fruns%2F08585236861638480597867166179CU104%2Fcontents%2FTriggerInputs%2Fread&sv=1.0&sig=",
+          "contentVersion": "2v/VLXFrKV6JvwSdcN7aHg==",
+          "contentSize": 343,
+          "contentHash": {
+            "algorithm": "md5",
+            "value": "2v/VLXFrKV6JvwSdcN7aHg=="
+          }
+        },
+        "outputsLink": {
+          "uri": "https://prod-130.westeurope.logic.azure.com:443/workflows/3ebadb794f6641e0b7f4fda131cdfb0b/runs/08585236861638480597867166179CU104/contents/TriggerOutputs?api-version=2016-06-01&se=2023-03-04T14%3A00%3A00.0000000Z&sp=%2Fruns%2F08585236861638480597867166179CU104%2Fcontents%2FTriggerOutputs%2Fread&sv=1.0&sig=",
+          "contentVersion": "AHZEeWNlQ0bLe48yDmpzrQ==",
+          "contentSize": 3478,
+          "contentHash": {
+            "algorithm": "md5",
+            "value": "AHZEeWNlQ0bLe48yDmpzrQ=="
+          }
+        },
+        "startTime": "2023-03-04T09:05:21.6192576Z",
+        "endTime": "2023-03-04T09:05:21.7442626Z",
+        "scheduledTime": "2023-03-04T09:05:21.573561Z",
+        "originHistoryName": "08585236861638480598867166179CU131",
+        "correlation": {
+          "clientTrackingId": "08585236861638480598867166179CU131"
+        },
+        "code": "OK",
+        "status": "Succeeded"
+      }
+    },
+    "startTime": "2023-03-04T09:05:21.8066368Z",
+    "endTime": "2023-03-04T09:05:22.5880202Z",
+    "status": "Succeeded",
+    "triggerName": "When_an_email_is_flagged_(V4)",
+    "triggerInformation": {
+      "from": "john@contoso.com",
+      "toRecipients": "doe@contoso.com",
+      "subject": "Dummy email",
+      "body": "<html><head>\r\\\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\"></head><body><p>This is dummy content</p></body></html>",
+      "importance": "normal",
+      "bodyPreview": "This is dummy content",
+      "hasAttachments": false,
+      "id": "AAMkADgzN2Q1NThiLTI0NjYtNGIxYS05MDdjLTg1OWQxNzgwZGM2ZgBGAAAAAAC6jQfUzacTSIHqMw2yacnUBwBiOC8xvYmdT6G2E_hLMK5kAAAAAAEMAABiOC8xvYmdT6G2E_hLMK5kAALUqy81AAA=",
+      "internetMessageId": "<DB7PR03MB5018879914324FC65695809FE1AD9@DB7PR03MB5018.eurprd03.prod.outlook.com>",
+      "conversationId": "AAQkADgzN2Q1NThiLTI0NjYtNGIxYS05MDdjLTg1OWQxNzgwZGM2ZgAQAMqP9zsK8a1CnIYEgHclLTk=",
+      "receivedDateTime": "2023-03-01T15:06:57+00:00",
+      "isRead": false,
+      "attachments": [],
+      "isHtml": true
+    },
+    "actions": {
+      "Compose": {
+        "input": "Test",
+        "inputsLink": {
+          "uri": "https://prod-255.westeurope.logic.azure.com:443/workflows/88b5146587d144ea85efb15683c4e58f/runs/08586652586741142222645090602CU35/actions/Compose/contents/ActionInputs?api-version=2016-06-01&se=2023-12-14T19%3A00%3A00.0000000Z&sp=%2Fruns%2F08586652586741142222645090602CU35%2Factions%2FCompose%2Fcontents%2FActionInputs%2Fread&sv=1.0&sig=wYD6bMHjdoOawYAMTHqpmyILowLKRCkFEfsNxi1NFzw",
+          "contentVersion": "test==",
+          "contentSize": 6,
+          "contentHash": {
+            "algorithm": "md5",
+            "value": "test=="
+          }
+        },
+        "output": "Test",
+        "outputsLink": {
+          "uri": "https://prod-255.westeurope.logic.azure.com:443/workflows/88b5146587d144ea85efb15683c4e58f/runs/08586652586741142222645090602CU35/actions/Compose/contents/ActionOutputs?api-version=2016-06-01&se=2023-12-14T19%3A00%3A00.0000000Z&sp=%2Fruns%2F08586652586741142222645090602CU35%2Factions%2FCompose%2Fcontents%2FActionOutputs%2Fread&sv=1.0&sig=KoI4_RAEVNFUgymktOFxvfb5mCoIKR2WCYGwexjD7kY",
+          "contentVersion": "test==",
+          "contentSize": 6,
+          "contentHash": {
+            "algorithm": "md5",
+            "value": "test=="
+          }
+        },
+        "startTime": "2023-11-17T21:06:14.466889Z",
+        "endTime": "2023-11-17T21:06:14.4676104Z",
+        "correlation": {
+          "actionTrackingId": "dabed750-0ec4-4c34-98f5-cc3695e0811e",
+          "clientTrackingId": "08585013686846794051719443325CU251",
+          "clientKeywords": [
+            "resubmitFlow"
+          ]
+        },
+        "status": "Succeeded",
+        "code": "OK"
+      }
+    }
+  }
+  ```
+  </TabItem>
+</Tabs>

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/group/group-member-add.mdx

@@ -33,18 +33,24 @@ m365 spo group member add [options]
 `--userIds [userIds]`
 : The user Id of the user to add as a member. (Id of the site user, for example: 14) If multiple users need to be added, the Ids have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
 
+`--entraGroupIds [entraGroupIds]`
+: The object Id of the Entra group to add as a member. If multiple groups need to be added, the Ids have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds`, `entraGroupIds`, `aadGroupNames`, or `entraGroupNames`.
+
 `--aadGroupIds [aadGroupIds]`
-: The object Id of the Azure AD group to add as a member. If multiple groups need to be added, the Ids have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
+: (deprecated. Use `entraGroupIds` instead) The object Id of the Azure AD group to add as a member. If multiple groups need to be added, the Ids have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds`, `entraGroupIds`, `aadGroupNames`, or `entraGroupNames`.
+
+`--entraGroupNames [entraGroupNames]`
+: The name of the Entra group to add as a member. If multiple groups need to be added, they have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds`, `entraGroupIds`, `aadGroupNames`, or `entraGroupNames`.
 
 `--aadGroupNames [aadGroupNames]`
-: The name of the Azure AD group to add as a member. If multiple groups need to be added, they have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames`.
+: (deprecated. Use `entraGroupNames` instead) The name of the Azure AD group to add as a member. If multiple groups need to be added, they have to be comma-separated. Specify either `userIds`, `userNames`, `emails`, `aadGroupIds`, `entraGroupIds`, `aadGroupNames`, or `entraGroupNames`.
 ```
 
 <Global />
 
 ## Remarks
 
-For the `userIds`, `userNames`, `emails`, `aadGroupIds` or `aadGroupNames` options you can specify multiple values by separating them with a comma. If one of the specified entries is not valid, the command will fail with an error message showing the list of invalid values.
+For the `userIds`, `userNames`, `emails`, `aadGroupIds`, `entraGroupIds`, `aadGroupNames`, or `entraGroupNames` options you can specify multiple values by separating them with a comma. If one of the specified entries is not valid, the command will fail with an error message showing the list of invalid values.
 
 ## Examples
 
@@ -84,11 +90,17 @@ Add multiple users with the userIds parameter to a SharePoint group with the gro
 m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --userIds "5,12"
 ```
 
-Add multiple users with the aadGroupNames parameter to a SharePoint group with the groupId parameter 
+Add multiple users with the entraGroupIds parameter to a SharePoint group with the groupId parameter.
+  
+```sh 
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --entraGroupIds "f2fb2f10-cfd2-4054-8ffd-64533657a5ab,3e86049e-89e6-4c27-bccb-d7549f0bbd06"
+```
+
+Add multiple users with the entraGroupNames parameter to a SharePoint group with the groupId parameter.
   
- ```sh 
- m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --aadGroupNames "Azure group one, Azure group two" 
- ``` 
+```sh 
+m365 spo group member add --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --entraGroupNames "Azure group one, Azure group two" 
+```
 
 ## Response
 

package/docs/docs/cmd/spo/group/group-member-remove.mdx

@@ -31,11 +31,17 @@ m365 spo group member remove [options]
 `--userId [userId]`
 : The user Id (Id of the site user, eg. 14) of the user to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId` or `aadGroupName`.
 
+`--entraGroupId [entraGroupId]`
+: The object Id of the Entra group to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId`, `entraGroupId`, `aadGroupName`, or `entraGroupName`.
+
 `--aadGroupId [aadGroupId]`
-: The object Id of the Azure AD group to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId` or `aadGroupName`.
+: (deprecated. Use `entraGroupId` instead) The object Id of the Azure AD group to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId`, `entraGroupId`, `aadGroupName`, or `entraGroupName`.
+
+`--entraGroupName [entraGroupName]`
+: The name of the Entra group to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId`, `entraGroupId`, `aadGroupName`, or `entraGroupName`.
 
 `--aadGroupName [aadGroupName]`
-: The name of the Azure AD group to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId` or `aadGroupName`.
+: (deprecated. Use `entraGroupName` instead) The name of the Azure AD group to remove as a member. Specify either `userName`, `email`, `userId`, `aadGroupId`, `entraGroupId`, `aadGroupName`, or `entraGroupName`.
 ```
 
 <Global />
@@ -60,16 +66,16 @@ Remove a user from a SharePoint group by email.
 m365 spo group member remove --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Site A Visitors" --userId 14
 ```
 
-Remove an Azure AD group from a SharePoint group based on the Azure AD group name on a given web.
+Remove an Entra group from a SharePoint group based on the Entra group name on a given web.
 
 ```sh
-m365 spo group member remove --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --aadGroupName "Azure AD Security Group"
+m365 spo group member remove --webUrl https://contoso.sharepoint.com/sites/SiteA --groupId 5 --entraGroupName "Azure AD Security Group"
 ```
 
-Remove an Azure AD group from a SharePoint group based on the Azure AD group ID on a given web.
+Remove an Entra group from a SharePoint group based on the Entra group ID on a given web.
 
 ```sh
-m365 spo group member remove --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Site A Visitors" --aadGroupId "5786b8e8-c495-4734-b345-756733960730"
+m365 spo group member remove --webUrl https://contoso.sharepoint.com/sites/SiteA --groupName "Site A Visitors" --entraGroupId "5786b8e8-c495-4734-b345-756733960730"
 ```
 
 ## Response

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.