Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
fa53de9
Update Set-CsTeamsMeetingPolicy.md
dlb233 Oct 28, 2025
f6e1c3e
Update Set-CsTeamsMeetingPolicy.md
dlb233 Oct 28, 2025
c76778d
Update Set-CsTeamsCallingPolicy.md
dlb233 Oct 28, 2025
013a13b
Update New-CsTeamsMeetingPolicy.md
dlb233 Oct 28, 2025
997205d
Update New-CsTeamsCallingPolicy.md
dlb233 Oct 28, 2025
ccc58b7
Create New-CsTeamsRecordingAndTranscriptionCustomMessage
dlb233 Oct 28, 2025
c07fc59
Create New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage
dlb233 Oct 29, 2025
2c641e5
Rename New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage …
dlb233 Oct 29, 2025
83ca4b4
Update and rename New-CsTeamsRecordingAndTranscriptionCustomMessage t…
dlb233 Oct 30, 2025
9402a93
Create Set-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
863acd0
Create Get-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
0e6f43c
Update Get-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
84f5742
Create Remove-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
a454545
Update Get-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
7b269b9
Update New-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
bc28b2d
Update Set-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
b6d66c1
Update New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage.md
dlb233 Oct 30, 2025
9a62c07
Update New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage.md
dlb233 Oct 30, 2025
a3fe6b2
Update Get-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
2292566
Update Set-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
271f6b6
Update Get-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
eacfce2
Update New-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
fcab740
Update Remove-CsTeamsRecordingAndTranscriptionCustomMessage.md
dlb233 Oct 30, 2025
8298f0f
Update New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage.md
dlb233 Oct 30, 2025
e59d865
Update New-CsTeamsCallingPolicy.md
dlb233 Oct 30, 2025
eb9c350
Update New-CsTeamsMeetingPolicy.md
dlb233 Oct 30, 2025
b53389c
Update Set-CsTeamsMeetingPolicy.md
dlb233 Oct 30, 2025
91c9ce5
Update Set-CsTeamsCallingPolicy.md
dlb233 Oct 30, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
author: lingbodu
Locale: en-US
Module Name: MicrosoftTeams
ms.author: wblocker
online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsTeamsRecordingAndTranscriptionCustomMessage
schema: 2.0.0
title: Get-CsTeamsRecordingAndTranscriptionCustomMessage
---

> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.

Return information about the instance of TeamsRecordingAndTranscriptionCustomMessage that have been configured for recording and transcription customized message.

## SYNTAX

### Identity (Default)
```
Get-CsTeamsRecordingAndTranscriptionCustomMessage [-Id <Guid>]
```

## DESCRIPTION
The strings defined in TeamsRecordingAndTranscriptionCustomMessage is used for display after recording or transcription is started in a meeting.
Based on the different scenarios when recording or transcription is enabled, we provide different keys for customization, as detailed below.
These strings will not take effect immediately after being created; they need to be associated with other configurations and policies.

This command will return existing TeamsRecordingAndTranscriptionCustomMessage by your input condition that have been configured before with New-CsTeamsRecordingAndTranscriptionCustomMessage.

## EXAMPLES

### Example 1
```powershell
PS C:\> Get-CsTeamsRecordingAndTranscriptionCustomMessage
```
The command shown in Example 1 returns information for all the instances of TeamsRecordingAndTranscriptionCustomMessage that have been created.

### Example 2
```powershell
PS C:\> Get-CsTeamsRecordingAndTranscriptionCustomMessage -Id '39dc3ede-c80e-4f19-9153-417a65a1f144'
```
In Example 2, information is returned for a single instance of a TeamsRecordingAndTranscriptionCustomMessage with the Id 39dc3ede-c80e-4f19-9153-417a65a1f144.

## RELATED LINKS
[New-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/new-CsTeamsRecordingAndTranscriptionCustomMessage)

[Set-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/set-CsTeamsRecordingAndTranscriptionCustomMessage)

[Remove-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/remove-CsTeamsRecordingAndTranscriptionCustomMessage)

[New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/new-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage)


36 changes: 36 additions & 0 deletions teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,8 @@ New-CsTeamsCallingPolicy [-Identity] <string>
[-RealTimeText <string>]
[-ExplicitRecordingConsent <string>]
[-WhatIf]
[-EnableRecordingAndTranscriptionCustomMessage <Boolean>]
[-RecordingAndTranscriptionCustomMessageIdentifier <Guid>]
[<CommonParameters>]
```

Expand Down Expand Up @@ -798,6 +800,40 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -EnableRecordingAndTranscriptionCustomMessage
> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.
This policy controls whether custom strings can be shown for recording and transcription in user's Teams calls. It need to work with RecordingAndTranscriptionCustomMessageIdentifier.

```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -RecordingAndTranscriptionCustomMessageIdentifier
> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.
This attribute holds the unique identifier for the custom recording and transcription calling message. It stores a GUID that points to the CustomMessage in TeamsCustomMessageConfiguration.

