diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md index 4ee07a6a0e..bd2442389b 100644 --- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md @@ -50,6 +50,7 @@ New-CsTeamsCallingPolicy [-Identity] [-MusicOnHoldEnabledType ] [-PopoutAppPathForIncomingPstnCalls ] [-PopoutForIncomingPstnCalls ] + [-PreventComplianceRecording ] [-PreventTollBypass ] [-SpamFilteringEnabledType ] [-VoiceSimulationInInterpreter ] @@ -662,6 +663,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PreventComplianceRecording + +> Applicable: Microsoft Teams + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Controls whether Compliance Recording (CR)-enabled users are blocked from joining calls owned by the policy-assigned user. When set to `None`, no restriction is applied and compliance recording operates as configured for the tenant. When set to `All`, CR-enabled users are blocked from joining calls initiated by or received by the policy-assigned user. This applies to both internal and external CR-enabled users (including federated and B2B guests). Anonymous and PSTN users are unaffected as they cannot be assigned compliance recording. + +Possible values: + +- **None**: Compliance recording is not prevented. The tenant's compliance recording configuration applies normally. This is the default value. +- **All**: CR-enabled users are blocked from joining calls initiated by or received by the policy-assigned user. This applies to all CR-enabled users regardless of whether they are internal or external to the tenant. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PreventTollBypass > Applicable: Microsoft Teams diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md index 0ed7e18503..39902f5442 100644 --- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md @@ -100,6 +100,7 @@ New-CsTeamsMeetingPolicy [-Identity] [-NoiseSuppressionForDialInParticipants ] [-ParticipantNameChange ] [-PreferredMeetingProviderForIslandsMode ] + [-PreventComplianceRecording ] [-QnAEngagementMode ] [-RecordingStorageMode ] [-RoomAttributeUserOverride ] @@ -1568,6 +1569,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PreventComplianceRecording + +> Applicable: Microsoft Teams + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Controls whether Compliance Recording (CR)-enabled users are blocked from joining meetings organized by the policy-assigned user. When set to `None`, no restriction is applied and compliance recording operates as configured for the tenant. When set to `All`, CR-enabled users are blocked from joining meetings organized by the policy-assigned user. This applies to both internal and external CR-enabled users (including federated and B2B guests). Anonymous and PSTN users are unaffected as they cannot be assigned compliance recording. + +Possible values: + +- **None**: Compliance recording is not prevented. The tenant's compliance recording configuration applies normally. This is the default value. +- **All**: CR-enabled users are blocked from joining meetings organized by the policy-assigned user. This applies to all CR-enabled users regardless of whether they are internal or external to the tenant. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -QnAEngagementMode This setting enables Microsoft 365 Tenant Admins to Enable or Disable the Questions and Answers experience (Q+A). When Enabled, Organizers can turn on Q+A for their meetings. When Disabled, Organizers cannot turn on Q+A in their meetings. The setting is enforced when a meeting is created or is updated by Organizers. Attendees can use Q+A in meetings where it was previously added. Organizers can remove Q+A for those meetings through Teams and Outlook Meeting Options. Possible values: Enabled, Disabled diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md index 660614830c..48bf9e52fa 100644 --- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md @@ -49,6 +49,7 @@ Set-CsTeamsCallingPolicy [-Identity] [-MusicOnHoldEnabledType ] [-PopoutAppPathForIncomingPstnCalls ] [-PopoutForIncomingPstnCalls ] + [-PreventComplianceRecording ] [-PreventTollBypass ] [-SpamFilteringEnabledType ] [-VoiceSimulationInInterpreter ] @@ -665,6 +666,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PreventComplianceRecording + +> Applicable: Microsoft Teams + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Controls whether Compliance Recording (CR)-enabled users are blocked from joining calls owned by the policy-assigned user. When set to `None`, no restriction is applied and compliance recording operates as configured for the tenant. When set to `All`, CR-enabled users are blocked from joining calls initiated by or received by the policy-assigned user. This applies to both internal and external CR-enabled users (including federated and B2B guests). Anonymous and PSTN users are unaffected as they cannot be assigned compliance recording. + +Possible values: + +- **None**: Compliance recording is not prevented. The tenant's compliance recording configuration applies normally. This is the default value. +- **All**: CR-enabled users are blocked from joining calls initiated by or received by the policy-assigned user. This applies to all CR-enabled users regardless of whether they are internal or external to the tenant. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PreventTollBypass > Applicable: Microsoft Teams diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md index 9994251cb5..ca8441fe6e 100644 --- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md +++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md @@ -104,6 +104,7 @@ Set-CsTeamsMeetingPolicy [[-Identity] ] [-NoiseSuppressionForDialInParticipants ] [-ParticipantNameChange ] [-PreferredMeetingProviderForIslandsMode ] + [-PreventComplianceRecording ] [-QnAEngagementMode ] [-RecordingStorageMode ] [-RoomAttributeUserOverride ] @@ -1610,6 +1611,32 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PreventComplianceRecording + +> Applicable: Microsoft Teams + +> [!NOTE] +> This feature has not been released yet and will have no changes if it is enabled or disabled. + +Controls whether Compliance Recording (CR)-enabled users are blocked from joining meetings organized by the policy-assigned user. When set to `None`, no restriction is applied and compliance recording operates as configured for the tenant. When set to `All`, CR-enabled users are blocked from joining meetings organized by the policy-assigned user. This applies to both internal and external CR-enabled users (including federated and B2B guests). Anonymous and PSTN users are unaffected as they cannot be assigned compliance recording. + +Possible values: + +- **None**: Compliance recording is not prevented. The tenant's compliance recording configuration applies normally. This is the default value. +- **All**: CR-enabled users are blocked from joining meetings organized by the policy-assigned user. This applies to all CR-enabled users regardless of whether they are internal or external to the tenant. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -QnAEngagementMode This setting enables Microsoft 365 Tenant Admins to Enable or Disable the Questions and Answers experience (Q+A).