@pnp/cli-microsoft365 7.5.0-beta.d4d820f → 7.6.0-beta.443bfd8

package/docs/docs/cmd/purview/threatassessment/threatassessment-list.mdx

@@ -0,0 +1,110 @@
+import Global from '/docs/cmd/_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# purview threatassessment list
+
+Get a list of threat assessments
+
+## Usage
+
+```sh
+m365 purview threatassessment list [options]
+```
+
+## Options
+
+```md definition-list
+`-t, --type [type]`
+: The type of threat assessment to retrieve. Allowed values are `mail`, `file`, `emailFile` and `url`.
+```
+
+<Global />
+
+## Examples
+
+Get a list of threat assessments
+
+```sh
+m365 purview threatassessment list
+```
+
+Get a list of threat assessments of type _mail_
+
+```sh
+m365 purview threatassessment list --type mail
+```
+
+## Response
+
+<Tabs>
+  <TabItem value="JSON">
+
+  ```json
+  [
+    {
+      "type": "mail",
+      "id": "49c5ef5b-1f65-444a-e6b9-08d772ea2059",
+      "createdDateTime": "2019-11-27T03:30:18.6890937Z",
+      "contentType": "mail",
+      "expectedAssessment": "block",
+      "category": "spam",
+      "status": "pending",
+      "requestSource": "administrator",
+      "recipientEmail": "john@contoso.onmicrosoft.com",
+      "destinationRoutingReason": "notJunk",
+      "messageUri": "https://graph.microsoft.com/v1.0/users/c52ce8db-3e4b-4181-93c4-7d6b6bffaf60/messages/AAMkADU3MWUxOTU0LWNlOTEt=",
+      "createdBy": {
+        "user": {
+          "id": "c52ce8db-3e4b-4181-93c4-7d6b6bffaf60",
+          "displayName": "John Doe"
+        }
+      }
+    }
+  ];
+  ```
+
+  </TabItem>
+  <TabItem value="Text">
+
+  ```text
+  id                                    type  category
+  ------------------------------------  -----------  --------
+  49c5ef5b-1f65-444a-e6b9-08d772ea2059  mail         spam
+  ```
+
+  </TabItem>
+  <TabItem value="CSV">
+
+  ```csv
+  id,type,category
+  49c5ef5b-1f65-444a-e6b9-08d772ea2059,mail,spam
+  ```
+
+  </TabItem>
+  <TabItem value="Markdown">
+
+  ```md
+  # purview threatassessment list
+
+  Date: 16/2/2023
+
+  ## a47e428c-a7bd-4cf2-f061-08db0f58b736
+
+  Property | Value
+  ---------|-------
+  type | mail
+  id | 49c5ef5b-1f65-444a-e6b9-08d772ea2059
+  createdDateTime | 2019-11-27T03:30:18.6890937Z
+  contentType | mail
+  expectedAssessment | block
+  category | spam
+  status | pending
+  recipientEmail | john@contoso.onmicrosoft.com
+  destinationRoutingReason | notJunk
+  messageUri | https://graph.microsoft.com/v1.0/users/c52ce8db-3e4b-4181-93c4-7d6b6bffaf60/messages/AAMkADU3MWUxOTU0LWNlOTEt=
+  createdBy | {"user":{"id":"c52ce8db-3e4b-4181-93c4-7d6b6bffaf60","displayName":"John Doe"}}
+  ```
+
+  </TabItem>
+</Tabs>

package/docs/docs/cmd/setup.mdx

@@ -90,3 +90,7 @@ Configure CLI for Microsoft for use in scripts without prompting for additional
 ```sh
 m365 setup --scripting
 ```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/spfx/project/project-azuredevops-pipeline-add.mdx

