Update TeamsEventsPolicy and TeamsMeetingPolicy to New and Set cmdlets to document new parameter for Backroom Chat

teams/teams-ps/MicrosoftTeams/New-CsTeamsEventsPolicy.md

@@ -16,7 +16,7 @@ This cmdlet allows you to create a new TeamsEventsPolicy instance and set its pr
 ## SYNTAX
 
 ```powershell
-New-CsTeamsEventsPolicy [-Identity] <String> [-AllowWebinars <String>] [-AllowTownhalls <String>] [-ImmersiveEvents <String>] [-AllowEmailEditing <String>] [-Description <String>]
+New-CsTeamsEventsPolicy [-Identity] <String> [-AllowWebinars <String>] [-AllowTownhalls <String>] [-BackroomChat <String>] [-ImmersiveEvents <String>] [-AllowEmailEditing <String>] [-Description <String>]
 [-TownhallEventAttendeeAccess <String>] [-RecordingForTownhall <String>] [-RecordingForWebinar <String>]
 [-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>] [-AllowEventIntegrations <Boolean>] [-TownhallChatExperience <String>]
 [-UseMicrosoftECDN <String>] [-EventAccessType <String>] [-BroadcastPremiumApps <String>]  [-TownhallMaxResolution <String>] [-HighBitrateForTownhall <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
@@ -163,6 +163,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -BackroomChat
+> [!NOTE]
+> This feature has not been fully released yet, so the setting will have no effect.
+This setting governs whether the user can create Events with Backroom Chat enabled.
+
+Possible values are:
+ - **Enabled**: Enables creating Events with Backroom Chat.
+ - **Disabled**: Disables creating Events with Backroom Chat.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:    
+
+Required: False
+Position: Named
+Default value: Enabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -BroadcastPremiumApps
 This setting will enable Tenant Admins to specify if an organizer of a Teams Premium town hall may add an app that is accessible by everyone, including attendees, in a broadcast style Event including a Town hall. This does not include control over apps (such as AI Producer and Custom Streaming Apps) that are only accessible by the Event group.
 

teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md

@@ -71,6 +71,7 @@ New-CsTeamsMeetingPolicy [-Identity] <XdsIdentity>
  [-AudibleRecordingNotification <String>]
  [-AutoAdmittedUsers <String>]
  [-AutomaticallyStartCopilot <String>]
+ [-BackroomChat <String>]
  [-BlockedAnonymousJoinClientTypes <List>]
  [-CaptchaVerificationForMeetingJoin <String>]
  [-ChannelRecordingDownload <String>]
@@ -1008,6 +1009,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -BackroomChat
+> [!NOTE]
+> This feature has not been fully released yet, so the setting will have no effect.
+This setting governs whether the user can create Events with Backroom Chat enabled.
+
+Possible values are:
+ - **Enabled**: Enables creating Events with Backroom Chat.
+ - **Disabled**: Disables creating Events with Backroom Chat.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:    
+
+Required: False
+Position: Named
+Default value: Enabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -BlockedAnonymousJoinClientTypes
 A user can join a Teams meeting anonymously using a [Teams client](https://support.microsoft.com/office/join-a-meeting-without-a-teams-account-c6efc38f-4e03-4e79-b28f-e65a4c039508) or using a [custom application built using Azure Communication Services](https://learn.microsoft.com/azure/communication-services/concepts/join-teams-meeting). When anonymous meeting join is enabled, both types of clients may be used by default. This optional parameter can be used to block one of the client types that can be used.
 

teams/teams-ps/MicrosoftTeams/Set-CsTeamsEventsPolicy.md

@@ -14,9 +14,8 @@ title: Set-CsTeamsEventsPolicy
 This cmdlet allows you to configure options for customizing Teams events experiences. Note that this policy is currently still in preview.
 
 ## SYNTAX
-
-```
-Set-CsTeamsEventsPolicy [-AllowWebinars <String>] [-EventAccessType <String>] [-AllowTownhalls <String>] [-ImmersiveEvents <String>]
+```powershell
+Set-CsTeamsEventsPolicy [-AllowWebinars <String>] [-EventAccessType <String>] [-AllowTownhalls <String>] [-BackroomChat <String>] [-ImmersiveEvents <String>]
  [-TownhallEventAttendeeAccess <String>] [-AllowEmailEditing <String>] [-AllowedQuestionTypesInRegistrationForm <String>]
  [-AllowEventIntegrations <Boolean>] [-AllowedWebinarTypesForRecordingPublish <String>]
  [-AllowedTownhallTypesForRecordingPublish <String>] [-TownhallChatExperience <String>] [-Description <String>]
@@ -164,6 +163,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -BackroomChat
+> [!NOTE]
+> This feature has not been fully released yet, so the setting will have no effect.
+This setting governs whether the user can create Events with Backroom Chat enabled.
+
+Possible values are:
+ - **Enabled**: Enables creating Events with Backroom Chat.
+ - **Disabled**: Disables creating Events with Backroom Chat.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:    
+
+Required: False
+Position: Named
+Default value: Enabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -BroadcastPremiumApps
 This setting will enable Tenant Admins to specify if an organizer of a Teams Premium town hall may add an app that is accessible by everyone, including attendees, in a broadcast style Event including a Town hall. This does not include control over apps (such as AI Producer and Custom Streaming Apps) that are only accessible by the Event group.
 

teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md

@@ -76,6 +76,7 @@ Set-CsTeamsMeetingPolicy [[-Identity] <XdsIdentity>]
  [-AutoAdmittedUsers <String>]
  [-AutoRecording <String>]
  [-AutomaticallyStartCopilot <String>]
+ [-BackroomChat <String>]
  [-BlockedAnonymousJoinClientTypes <List>]
  [-CaptchaVerificationForMeetingJoin <String>]
  [-ChannelRecordingDownload <String>]
@@ -126,7 +127,7 @@ Set-CsTeamsMeetingPolicy [[-Identity] <XdsIdentity>]
  [-WatermarkForScreenSharingPattern <String>]
  [-AllowedUsersForMeetingDetails <String>]
  [-RealTimeText <String>]
- [-ParticipantSlideControl <String>
+ [-ParticipantSlideControl <String>]
  [-WhatIf]
  [-WhoCanRegister <String>]
  [<CommonParameters>]
@@ -1052,6 +1053,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -BackroomChat
+> [!NOTE]
+> This feature has not been fully released yet, so the setting will have no effect.
+This setting governs whether the user can create Events with Backroom Chat enabled.
+
+Possible values are:
+ - **Enabled**: Enables creating Events with Backroom Chat.
+ - **Disabled**: Disables creating Events with Backroom Chat.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:    
+
+Required: False
+Position: Named
+Default value: Enabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -BlockedAnonymousJoinClientTypes
 A user can join a Teams meeting anonymously using a [Teams client](https://support.microsoft.com/office/join-a-meeting-without-a-teams-account-c6efc38f-4e03-4e79-b28f-e65a4c039508) or using a [custom application built using Azure Communication Services](https://learn.microsoft.com/azure/communication-services/concepts/join-teams-meeting). When anonymous meeting join is enabled, both types of clients may be used by default. This optional parameter can be used to block one of the client types that can be used.