Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
45aecc1
Update Set-RetentionCompliancePolicy.md
vilega Feb 26, 2025
c16a228
Update DeletedResources parameter details and examples
vilega Feb 26, 2025
a2830c8
Fix broken link in documentation
vilega Feb 26, 2025
0475f3b
Clarify policy exclusion example description
vilega Feb 26, 2025
90db49e
Clarify exclusion of soft-deleted mailboxes
vilega Feb 26, 2025
9ed1bcc
Update Set-AppRetentionCompliancePolicy.md
vilega Feb 26, 2025
ca61d3b
Update link format in documentation
vilega Feb 26, 2025
9a130bd
Clarify DeletedResources parameter description
vilega Feb 26, 2025
8c3c35f
Fix capitalization and formatting in documentation
chrisda Feb 26, 2025
2829863
Update wording for clarity in documentation
chrisda Feb 26, 2025
ed068f9
Update documentation for policy exclusions and parameters
chrisda Feb 26, 2025
0cd991e
Update New-CsTeamsEventsPolicy.md
SarinaMS Feb 26, 2025
a72177c
Update Set-CsTeamsEventsPolicy.md
SarinaMS Feb 26, 2025
27b42e7
Update Set-CsTeamsEventsPolicy.md
SarinaMS Feb 26, 2025
8d45050
Update New-CsTeamsEventsPolicy.md
SarinaMS Feb 26, 2025
f697daf
Update Set-CsTeamsEventsPolicy.md
SarinaMS Feb 26, 2025
89958aa
Update retention policy example and documentation
vilega Feb 26, 2025
7d12846
Merge pull request #12549 from vilega/patch-3
cabailey Feb 26, 2025
79934f6
Clarify wording for limits to match other cmdlet
cabailey Feb 26, 2025
3a55e57
Merge branch 'main' into patch-2
cabailey Feb 26, 2025
2c6f7dd
Merge pull request #12548 from vilega/patch-2
cabailey Feb 26, 2025
da5bf6a
Merge branch 'main' into patch-2
rjagiewich Feb 26, 2025
92eddb8
Merge pull request #12550 from SarinaMS/patch-2
rjagiewich Feb 26, 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
Expand Up @@ -119,6 +119,34 @@ Set-AppRetentionCompliancePolicy -Identity "Regulation 563 Marketing" -Applicati

This example adds a new user to the existing static scope retention policy named Regulation 563 Marketing that's set up for Teams private channels messages.

### Example 2
```powershell
$stringJson = @"
[{
'EmailAddress': '[email protected]'
}]
"@
Set-AppRetentionCompliancePolicy -Identity "Teams Private Channel Retention Policy" -AddExchangeLocationException "[email protected]" -DeletedResources $stringJson
```
This example excludes the specified soft-deleted mailbox or mail user from the retention policy configured for Teams private channel messages. You can identify the deleted resources using the mailbox or mail user's email address.