@@ -0,0 +1,87 @@
+import Global from '/docs/cmd/_global.mdx';
+
+# spfx project azuredevops pipeline add
+
+Adds a Azure DevOps Pipeline for a SharePoint Framework project
+
+## Usage
+
+```sh
+m365 spfx project azuredevops pipeline add [options]
+```
+
+## Options
+
+```md definition-list
+`-n, --name [name]`
+: Name of the pipeline run that will be created. If none is specified a default name generated by Azure DevOps will be used
+
+`-b, --branchName [branchName]`
+: Specify the branch name which should trigger the workflow on push. If none is specified a default will be used which is 'main'
+
+`-l, --loginMethod [loginMethod]`
+: Specify the login method used for the login action. Possible options are: `user`, `application`. Default `application`
+
+`-s, --scope [scope]`
+: Scope of the app catalog: `tenant`, `sitecollection`. Default is `tenant`
+
+`-u, --siteUrl [siteUrl]`
+: The URL of the site collection where the solution package will be added. Required if scope is set to `sitecollection`
+
+`--skipFeatureDeployment`
+: When specified the app will be added to all sites. When deployed to the site app catalog it will be added to all sub-sites of that site.
+```
+
+<Global />
+
+## Remarks
+
+The `spfx project azuredevops pipeline add` will create a workflow .yml file in the `.azuredevops/pipelines` directory in your project. If such directory does not exist the command will automatically create it.
+
+The command will not create the Azure DevOps pipeline. You will need to manually create it in Azure DevOps. The command will only create the workflow file which you can then push to your repo and create a new yaml pipline based on it.
+
+For the `application` login method the command does not register an Entra application nor does it create the required certificate. In order to proceed, obtain (create) a self-signed certificate and register a new Entra application with certificate authentication. After that you will need to fill the following variables, or what is more preferable, create a dedicated variable group to store those properties:
+
+- `CertificateBase64Encoded` - base 64 encoded certificate. Use either `CertificateBase64Encoded` or `CertificateSecureFileId` but not both
+- `CertificateSecureFileId` - id of a certificate file in the secure files section of the DevOps library. `.pfx` file. Use either `CertificateBase64Encoded` or `CertificateSecureFileId` but not both
+- `CertificatePassword` - certificate password. This applies only if the certificate is encoded which is the recommended approach
+- `EntraAppId` - client id of the registered Entra application
+
+This use case is perfect in a production context as it does not create any dependencies on an account
+
+For the `user` login method you will need to fill the following variables, or what is more preferable, create a dedicated variable group to store those properties:
+
+- `UserName` - user email
+- `Password` - password
+
+This method is perfect to test your workflow, in a dev context, for personal usage. It will not work for accounts with MFA.
+
+:::info
+
+Run this command in the SPFx solution folder.
+
+:::
+    
+## Examples
+
+Adds an Azure DevOps Pipeline for a SharePoint Framework project triggered on push to main
+
+```sh
+m365 spfx project azuredevops pipeline add
+```
+
+Adds an Azure DevOps Pipeline for a SharePoint Framework project with `user` login method triggered on push to main
+
+```sh
+m365 spfx project azuredevops pipeline add --loginMethod "user"
+```
+
+Adds an Azure DevOps Pipeline for a SharePoint Framework project with deployment to a site collection app catalog
+
+```sh
+m365 spfx project azuredevops pipeline add --scope "sitecollection" --siteUrl "https://some.sharepoint.com/sites/someSite"
+```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/spo/list/list-webhook-set.mdx

