@pnp/cli-microsoft365 7.3.0-beta.73848f3 → 7.3.0-beta.ca3f7f5

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.
 
-:::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/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.
 
-:::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/eventreceiver/eventreceiver-remove.mdx

@@ -42,7 +42,7 @@ m365 spo eventreceiver remove [options]
 
 ## Remarks
 
-:::caution
+:::warning
 
 You can only remove an event receiver if it has been registered by an app with the same ID.
 

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`.
 
-:::caution 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-sensitivitylabel-ensure.mdx

@@ -36,7 +36,7 @@ m365 spo list sensitivitylabel ensure [options]
 
 ## Remarks
 
-:::caution
+:::warning
 
 This command is based on an API that is currently in preview and is subject to change once the API reaches general availability.
 

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 `<`.
 
-:::caution 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
 
-:::caution 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

@@ -40,7 +40,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
 ```
 
-:::caution 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
 
-:::caution 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_.
 
-:::caution 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.
 
-:::caution 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,7 +63,7 @@ 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>"}]'`.
 
-:::caution 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.
 

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

@@ -17,9 +17,6 @@ m365 spo report activityfilecounts [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-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 />