```yaml
Type: Guid
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

Expand Down
36 changes: 36 additions & 0 deletions teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,8 @@ New-CsTeamsMeetingPolicy [-Identity] <XdsIdentity>
[-ParticipantSlideControl <string>]
[-WhatIf]
[-WhoCanRegister <Object>]
[-EnableRecordingAndTranscriptionCustomMessage <Boolean>]
[-RecordingAndTranscriptionCustomMessageIdentifier <Guid>]
[<CommonParameters>]
```

Expand Down Expand Up @@ -1981,6 +1983,40 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -EnableRecordingAndTranscriptionCustomMessage
> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.
This policy controls whether custom strings can be shown for recording and transcription in user's Teams meetings. It need to work with RecordingAndTranscriptionCustomMessageIdentifier.

```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -RecordingAndTranscriptionCustomMessageIdentifier
> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.
This attribute holds the unique identifier for the custom recording and transcription meeting message. It stores a GUID that points to the CustomMessage in TeamsCustomMessageConfiguration.

```yaml
Type: Guid
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
---
author: lingbodu
Locale: en-US
Module Name: MicrosoftTeams
ms.author: wblocker
online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-CsTeamsRecordingAndTranscriptionCustomMessage
schema: 2.0.0
title: New-CsTeamsRecordingAndTranscriptionCustomMessage
---

# New-CsTeamsRecordingAndTranscriptionCustomMessage

> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.

## SYNOPSIS

Create a concrete prompt message setting in multiple languages and multiple scenarios to be displayed to participants after recording or transcription has started.
## SYNTAX

```
New-CsTeamsRecordingAndTranscriptionCustomMessage
[-Id <System.Guid>]
[-Description <String>]
[-RecordingAndTranscriptionLocalizationCustomMessage <RecordingAndTranscriptionLocalizationCustomMessage>]
[<CommonParameters>]
```

## DESCRIPTION
The strings defined by this command is used for display after recording or transcription is started in a meeting.
Based on the different scenarios when recording or transcription is enabled, we provide different keys for customization, as detailed below.
These strings will not take effect immediately after being created; they need to be associated with other configurations and policies.

This command will define a complete custom message override policy that can be directly assigned to users.
It specifies the UFD prompt content that users with different roles will see in six different scenarios when starting recording and transcription, across various language environments.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UFD is not defined. Please spell it out or describe it

After this configuration is successfully completed, you can assign the generated Id to the user’s RecordingAndTranscriptionCustomMessageIdentifier field to apply the policy to that user. Afterwards, in meetings hosted by this user, once the language and scenario match, participants will see the new UFD message customized by this command.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UFD is not defined. Please spell it out or describe it


## EXAMPLES

### Example 1
```powershell
PS C:\> New-CsTeamsRecordingAndTranscriptionCustomMessage -Id '39dc3ede-c80e-4f19-9153-417a65a1f144'
```

The command shown in Example 1 creates an in-memory instance of a CsTeamsRecordingAndTranscriptionCustomMessage with no content. It can be set to RecordingAndTranscriptionCustomMessageIdentifier but nothing will change.

### Example 2
```
$en = New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage -Language "en-US" -InitiatorImplicit "This call is being recorded." -ParticipantImplicit "This call is being recorded."
>> $zh = New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage -Language "zh-CN" -InitiatorExplicit "请注意,此通话正在录音。" -ParticipantExplicitRequested "此通话正在录音,我们将在得到您同意后再录制你的声音。"
>> New-CsTeamsRecordingAndTranscriptionCustomMessage -Description "Multi languages record custom message" -RecordingAndTranscriptionLocalizationCustomMessage @($en, $zh)
```
Example 2 demonstrates a complete case, defining the recording and transcription prompt messages that users see in English and Chinese under different scenarios.
If such policy applied to the meeting organizer, then:
- Current user is recording/transcription intiator, Teams language is English US", the meeting organizer doesn't enable consent recording/transcription, when current user start recording or transcript, he/she will see "This call is being recorded.".
- Current user is normal participant, Teams language is English US, the meeting organizer doesn't enable consent recording/transcription, when recording or transcript started, current user will see "This call is being recorded."
- Current user is recording/transcription intiator, Teams language is Chinese simplify, the meeting organizer enable the consent recording/transcription, when current user start recording or transcript, he/she will see "请注意,此通话正在录音。"
- Current user is normal participant, Teams language is Chinese simplify, the meeting organizer enable the consent recording/transcription,after someone started recording or transcription, he will see "此通话正在录音,我们将在得到您同意后再录制你的声音。"

## Parameters
### -Id
The ObjectId of the CsTeamsRecordingAndTranscriptionCustomMessage setting, By assigning the ID to the **RecordingAndTranscriptionCustomMessageIdentifier** field in the meeting policy or calling policy, you can associate the current custom prompt message configuration with a user group or individual users.

At the same time, when creating CsTeamsRecordingAndTranscriptionCustomMessage, it is not necessary to explicitly specify the ID; a GUID will be automatically generated and stored as the Id.

### -DESCRIPTION
Add a description for CsTeamsRecordingAndTranscriptionCustomMessage.