@@ -64,6 +64,6 @@ Update the notification url and clientState of a webhook with a specific ID atta
 m365 spo list webhook set --webUrl https://contoso.sharepoint.com/sites/ninja --listUrl '/sites/ninja/Documents' --id cc27a922-8224-4296-90a5-ebbc54da2e81 --notificationUrl https://contoso-functions.azurewebsites.net/webhook --expirationDateTime 2019-03-02 --clientState 'My client state'
 ```
 
-## Respone
+## Response
 
 The command won't return a response on success.

package/docs/docs/cmd/spo/spo-search.mdx

@@ -25,7 +25,7 @@ m365 spo search [options]
 : The web against which we want to execute the query. If the parameter is not defined, the query is executed against the web that's used when logging in to the SPO environment.
 
 `--allResults`
-: Set, to get all results of the search query, instead of the number specified by the `rowlimit` (default: 10)
+: Set, to get all results of the search query in batches of 500.
 
 `--rowLimit [rowLimit]`
 : The number of rows to be returned. When the `allResults` option is used, the specified value will define the size of retrieved batches
@@ -55,7 +55,7 @@ m365 spo search [options]
 : The ID of the ranking model to use for the query.
 
 `--startRow [startRow]`
-: The first row that is included in the search results that are returned. You use this parameter when you want to implement paging for search results.
+: The first row that is included in the search results that are returned. You use this parameter when you want to implement manual paging for search results.
 
 `--properties [properties]`
 : Additional properties for the query.
@@ -90,6 +90,10 @@ m365 spo search [options]
 
 <Global />
 
+## Remarks
+
+When using the `--allResults` option, you cannot use the `--startRow` option. Only use `--startRow` for manual paging purposes.
+
 ## Examples
 
 Execute search query to retrieve all Document Sets (ContentTypeId = _0x0120D520_) for the English locale

package/docs/docs/cmd/spo/theme/theme-set.mdx

@@ -76,13 +76,25 @@ To use this command you have to have permissions to access the tenant admin site
 Add or update a theme from a theme JSON file
 
 ```sh
-m365 spo theme set --name Contoso-Blue --theme @/Users/rjesh/themes/contoso-blue.json
+m365 spo theme set --name Contoso-Blue --theme @/Users/user/themes/contoso-blue.json
 ```
 
 Add or update an inverted theme from a theme JSON file
 
 ```sh
-m365 spo theme set --name Contoso-Blue --theme @/Users/rjesh/themes/contoso-blue.json --isInverted
+m365 spo theme set --name Contoso-Blue --theme @/Users/user/themes/contoso-blue.json --isInverted
+```
+
+Add or update a theme from inline JSON
+
+```sh
+m365 spo theme set --name Contoso-Red --theme '{"themePrimary":"#d81e05","themeLighterAlt":"#fdf5f4","themeLighter":"#f9d6d2","themeLight":"#f4b4ac","themeTertiary":"#e87060","themeSecondary":"#dd351e","themeDarkAlt":"#c31a04","themeDark":"#a51603","themeDarker":"#791002","neutralLighterAlt":"#eeeeee","neutralLighter":"#f5f5f5","neutralLight":"#e1e1e1","neutralQuaternaryAlt":"#d1d1d1","neutralQuaternary":"#c8c8c8","neutralTertiaryAlt":"#c0c0c0","neutralTertiary":"#c2c2c2","neutralSecondary":"#858585","neutralPrimaryAlt":"#4b4b4b","neutralPrimary":"#333333","neutralDark":"#272727","black":"#1d1d1d","white":"#f5f5f5"}'
+```
+
+Add or update an inverted theme from inline JSON
+
+```sh
+m365 spo theme set --name Contoso-Red --theme '{"themePrimary":"#d81e05","themeLighterAlt":"#fdf5f4","themeLighter":"#f9d6d2","themeLight":"#f4b4ac","themeTertiary":"#e87060","themeSecondary":"#dd351e","themeDarkAlt":"#c31a04","themeDark":"#a51603","themeDarker":"#791002","neutralLighterAlt":"#eeeeee","neutralLighter":"#f5f5f5","neutralLight":"#e1e1e1","neutralQuaternaryAlt":"#d1d1d1","neutralQuaternary":"#c8c8c8","neutralTertiaryAlt":"#c0c0c0","neutralTertiary":"#c2c2c2","neutralSecondary":"#858585","neutralPrimaryAlt":"#4b4b4b","neutralPrimary":"#333333","neutralDark":"#272727","black":"#1d1d1d","white":"#f5f5f5"}' --isInverted
 ```
 
 ## Response

package/docs/docs/cmd/spo/user/user-remove.mdx

@@ -14,13 +14,25 @@ m365 spo user remove [options]
 
 ```md definition-list
 `-u, --webUrl <webUrl>`
-: URL of the web to remove user
+: URL of the web to remove user.
 
 `--id [id]`
