You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ApplyHtmlDisclaimer parameter specifies an action for the rule that adds disclaimer text to messages.This parameter uses the syntax: `@{Text = "Disclaimer text"; Location = <Append | Prepend>; FallbackAction = <Wrap | Ignore | Reject> }`.
276
+
277
+
- Text: Specifies the disclaimer text to add. Disclaimer text can include HTML tags and inline cascading style sheet (CSS) tags. You can add images using the IMG tag.
278
+
- Location: Specifies where to insert the HTML disclaimer text in the body of messages. Append = Add to the end of the message body. Prepend = Insert at the beginning of the message body.
279
+
- FallbackAction: Specifies what to do if the HTML disclaimer can't be added to a message. Wrap = The original message is wrapped in a new message envelope, and the disclaimer is used as the message body for the new message. Ignore = The rule is ignored and the message is delivered without the disclaimer. Reject = The message is rejected.
280
+
281
+
You can use this condition in DLP policies that are scoped only to Exchange.
282
+
283
+
```yaml
284
+
Type: PswsHashtable
285
+
Parameter Sets: (All)
286
+
Aliases:
287
+
Applicable: Security & Compliance Center
288
+
289
+
Required: False
290
+
Position: Named
291
+
Default value: None
292
+
Accept pipeline input: False
293
+
Accept wildcard characters: False
294
+
```
295
+
270
296
### -BlockAccess
271
297
The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are:
The ContentCharacterSetContainsWords parameter specifies a condition for the rule that looks for character set names in messages.
346
-
347
-
To specify multiple words, this parameter uses the syntax: `Word1,word2,...wordN`. Don't use leading or trailing spaces.
371
+
The ContentCharacterSetContainsWords parameter specifies a condition for the rule that looks for character set names in messages. You can specify multiple values separated by commas.
The ExceptIfWithImportance parameter specifies an exception for the rule that looks for messages with the specified importance level. Valid values are:
1193
+
1194
+
- Low
1195
+
- Normal
1196
+
- High
1197
+
1198
+
You can use this exception in DLP policies that are scoped only to Exchange.
1199
+
1200
+
```yaml
1201
+
Type: WithImportance
1202
+
Parameter Sets: (All)
1203
+
Aliases:
1204
+
Applicable: Security & Compliance Center
1205
+
1206
+
Required: False
1207
+
Position: Named
1208
+
Default value: None
1209
+
Accept pipeline input: False
1210
+
Accept wildcard characters: False
1211
+
```
1212
+
1167
1213
### -ExpiryDate
1168
1214
This parameter is reserved for internal Microsoft use.
The PrependSubject parameter specifies an action for the rule that adds text to add to the beginning of the Subject field of messages. The value for this parameter is the text that you want to add. If the text contains spaces, enclose the value in quotation marks (").
1632
+
1633
+
Consider ending the value for this parameter with a colon (:) and a space, or at least a space, to separate it from the original subject.
1634
+
1635
+
You can use this condition in DLP policies that are scoped only to Exchange.
1636
+
1637
+
```yaml
1638
+
Type: String
1639
+
Parameter Sets: (All)
1640
+
Aliases:
1641
+
Applicable: Security & Compliance Center
1642
+
1643
+
Required: False
1644
+
Position: Named
1645
+
Default value: None
1646
+
Accept pipeline input: False
1647
+
Accept wildcard characters: False
1648
+
```
1649
+
1584
1650
### -Priority
1585
1651
The Priority parameter specifies a priority value for the rule that determines the order of rule processing within the policy. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
The WithImportance parameter specifies a condition for the rule that looks for messages with the specified importance level. Valid values are:
2002
+
2003
+
- Low
2004
+
- Normal
2005
+
- High
2006
+
2007
+
You can use this condition in DLP policies that are scoped only to Exchange.
2008
+
2009
+
```yaml
2010
+
Type: WithImportance
2011
+
Parameter Sets: (All)
2012
+
Aliases:
2013
+
Applicable: Security & Compliance Center
2014
+
2015
+
Required: False
2016
+
Position: Named
2017
+
Default value: None
2018
+
Accept pipeline input: False
2019
+
Accept wildcard characters: False
2020
+
```
2021
+
1934
2022
### CommonParameters
1935
2023
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).
The ApplyHtmlDisclaimer parameter specifies an action for the rule that adds disclaimer text to messages.This parameter uses the syntax: `@{Text = "Disclaimer text"; Location = <Append | Prepend>; FallbackAction = <Wrap | Ignore | Reject> }`.
259
+
260
+
- Text: Specifies the disclaimer text to add. Disclaimer text can include HTML tags and inline cascading style sheet (CSS) tags. You can add images using the IMG tag.
261
+
- Location: Specifies where to insert the HTML disclaimer text in the body of messages. Append = Add to the end of the message body. Prepend = Insert at the beginning of the message body.
262
+
- FallbackAction: Specifies what to do if the HTML disclaimer can't be added to a message. Wrap = The original message is wrapped in a new message envelope, and the disclaimer is used as the message body for the new message. Ignore = The rule is ignored and the message is delivered without the disclaimer. Reject = The message is rejected.
263
+
264
+
You can use this condition in DLP policies that are scoped only to Exchange.
265
+
266
+
```yaml
267
+
Type: PswsHashtable
268
+
Parameter Sets: (All)
269
+
Aliases:
270
+
Applicable: Security & Compliance Center
271
+
272
+
Required: False
273
+
Position: Named
274
+
Default value: None
275
+
Accept pipeline input: False
276
+
Accept wildcard characters: False
277
+
```
278
+
254
279
### -BlockAccess
255
280
The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are:
The ContentCharacterSetContainsWords parameter specifies a condition for the rule that looks for character set names in messages.
354
+
The ContentCharacterSetContainsWords parameter specifies a condition for the rule that looks for character set names in messages. You can specify multiple values separated by commas.
330
355
331
-
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
The ExceptIfWithImportance parameter specifies an exception for the rule that looks for messages with the specified importance level. Valid values are:
1161
+
1162
+
- Low
1163
+
- Normal
1164
+
- High
1165
+
1166
+
You can use this exception in DLP policies that are scoped only to Exchange.
1167
+
1168
+
```yaml
1169
+
Type: WithImportance
1170
+
Parameter Sets: (All)
1171
+
Aliases:
1172
+
Applicable: Security & Compliance Center
1173
+
1174
+
Required: False
1175
+
Position: Named
1176
+
Default value: None
1177
+
Accept pipeline input: False
1178
+
Accept wildcard characters: False
1179
+
```
1180
+
1134
1181
### -ExpiryDate
1135
1182
This parameter is reserved for internal Microsoft use.
The PrependSubject parameter specifies an action for the rule that adds text to add to the beginning of the Subject field of messages. The value for this parameter is the text that you want to add. If the text contains spaces, enclose the value in quotation marks (").
1583
+
1584
+
Consider ending the value for this parameter with a colon (:) and a space, or at least a space, to separate it from the original subject.
1585
+
1586
+
You can use this condition in DLP policies that are scoped only to Exchange.
1587
+
1588
+
```yaml
1589
+
Type: String
1590
+
Parameter Sets: (All)
1591
+
Aliases:
1592
+
Applicable: Security & Compliance Center
1593
+
1594
+
Required: False
1595
+
Position: Named
1596
+
Default value: None
1597
+
Accept pipeline input: False
1598
+
Accept wildcard characters: False
1599
+
```
1600
+
1534
1601
### -Priority
1535
1602
The Priority parameter specifies a priority value for the rule that determines the order of rule processing within the policy. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
The WithImportance parameter specifies a condition for the rule that looks for messages with the specified importance level. Valid values are:
1953
+
1954
+
- Low
1955
+
- Normal
1956
+
- High
1957
+
1958
+
You can use this condition in DLP policies that are scoped only to Exchange.
1959
+
1960
+
```yaml
1961
+
Type: WithImportance
1962
+
Parameter Sets: (All)
1963
+
Aliases:
1964
+
Applicable: Security & Compliance Center
1965
+
1966
+
Required: False
1967
+
Position: Named
1968
+
Default value: None
1969
+
Accept pipeline input: False
1970
+
Accept wildcard characters: False
1971
+
```
1972
+
1884
1973
### CommonParameters
1885
1974
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).
0 commit comments