### RecordingAndTranscriptionLocalizationCustomMessage
Set the specific recording and transcription prompt messages to be customized. The type is a list of TeamsRecordingAndTranscriptionLocalizationCustomMessage, with each element in the list representing a custom message for a particular language. For more information, please refer to New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage.
```yaml
Type: TeamsRecordingAndTranscriptionLocalizationCustomMessage[]
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

## RELATED LINKS
[Set-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/set-CsTeamsRecordingAndTranscriptionCustomMessage)

[Get-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsTeamsRecordingAndTranscriptionCustomMessage)

[Remove-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/remove-CsTeamsRecordingAndTranscriptionCustomMessage)

[New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/new-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage)
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
---
applicable: Microsoft Teams
author: lingbodu
external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml
Locale: en-US
Module Name: MicrosoftTeams
ms.author:
online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage
schema: 2.0.0
title: New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage
---
# New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage

> [!NOTE]
> This feature has not been fully released yet, so the setting will have no effect.

## SYNOPSIS
Create a set of language-specific prompt messages to be displayed to participants after recording or transcription has started.


## SYNTAX

```
New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage -Language <String>
[<CommonParameters>]
```

The strings defined by this command is used for display after recording or transcription is started in a meeting. Based on the different scenarios when recording or transcription is enabled, we provide different keys for customization, as detailed below.
These strings will not take effect immediately after being created; they need to be associated with other configurations and policies.


| key name | description |
| ---------|-------------|
| initiatorImplicit | User is recording/transcription initiator, recording/transcription consent policy is off for the organizer.|
| ParticipantImplicit | Others in meeting/calling turns on the recording or transcription, recording/transcription consent policy is off for the organizer.|
| initiatorExplicit | User is recording/transcription initiator, recording/transcription consent policy is on for the organizer.|
| ParticipantExplicitRequested | Others in meeting/calling turns on the recording or transcription, recording/transcription consent policy is on for the organizer. Current consent state is "required the attendee to give the consent to recording and transcription"|
| ParticipantExplicitProvided | Others in meeting/calling turns on the recording or transcription, recording/transcription consent policy is on for the organizer. Current consent state is "attendee has given the consent to recording and transcription"|
| agreementDialogue | Others in meeting/calling turns on the recording or transcription, recording/transcription consent policy is on for the organizer. User clicks the mute/share screen/turn on camera, then a confirm dialog will show to the user.|

In most cases, we directly use the custom string to overwrite the original string content. For example, under normal circumstances, when the meeting organizer starts recording, the prompt shown to regular participants is "Started by XXX. By attending this meeting, you agree to being included." If you set the ParticipantImplicit string to "This meeting will be recorded." and successfully apply it to the organizer, then regular participants will see: "Started by XXX. This meeting will be recorded."

However, ParticipantExplicitRequested and agreementDialogue are handled differently. Their original content contains instructional information, so we retain the original content and append the custom content after it.

Note that this cmdlet is only used in conjunction with New-CsTeamsRecordingAndTranscriptionCustomMessage and Set-CsTeamsRecordingAndTranscriptionCustomMessage to create associations between messages in multiple languages.
Please refer to the documentation of CsTeamsRecordingAndTranscriptionCustomMessage cmdlets for examples and further information.

## EXAMPLES

### Example 1
```powershell
PS C:\> New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage -Language "en-US" -InitiatorImplicit "This call is being recorded." -ParticipantImplicit "This call is being recorded."
```
The command shown in Example 1 created a new set of custom message in en-US, it defined 2 scenarios, InitiatorImplicit and ParticipantImplicit.

### Example 2
```powershell
PS C:\> New-CsTeamsRecordingAndTranscriptionLocalizationCustomMessage -Language "en-US" -initiatorExplicit "<empty>" -ParticipantExplicitProvided "<empty>"
```
**<empty>** is a keyword for clean the default message. The command shown in Example 2 will create a void message to override the default message of initiatorExplicit and ParticipantExplicitProvided scenarios.


## PARAMETERS

### -Language
Define language of the message set. In a meeting, if the organizer has applied a custom message, all participants will use the organizer’s policy. If meeting participants are from different countries and regions, then when recording or transcription is enabled, the prompt content depends on whether the organizer has customized the message for the language currently used by each participant. For example, if A is the meeting organizer and the policy applied to A defines messages in English and French, and B, C, and D use English, Chinese, and French as their Teams languages respectively, then B and D will see the customized prompt, while C will only see the default prompt.

### -initiatorImplicit
With **-ParticipantImplicit**,**-initiatorExplicit**,**-ParticipantExplicitRequested**,**-ParticipantExplicitProvided**,**-agreementDialogue**, as mentioned on above tables, they represent different user scenarios.

## RELATED LINKS
[New-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/new-CsTeamsRecordingAndTranscriptionCustomMessage)

[Set-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/set-CsTeamsRecordingAndTranscriptionCustomMessage)

[Get-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/get-CsTeamsRecordingAndTranscriptionCustomMessage)

[Remove-CsTeamsRecordingAndTranscriptionCustomMessage](https://learn.microsoft.com/powershell/module/microsoftteams/remove-CsTeamsRecordingAndTranscriptionCustomMessage)





Loading