@pnp/cli-microsoft365 7.3.0-beta.16c6462 → 7.3.0-beta.6062919

package/docs/docs/cmd/spo/report/report-activitypages.mdx

@@ -17,9 +17,6 @@ m365 spo report activitypages [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-activityusercounts.mdx

@@ -17,9 +17,6 @@ m365 spo report activityusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-activityuserdetail.mdx

@@ -20,9 +20,6 @@ m365 spo report activityuserdetail [options]
 
 `-p, --period [period]`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`. Specify either `date` or `period`, but not both.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams device usage by user report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagedetail.mdx

@@ -20,9 +20,6 @@ m365 spo report siteusagedetail [options]
 
 `-p, --period [period]`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`. Specify either `date` or `period`, but not both.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagefilecounts.mdx

@@ -17,9 +17,6 @@ m365 spo report siteusagefilecounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagepages.mdx

@@ -17,9 +17,6 @@ m365 spo report siteusagepages [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagesitecounts.mdx

@@ -17,9 +17,6 @@ m365 spo report siteusagesitecounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/report/report-siteusagestorage.mdx

@@ -17,9 +17,6 @@ m365 spo report siteusagestorage [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/spo/site/site-groupify.mdx

@@ -41,7 +41,7 @@ m365 spo site groupify [options]
 
 ## Remarks
 
-:::caution
+:::warning
 
 This command is based on a SharePoint API that is currently in preview and is subject to change once the API reached general availability.
 

package/docs/docs/cmd/spo/site/site-recyclebinitem-clear.mdx

@@ -27,7 +27,7 @@ m365 spo site recyclebinitem clear [options]
 
 ## Remarks
 
-:::caution
+:::warning
 
 Items in the recycle bin will be permanently removed without the ability to restore them.
 

package/docs/docs/cmd/spo/site/site-recyclebinitem-remove.mdx

@@ -27,7 +27,7 @@ m365 spo site recyclebinitem remove [options]
 
 ## Remarks
 
-:::caution
+:::warning
 
 Items in the recycle bin will be permanently removed without the ability to restore them.
 

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"}'`.
 
-:::caution 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"}'`.
 
-:::caution 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"}'`.
 
-:::caution 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
 
-:::caution 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
 
-:::caution 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
 
-:::caution    
+:::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
 
-:::caution 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/meeting/meeting-add.mdx

@@ -0,0 +1,283 @@
+import Global from '/docs/cmd/_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# teams meeting add
+
+Create a new online meeting
+
+## Usage
+
+```sh
+m365 teams meeting add [options]
+```
+
+## Options
+
+```md definition-list
+`-s, --startTime [startTime]`
+: The start time of the meeting. If not specified, the start time will be set to the current time.
+
+`-e, --endTime [endTime]`
+: The end time of the meeting. If not specified, the end time will be set to one hour after the start time.
+
+`--subject [subject]`
+: The subject of the meeting.
+
+`-p, --participantUserNames [participantUserNames]`
+: A comma-separated list of participant UPNs.
+
+`--organizerEmail [organizerEmail]`
+: The organizer's email address.
+
+`-r, --recordAutomatically`
+: When using this flag, the meeting will be recorded automatically.
+```
+
+<Global />
+
+## Remarks
+
+:::info
+
+This command creates a standalone meeting that is not associated with any event on the user's calendar; therefore, meetings created via this command will not show on the user's calendar.
+
+:::
+
+To create an online meeting for a specific organizer, use the `organizerEmail` option along with app-only permissions. The application should have the _OnlineMeetings.ReadWrite.All_ permissions, and a special policy should be assigned to the user specified in the `organizerEmail` option. You can find more information on how to assign this policy to a user [here](https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy).
+
+## Examples
+
+Create a new online meeting for the currently logged-in user, starting immediately and ending after one hour. 
+
+```sh
+m365 teams meeting add
+```
+
+Create a new online meeting for the currently logged-in user, with a specified start date and a duration of one hour.
+
+```sh
+m365 teams meeting add --startTime "2025-09-21T13:30:00Z"
+```
+
+Create a new online meeting for the currently logged-in user, with specified end date the current date as the start date.
+
+```sh
+m365 teams meeting add --endTime "2025-09-21T23:55:00Z"
+```
+
+Create a new online meeting for the currently logged-in user, with specified start and end dates.
+
+```sh
+m365 teams meeting add --startTime "2025-09-21T13:30:00Z" --endTime "2025-09-21T23:55:00Z"
+```
+
+Create a new online meeting for the currently logged-in user, with a specified subject.
+
+```sh
+m365 teams meeting add --startTime "2025-09-21T13:30:00Z" --endTime "2025-09-21T23:55:00Z" --subject "Test Subject"
+```
+
+Create a new online meeting for the currently logged-in user, with a specified subject and a list of participantUserNames.
+
+```sh
+m365 teams meeting add --subject "Test Subject" --participantUserNames "john.doe@contoso.com,olga.manager@contoso.com"
+```
+
+Create a new online meeting for the currently logged-in user, with a specified subject, a list of participantUserNames, and automatic meeting recording.
+
+```sh
+m365 teams meeting add --subject "Test Subject" --participantUserNames "john.doe@contoso.com,olga.manager@contoso.com" --recordAutomatically
+```
+
+Create a new online meeting for a selected organizer, with a specified subject, a list of participantUserNames, and automatic meeting recording. This option is available for app-only permissions.
+
+```sh
+m365 teams meeting add --organizerEmail "john.doe@contoso.com" --subject "Test Subject" --participantUserNames "olga.manager@contoso.com" --recordAutomatically
+```
+
+## Response
+
+<Tabs>
+  <TabItem value="JSON">
+
+  ```json
+  {
+    "id": "abc",
+    "creationDateTime": "2023-07-25T19:29:32.033109Z",
+    "startDateTime": "2023-07-17T03:00:00Z",
+    "endDateTime": "2023-07-17T04:00:00Z",
+    "joinUrl": "https://teams.microsoft.com/l/meetup-join/abc",
+    "joinWebUrl": "https://teams.microsoft.com/l/meetup-join/abc",
+    "meetingCode": "12345",
+    "subject": "Subject",
+    "isBroadcast": false,
+    "autoAdmittedUsers": "unknownFutureValue",
+    "outerMeetingAutoAdmittedUsers": null,
+    "isEntryExitAnnounced": false,
+    "allowedPresenters": "everyone",
+    "allowMeetingChat": "enabled",
+    "shareMeetingChatHistoryDefault": "none",
+    "allowTeamworkReactions": true,
+    "allowAttendeeToEnableMic": true,
+    "allowAttendeeToEnableCamera": true,
+    "recordAutomatically": false,
+    "anonymizeIdentityForRoles": [],
+    "capabilities": [],
+    "videoTeleconferenceId": null,
+    "externalId": null,
+    "iCalUid": null,
+    "meetingType": null,
+    "allowParticipantsToChangeName": false,
+    "allowRecording": true,
+    "allowTranscription": true,
+    "meetingMigrationMode": null,
+    "broadcastSettings": null,
+    "audioConferencing": null,
+    "meetingInfo": null,
+    "participants": {
+      "organizer": {
+        "upn": "john.doe@contoso.com",
+        "role": "presenter",
+        "identity": {
+          "application": null,
+          "device": null,
+          "user": {
+            "id": "12345678-1234-1234-1234-12345678",
+            "displayName": null,
+            "tenantId": "12345678-1234-1234-1234-12345678",
+            "identityProvider": "AAD"
+          }
+        }
+      },
+      "attendees": [
+        {
+          "upn": "adele.vance@contoso.com",
+          "role": "attendee",
+          "identity": {
+            "application": null,
+            "device": null,
+            "user": {
+              "id": "12345678-1234-1234-1234-12345678",
+              "displayName": null,
+              "tenantId": "12345678-1234-1234-1234-12345678,
+              "identityProvider": "AAD"
+            }
+          }
+        }
+      ]
+    },
+    "lobbyBypassSettings": {
+      "scope": "unknownFutureValue",
+      "isDialInBypassEnabled": false
+    },
+    "joinMeetingIdSettings": {
+      "isPasscodeRequired": true,
+      "joinMeetingId": "12345",
+      "passcode": "123456"
+    },
+    "chatInfo": {
+      "threadId": "abc",
+      "messageId": "0",
+      "replyChainMessageId": null
+    },
+    "joinInformation": {
+      "content": "textContent",
+      "contentType": "html"
+    },
+    "watermarkProtection": {
+      "isEnabledForContentSharing": false,
+      "isEnabledForVideo": false
+    }
+  }
+  ```
+
+  </TabItem>
+  <TabItem value="Text">
+
+  ```text
+  allowAttendeeToEnableCamera   : true   
+  allowAttendeeToEnableMic      : true   
+  allowMeetingChat              : enabled
+  allowParticipantsToChangeName : false  
+  allowRecording                : true
+  allowTeamworkReactions        : true
+  allowTranscription            : true
+  allowedPresenters             : everyone
+  anonymizeIdentityForRoles     : []
+  audioConferencing             : null
+  autoAdmittedUsers             : everyoneInCompany
+  broadcastSettings             : null
+  capabilities                  : []
+  chatInfo                      : {"threadId":"19:meeting_ID@thread.v2","messageId":"0","replyChainMessageId":null}
+  chatRestrictions              : null
+  creationDateTime              : 2023-11-13T16:02:12.5012352Z
+  endDateTime                   : 2023-11-13T17:02:11.9711697Z
+  externalId                    : null
+  iCalUid                       : null
+  id                            : meetingID
+  isBroadcast                   : false
+  isEntryExitAnnounced          : true
+  joinInformation               : {"content":"data:text/html,htmlMessageTemplate","contentType":"html"}
+  joinMeetingIdSettings         : {"isPasscodeRequired":false,"joinMeetingId":"123456789012","passcode":null}
+  joinUrl                       : https://teams.microsoft.com/l/meetup-join/abc
+  joinWebUrl                    : https://teams.microsoft.com/l/meetup-join/abc
+  lobbyBypassSettings           : {"scope":"organization","isDialInBypassEnabled":false}
+  meetingCode                   : 123456789012
+  meetingInfo                   : null
+  meetingMigrationMode          : null
+  meetingType                   : null
+  outerMeetingAutoAdmittedUsers : null
+  participants                  : {"organizer":{"upn":"user@contoso.com","role":"presenter","identity":{"application":null,"device":null,"user":{"id":"12345678-1234-1234-1234-12345678","displayName":null,"tenantId":"12345678-1234-1234-1234-12345678","identityProvider":"AAD"}}},"attendees":[]}
+  recordAutomatically           : false
+  shareMeetingChatHistoryDefault: none
+  startDateTime                 : 2023-11-13T16:02:11.9711697Z
+  subject                       : null
+  videoTeleconferenceId         : null
+  watermarkProtection           : null
+  ```
+
+  </TabItem>
+  <TabItem value="CSV">
+
+  ```csv
+  id,creationDateTime,startDateTime,endDateTime,joinUrl,meetingCode,isBroadcast,autoAdmittedUsers,joinWebUrl,isEntryExitAnnounced,allowedPresenters,allowAttendeeToEnableMic,allowAttendeeToEnableCamera,allowMeetingChat,shareMeetingChatHistoryDefault,allowTeamworkReactions,recordAutomatically,allowParticipantsToChangeName,allowTranscription,allowRecording
+meetingId,2023-11-13T16:03:03.5669316Z,2023-11-13T16:03:03.2213499Z,2023-11-13T17:03:03.2213499Z,https://teams.microsoft.com/l/meetup-join/abc,123456789012,,everyoneInCompany,https://teams.microsoft.com/l/meetup-join/abc,1,everyone,1,1,enabled,none,1,,,1,1
+  ```
+
+  </TabItem>
+  <TabItem value="Markdown">
+
+  ```md
+  # teams meeting add 
+
+  Date: 13/11/2023
+
+  ## meetingId
+
+  Property | Value
+  ---------|-------
+  id | meetingId
+  creationDateTime | 2023-11-13T16:03:57.6531542Z
+  startDateTime | 2023-11-13T16:03:56.8464734Z
+  endDateTime | 2023-11-13T17:03:56.8464734Z
+  joinUrl | https://teams.microsoft.com/l/meetup-join/abc
+  meetingCode | 123456789012
+  isBroadcast | false
+  autoAdmittedUsers | everyoneInCompany
+  joinWebUrl | https://teams.microsoft.com/l/meetup-join/abc
+  isEntryExitAnnounced | true
+  allowedPresenters | everyone
+  allowAttendeeToEnableMic | true
+  allowAttendeeToEnableCamera | true
+  allowMeetingChat | enabled
+  shareMeetingChatHistoryDefault | none
+  allowTeamworkReactions | true
+  recordAutomatically | false
+  allowParticipantsToChangeName | false
+  allowTranscription | true
+  allowRecording | true
+  ```
+
+  </TabItem>
+</Tabs>

package/docs/docs/cmd/teams/meeting/meeting-transcript-list.mdx

@@ -46,13 +46,13 @@ m365 teams meeting transcript list --userName garthf@contoso.com --meetingId MSo
 
 ## Remarks
 
-:::caution
+:::warning
 
 This command is based on a Microsoft Graph API that is currently in preview and is subject to change once the API reached general availability.
 
 :::
 
-:::caution
+:::warning
 
 To run this command with application permissions, tenant administrators must create an application access policy and grant it to a user. This authorizes the app configured in the policy to fetch online meetings and/or online meeting artifacts on behalf of that user. For more details, click [here](https://learn.microsoft.com/graph/cloud-communication-online-meeting-application-access-policy).
 

package/docs/docs/cmd/teams/report/report-deviceusagedistributionusercounts.mdx

@@ -17,9 +17,6 @@ m365 teams report deviceusagedistributionusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams unique users by device type report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/teams/report/report-deviceusageusercounts.mdx

@@ -17,9 +17,6 @@ m365 teams report deviceusageusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams daily unique users by device type report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/teams/report/report-deviceusageuserdetail.mdx

@@ -20,9 +20,6 @@ m365 teams report deviceusageuserdetail [options]
 
 `-d, --date [date]`
 : The date for which you would like to view the users who performed any activity. Supported date format is `YYYY-MM-DD`.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams device usage by user report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/teams/report/report-useractivitycounts.mdx

@@ -17,9 +17,6 @@ m365 teams report useractivitycounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams activities by activity type report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/teams/report/report-useractivityusercounts.mdx

@@ -17,9 +17,6 @@ m365 teams report useractivityusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams users by activity type report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/teams/report/report-useractivityuserdetail.mdx

@@ -20,9 +20,6 @@ m365 teams report useractivityuserdetail [options]
 
 `-d, --date [date]`
 : The date for which you would like to view the users who performed any activity. Supported date format is `YYYY-MM-DD`. Specify the `date` or `period`, but not both.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams user activity by user report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/tenant/people/people-profilecardproperty-add.mdx

@@ -38,7 +38,7 @@ You can specify localized values for the `displayName` as well. These can be ent
 
 :::
 
-:::caution
+:::warning
 
 When adding an attribute to a profile card, it takes up to 24 hours for the addition to be displayed.
 

package/docs/docs/cmd/tenant/people/people-profilecardproperty-remove.mdx

@@ -32,7 +32,7 @@ To use this command you must be either **Tenant Administrator** or **Global Admi
 
 :::
 
-:::caution
+:::warning
 
 When removing an attribute from a profile card, it takes up to 24 hours for the change to be displayed.
 

package/docs/docs/cmd/tenant/people/people-profilecardproperty-set.mdx

@@ -38,7 +38,7 @@ You can specify localized values for the `displayName` as well. These can be ent
 
 :::
 
-:::caution
+:::warning
 
 When updating an attribute to a profile card, it takes up to 24 hours for the addition to be displayed.
 

package/docs/docs/cmd/tenant/report/report-activeusercounts.mdx

@@ -17,9 +17,6 @@ m365 tenant report activeusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the Microsoft Teams daily unique users by device type report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/tenant/report/report-activeuserdetail.mdx

@@ -20,9 +20,6 @@ m365 tenant report activeuserdetail [options]
 
 `-p, --period [period]`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/tenant/report/report-servicesusercounts.mdx

@@ -17,9 +17,6 @@ m365 tenant report servicesusercounts [options]
 ```md definition-list
 `-p, --period <period>`
 : The length of time over which the report is aggregated. Supported values `D7`, `D30`, `D90`, `D180`.
-
-`--outputFile [outputFile]`
-: Path to the file where the report should be stored in.
 ```
 
 <Global />

package/docs/docs/cmd/yammer/group/group-list.mdx

@@ -26,7 +26,7 @@ m365 yammer group list [options]
 
 ## Remarks
 
-:::caution
+:::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.
 

package/docs/docs/cmd/yammer/group/group-user-add.mdx

@@ -27,7 +27,7 @@ m365 yammer group user add [options]
 
 ## Remarks
 
-:::caution
+:::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.
 

package/docs/docs/cmd/yammer/group/group-user-remove.mdx

@@ -27,7 +27,7 @@ m365 yammer group user remove [options]
 
 ## Remarks
 
-:::caution
+:::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.