-: ID of the user to remove from web
+: ID of the user to remove from web. Use either `id` or `loginName` or `email`, `userName`, `entraGroupId`, or `entraGroupName`, but not all.
 
 `--loginName [loginName]`
-: Login name of the site user to remove
+: Login name of the user to remove from web. Use either `id` or `loginName` or `email`, `userName`, `entraGroupId`, or `entraGroupName`, but not all.
+
+`--userName [userName]`
+: User name of the user to remove from web. Use either `id` or `loginName` or `email`, `userName`, `entraGroupId`, or `entraGroupName`, but not all.
+
+`--email [email]`
+: Email of the user to remove from web. Use either `id` or `loginName` or `email`, `userName`, `entraGroupId`, or `entraGroupName`, but not all.
+
+`--entraGroupId [entraGroupId]`
+: Object ID of the Entra group ID to remove. Use either `id` or `loginName` or `email`, `userName`, `entraGroupId`, or `entraGroupName`, but not all.
+
+`--entraGroupName [entraGroupName]`
+: Name of the Entra group to remove. Use either `id` or `loginName` or `email`, `userName`, `entraGroupId`, or `entraGroupName`, but not all.
 
 `-f, --force`
 : Do not prompt for confirmation before removing user from web
@@ -28,24 +40,43 @@ m365 spo user remove [options]
 
 <Global />
 
-## Remarks
-
-Use either `id` or `loginName`, but not both
-
 ## Examples
 
-Removes user with id _10_ from a web without prompting for confirmation
+Removes user by id from a web without prompting for confirmation
 
 ```sh
 m365 spo user remove --webUrl "https://contoso.sharepoint.com/sites/HR" --id 10 --force
 ```
 
-Removes user with login name _i:0#.f|membership|john.doe@mytenant.onmicrosoft.com_ from a web
+Removes user by loginName from a web
 
 ```sh
 m365 spo user remove --webUrl "https://contoso.sharepoint.com/sites/HR" --loginName "i:0#.f|membership|john.doe@mytenant.onmicrosoft.com"
 ```
 
+Removes user by userName from a web
+
+```sh
+m365 spo user remove --webUrl "https://contoso.sharepoint.com/sites/HR" --userName "john.doe_hotmail.com#ext#@mytenant.onmicrosoft.com"
+```
+
+Removes user by email from a web
+
+```sh
+m365 spo user remove --webUrl "https://contoso.sharepoint.com/sites/HR" --email "john.doe@mytenant.onmicrosoft.com"
+```
+
+Removes user by entraGroupId from a web
+
+```sh
+m365 spo user remove --webUrl "https://contoso.sharepoint.com/sites/HR" --entraGroupId f832a493-de73-4fef-87ed-8c6fffd91be6
+```
+
+Removes user by entraGroupName from a web
+
+```sh
+m365 spo user remove --webUrl _https://contoso.sharepoint.com/sites/HR_ --entraGroupName "Test Members"
+```
 ## Response
 
 The command won't return a response on success.

package/docs/docs/cmd/{yammer/group/group-list.mdx → viva/engage/engage-group-list.mdx}

@@ -2,14 +2,14 @@ import Global from '/docs/cmd/_global.mdx';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# yammer group list
+# viva engage group list
 
-Returns the list of groups in a Yammer network or the groups for a specific user
+Returns the list of groups in a Viva Engage network or the groups for a specific user
 
 ## Usage
 
 ```sh
-m365 yammer group list [options]
+m365 viva engage group list [options]
 ```
 
 ## Options
@@ -28,34 +28,34 @@ m365 yammer group list [options]
 
 :::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.
+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 Viva Engage API. To do this, execute the `cli consent --service VivaEngage` command.
 
 :::
 
 ## Examples
 
-Returns all Yammer network groups
+Returns all Viva Engage network groups
 
 ```sh
-m365 yammer group list
+m365 viva engage group list
 ```
 
-Returns all Yammer network groups for the user with the ID `5611239081`
+Returns all Viva Engage network groups for the user with the ID `5611239081`
 
 ```sh
-m365 yammer group list --userId 5611239081
+m365 viva engage group list --userId 5611239081
 ```
 