Policy exclusions must remain within the supported limits for retention policies. For more information, see [Limits for Microsoft 365 retention policies and retention label policies](https://learn.microsoft.com/purview/retention-limits#maximum-number-of-items-per-policy).

### Example 3
```powershell
$stringJson = @"
[{
'EmailAddress': '[email protected]'
},
{
'EmailAddress': '[email protected]'
}]
"@
Set-AppRetentionCompliancePolicy -Identity "Teams Private Chat Retention Policy" -AddExchangeLocationException "[email protected]", "[email protected]" -DeletedResources $stringJson
```

This example is similar to Example 2, except multiple deleted resources are specified.

## PARAMETERS

### -Identity
Expand Down Expand Up @@ -347,7 +375,11 @@ Accept wildcard characters: False
```

### -DeletedResources
{{ Fill DeletedResources Description }}
The DeletedResources parameter specifies the deleted mailbox or mail user to add as an exclusion to the respective location list. Use this parameter with the AddTeamsChatLocationException parameter for deleted mailboxes or mail users that needs to be excluded from a Teams only retention policy.

A valid value is a JSON string. Refer to the Examples section for syntax and usage examples of this parameter.

For information on the inactive mailbox scenario, see [Learn about inactive mailboxes](https://learn.microsoft.com/purview/inactive-mailboxes-in-office-365).

```yaml
Type: String
Expand Down
38 changes: 35 additions & 3 deletions exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -180,6 +180,36 @@ Set-RetentionCompliancePolicy -Identity "Sales Policy" -RemoveModernGroupLocatio

This example is similar to Example 2, except multiple deleted resources are specified.

### Example 5
```powershell
$stringJson = @"
[{
'EmailAddress': '[email protected]'
}]
"@

Set-RetentionCompliancePolicy -Identity "Teams Chat Retention Policy" -AddTeamsChatLocationException "[email protected]" -DeletedResources $stringJson
```

This example excludes the specified soft-deleted mailbox or mail user from the mentioned Teams Retention Policy. You can identify the deleted resources using the mailbox or mail user's email address.
Policy exclusions must remain within the supported limits for retention policies: [Limits for Microsoft 365 retention policies and retention label policies](https://learn.microsoft.com/purview/retention-limits#maximum-number-of-items-per-policy)

### Example 6
```powershell
$stringJson = @"
[{
'EmailAddress': '[email protected]'
},
{
'EmailAddress': '[email protected]'
}]
"@

Set-RetentionCompliancePolicy -Identity "Teams Chat Retention Policy" -AddTeamsChatLocationException "[email protected]", "[email protected]" -DeletedResources $stringJson
```

This example is similar to Example 5, except multiple deleted resources are specified.

## PARAMETERS

### -Identity
Expand Down Expand Up @@ -629,11 +659,13 @@ Accept wildcard characters: False
```

### -DeletedResources
The DeletedResources parameter specifies the Sharepoint sites to be removed from the list of included sites or excluded from a tenant level policy when the associated group has been deleted. You use this parameter with the AddModernGroupLocationException and RemoveModernGroupLocation parameters.
The DeletedResources parameter specifies the deleted Microsoft 365 Group, mailbox, or mail user to be removed or added as an exclusion to the respective location list. Use this parameter with the AddModernGroupLocationException and RemoveModernGroupLocation parameters for deleted Microsoft 365 Groups, or with the AddTeamsChatLocationException parameter for deleted mailboxes or mail users.

A valid value is a JSON string. Refer to the Examples section for syntax and usage examples of this parameter.

A valid value is a JSON String. See the Examples section for syntax and examples using this parameter.
For more information on the deleted Microsoft 365 Group scenario, see [Learn more about modern group deletion under retention hold](https://learn.microsoft.com/purview/retention-settings#what-happens-if-a-microsoft-365-group-is-deleted-after-a-policy-is-applied).

For more information about this scenario, see [Learn more about modern group deletion under retention hold](https://learn.microsoft.com/purview/retention-settings#what-happens-if-a-microsoft-365-group-is-deleted-after-a-policy-is-applied).
For more information on the inactive mailbox scenario, see [Learn about inactive mailboxes](https://learn.microsoft.com/purview/inactive-mailboxes-in-office-365).

```yaml
Type: String
Expand Down
22 changes: 20 additions & 2 deletions teams/teams-ps/teams/New-CsTeamsEventsPolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Module Name: MicrosoftTeams
online version: https://learn.microsoft.com/powershell/module/teams/new-csteamseventspolicy
title: New-CsTeamsEventsPolicy
schema: 2.0.0
ms.date: 11/12/2024
ms.date: 02/26/2025
---

# New-CsTeamsEventsPolicy
Expand All @@ -16,7 +16,7 @@ This cmdlet allows you to create a new TeamsEventsPolicy instance and set its pr

```powershell
New-CsTeamsEventsPolicy [-Identity] <String> [-AllowWebinars <String>] [-AllowTownhalls <String>] [-AllowEmailEditing <String>] [-Description <String>]
[-RecordingForTownhall <String>] [-RecordingForWebinar <String>]
[-TownhallEventAttendeeAccess <String>] [-RecordingForTownhall <String>] [-RecordingForWebinar <String>]
[-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>] [-AllowEventIntegrations <Boolean>] [-TownhallChatExperience <String>]
[-UseMicrosoftECDN <String>] [-EventAccessType <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
[-ImmersiveEvents <String>]
Expand Down Expand Up @@ -94,6 +94,24 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -TownhallEventAttendeeAccess
This setting governs what identity types may attend a Town hall that is scheduled by a particular person or group that is assigned this policy.
Possible values are:
- **Everyone**: Anyone with the join link may enter the event.
- **EveryoneInOrganizationAndGuests**: Only those who are Guests to the tenant, MTO users, and internal AAD users may enter the event.

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

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

### -AllowEmailEditing
This setting governs if a user is allowed to edit the communication emails in Teams Town Hall or Teams Webinar events.
Possible values are:
Expand Down
22 changes: 20 additions & 2 deletions teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Module Name: MicrosoftTeams
online version: https://learn.microsoft.com/powershell/module/teams/set-csteamseventspolicy
title: Set-CsTeamsEventsPolicy
schema: 2.0.0
ms.date: 11/12/2024
ms.date: 02/26/2025
---

# Set-CsTeamsEventsPolicy
Expand All @@ -16,7 +16,7 @@ This cmdlet allows you to configure options for customizing Teams events experie

```
Set-CsTeamsEventsPolicy [-AllowWebinars <String>] [-EventAccessType <String>] [-AllowTownhalls <String>]
[-AllowEmailEditing <String>] [-AllowedQuestionTypesInRegistrationForm <String>]
[-TownhallEventAttendeeAccess <String>] [-AllowEmailEditing <String>] [-AllowedQuestionTypesInRegistrationForm <String>]
[-AllowEventIntegrations <Boolean>] [-AllowedWebinarTypesForRecordingPublish <String>]
[-AllowedTownhallTypesForRecordingPublish <String>] [-TownhallChatExperience <String>] [-Description <String>]
[-RecordingForTownhall <String>] [-RecordingForWebinar <String>]
Expand Down Expand Up @@ -106,6 +106,24 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -TownhallEventAttendeeAccess
This setting governs what identity types may attend a Town hall that is scheduled by a particular person or group that is assigned this policy.
Possible values are:
- **Everyone**: Anyone with the join link may enter the event.
- **EveryoneInOrganizationAndGuests**: Only those who are Guests to the tenant, MTO users, and internal AAD users may enter the event.

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

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

### -Description
Enables administrators to provide explanatory text to accompany a Teams Events policy.

Expand Down