Skip to content

Commit 3ba46a1

Browse files
authored
Merge pull request #6964 from cabailey/patch-3
Update Set-RetentionCompliancePolicy.md
2 parents cfc7054 + 81132fb commit 3ba46a1

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ This cmdlet is available only in Security & Compliance Center PowerShell. For mo
1616

1717
Use the Set-RetentionCompliancePolicy cmdlet to modify existing retention policies in the Security & Compliance Center.
1818

19+
**Note**: Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to update multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy.
20+
1921
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2022

2123
## SYNTAX
@@ -124,8 +126,6 @@ Accept wildcard characters: False
124126
### -RetryDistribution
125127
The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint Online locations. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch.
126128
127-
**Note**: Because the process of retrying distribution is a significant operation, run it only if necessary and for one policy at a time. It is not intended to be run every time you update a policy. If you run a script to update multiple policies, wait until the policy distribution is successful before running the command again for the next policy.
128-
129129
```yaml
130130
Type: SwitchParameter
131131
Parameter Sets: RetryDistribution
@@ -775,14 +775,14 @@ Accept wildcard characters: False
775775
```
776776

777777
### -RestrictiveRetention
778-
The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are:
778+
The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for a retention policy or retention label policy. Valid values are:
779779

780780
- $true: Preservation Lock is enabled for the policy. No one (including an administrator) can turn off the policy or make it less restrictive.
781781
- $false: Preservation Lock isn't enabled for the policy. This is the default value.
782782

783-
After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
783+
After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only way that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
784784

785-
Therefore, before you lock a retention policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need.
785+
Therefore, before you lock a policy for retention, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need.
786786

787787
```yaml
788788
Type: Boolean

0 commit comments

Comments
 (0)