-Returns the first 10 Yammer network groups
+Returns the first 10 Viva Engage network groups
 
 ```sh
-m365 yammer group list --limit 10
+m365 viva engage group list --limit 10
 ```
 
-Returns the first 10 Yammer network groups for the user with the ID `5611239081`
+Returns the first 10 Viva Engage network groups for the user with the ID `5611239081`
 
 ```sh
-m365 yammer group list --userId 5611239081 --limit 10
+m365 viva engage group list --userId 5611239081 --limit 10
 ```
 
 ## Response
@@ -130,7 +130,7 @@ m365 yammer group list --userId 5611239081 --limit 10
   <TabItem value="Markdown">
 
   ```md
-  # yammer group list --limit "1"
+  # viva engage group list --limit "1"
 
   Date: 2023-05-16
 

package/docs/docs/cmd/{yammer/group/group-user-add.mdx → viva/engage/engage-group-user-add.mdx}

@@ -1,13 +1,13 @@
 import Global from '/docs/cmd/_global.mdx';
 
-# yammer group user add
+# viva engage group user add
 
-Adds a user to a Yammer Group
+Adds a user to a Viva Engage Group
 
 ## Usage
 
 ```sh
-m365 yammer group user add [options]
+m365 viva engage group user add [options]
 ```
 
 ## Options
@@ -29,7 +29,7 @@ m365 yammer group user add [options]
 
 :::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.
+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 Viva Engage API. To do this, execute the `cli consent --service VivaEngage` command.
 
 :::
 
@@ -40,19 +40,19 @@ If the specified user is not a member of the network, the command will return an
 Adds the current user to the group with the ID `5611239081`
 
 ```sh
-m365 yammer group user add --groupId 5611239081
+m365 viva engage group user add --groupId 5611239081
 ```
 
 Adds the user with ID `66622349` to the group with the ID `5611239081`
 
 ```sh
-m365 yammer group user add --groupId 5611239081 --id 66622349
+m365 viva engage group user add --groupId 5611239081 --id 66622349
 ```
 
 Adds the user with e-mail to the group with ID `5611239081`
 
 ```sh
-m365 yammer group user add --groupId 5611239081 --email suzy@contoso.com
+m365 viva engage group user add --groupId 5611239081 --email suzy@contoso.com
 ```
 
 ## Response

package/docs/docs/cmd/{yammer/group/group-user-remove.mdx → viva/engage/engage-group-user-remove.mdx}

@@ -1,26 +1,26 @@
 import Global from '/docs/cmd/_global.mdx';
 
-# yammer group user remove
+# viva engage group user remove
 
-Removes a user from a Yammer group
+Removes a user from a Viva Engage group
 
 ## Usage
 
 ```sh
-m365 yammer group user remove [options]
+m365 viva engage group user remove [options]
 ```
 
 ## Options
 
 ```md definition-list
 `--groupId <groupId>`
-: The ID of the Yammer group
+: The ID of the Viva Engage group.
 
 `--id [id]`
-: ID of the user to remove from the group. If not specified, removes the current user
+: ID of the user to remove from the group. If not specified, removes the current user.
 
 `-f, --force`
-: Don't prompt for confirmation before removing the user from the group
+: Don't prompt for confirmation.
 ```
 
 <Global />
@@ -29,7 +29,7 @@ m365 yammer group user remove [options]
 
 :::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.
+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 Viva Engage API. To do this, execute the `cli consent --service VivaEngage` command.
 
 :::
 
@@ -38,19 +38,19 @@ In order to use this command, you need to grant the Azure AD application used by
 Remove the current user from the group with the ID `5611239081`
 
 ```sh
-m365 yammer group user remove --groupId 5611239081
+m365 viva engage group user remove --groupId 5611239081
 ```
 
 Remove the user with the ID `66622349` from the group with the ID `5611239081`
 
 ```sh
-m365 yammer group user remove --groupId 5611239081 --id 66622349
+m365 viva engage group user remove --groupId 5611239081 --id 66622349
 ```
 
 Remove the user with the ID `66622349` from the group with the ID `5611239081` without asking for confirmation
 
 ```sh
-m365 yammer group user remove --groupId 5611239081 --id 66622349 --force
+m365 viva engage group user remove --groupId 5611239081 --id 66622349 --force
 ```
 
 ## Response

package/docs/docs/cmd/{yammer/message/message-add.mdx → viva/engage/engage-message-add.mdx}

@@ -2,14 +2,14 @@ import Global from '/docs/cmd/_global.mdx';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# yammer message add
+# viva engage message add
 
-Posts a Yammer network message on behalf of the current user
+Posts a Viva Engage network message on behalf of the current user
 
 ## Usage
 
 ```sh
-m365 yammer message add [options]
+m365 viva engage message add [options]
 ```
 
 ## Options
@@ -25,7 +25,7 @@ m365 yammer message add [options]
 : The message ID this message is in reply to. If this is set then groupId and networkId are inferred from it. You must either specify `groupId`, `repliedToId`, or `directToUserIds` to send the message
 
 `-d, --directToUserIds [directToUserIds]`
-: Send a private message to one or more users, specified by ID. Alternatively, you can use the Yammer network e-mail addresses instead of the IDs. You must either specify `groupId`, `repliedToId`, or `directToUserIds` to send the message
+: Send a private message to one or more users, specified by ID. Alternatively, you can use the Viva Engage network e-mail addresses instead of the IDs. You must either specify `groupId`, `repliedToId`, or `directToUserIds` to send the message
 
 `--networkId [networkId]`
 : Specify the network to post a message
@@ -37,7 +37,7 @@ m365 yammer message add [options]
 
 :::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.
+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 Viva Engage API. To do this, execute the `cli consent --service VivaEngage` command.
 
 :::
 
@@ -46,37 +46,37 @@ In order to use this command, you need to grant the Azure AD application used by
 Replies to a message with the ID 1231231231
 
 ```sh
-m365 yammer message add --body "Hello everyone!" --repliedToId 1231231231
+m365 viva engage message add --body "Hello everyone!" --repliedToId 1231231231
 ```
 
 Sends a private conversation to the user with the ID 1231231231
 
 ```sh
-m365 yammer message add --body "Hello everyone!" --directToUserIds 1231231231
+m365 viva engage message add --body "Hello everyone!" --directToUserIds 1231231231
 ```
 
 Sends a private conversation to multiple users by ID
 
 ```sh
-m365 yammer message add --body "Hello everyone!" --directToUserIds "1231231231,1121312"
+m365 viva engage message add --body "Hello everyone!" --directToUserIds "1231231231,1121312"
 ```
 
 Sends a private conversation to the user with several e-mail addresses
 
 ```sh
-m365 yammer message add --body "Hello everyone!" --directToUserIds "pl@nubo.eu,sc@nubo.eu"
+m365 viva engage message add --body "Hello everyone!" --directToUserIds "pl@nubo.eu,sc@nubo.eu"
 ```
 
 Posts a message to the group with the ID 12312312312
 
 ```sh
-m365 yammer message add --body "Hello everyone!" --groupId 12312312312
+m365 viva engage message add --body "Hello everyone!" --groupId 12312312312
 ```
 
 Posts a message to the group with the ID 12312312312 in the network 11112312
 
 ```sh
-m365 yammer message add --body "Hello everyone!" --groupId 12312312312 --networkId 11112312
+m365 viva engage message add --body "Hello everyone!" --groupId 12312312312 --networkId 11112312
 ```
 
 ## Response
@@ -141,7 +141,7 @@ m365 yammer message add --body "Hello everyone!" --groupId 12312312312 --network
   <TabItem value="Markdown">
 
   ```md
-  # yammer message add --body "Hello everyone!" --groupId "123412865024"
+  # viva engage message add --body "Hello everyone!" --groupId "123412865024"
 
   Date: 2023-05-16
 
@@ -172,4 +172,3 @@ m365 yammer message add --body "Hello everyone!" --groupId 12312312312 --network
 
   </TabItem>
 </Tabs>
-