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 ContentCharacterSetContainsWords parameter specifies a condition for the rule that looks for character set names in messages.
346
+
347
+
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
348
+
349
+
```yaml
350
+
Type: MultiValuedProperty
351
+
Parameter Sets: (All)
352
+
Aliases:
353
+
Applicable: Security & Compliance Center
354
+
355
+
Required: False
356
+
Position: Named
357
+
Default value: None
358
+
Accept pipeline input: False
359
+
Accept wildcard characters: False
360
+
```
361
+
332
362
### -ContentContainsSensitiveInformation
333
363
The ContentContainsSensitiveInformation parameter specifies a condition for the rule that's based on a sensitive information type match in content. The rule is applied to content that contains the specified sensitive information type.
334
364
@@ -590,6 +620,24 @@ Accept pipeline input: False
590
620
Accept wildcard characters: False
591
621
```
592
622
623
+
### -ExceptIfContentCharacterSetContainsWords
624
+
The ExceptIfContentCharacterSetContainsWords parameter specifies an exception for the rule that looks for character set names in messages.
625
+
626
+
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
627
+
628
+
```yaml
629
+
Type: MultiValuedProperty
630
+
Parameter Sets: (All)
631
+
Aliases:
632
+
Applicable: Security & Compliance Center
633
+
634
+
Required: False
635
+
Position: Named
636
+
Default value: None
637
+
Accept pipeline input: False
638
+
Accept wildcard characters: False
639
+
```
640
+
593
641
### -ExceptIfContentContainsSensitiveInformation
594
642
The ExceptIfContentContainsSensitiveInformation parameter specifies an exception for the rule that's based on a sensitive information type match in content. The rule isn't applied to content that contains the specified sensitive information type.
595
643
@@ -812,6 +860,48 @@ Accept pipeline input: False
812
860
Accept wildcard characters: False
813
861
```
814
862
863
+
### -ExceptIfFromScope
864
+
The ExceptIfFromScope parameter specifies an exception for the rule that looks for the location of message senders. Valid values are:
865
+
866
+
- InOrganization: The sender is a mailbox, mail user, group, or mail-enabled public folder in your organization or The sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain, and the message was sent or received over an authenticated connection.
867
+
- NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain.
868
+
869
+
You can use this exception in DLP policies that are scoped only to Exchange.
870
+
871
+
```yaml
872
+
Type: FromScope
873
+
Parameter Sets: (All)
874
+
Aliases:
875
+
Applicable: Security & Compliance Center
876
+
877
+
Required: False
878
+
Position: Named
879
+
Default value: None
880
+
Accept pipeline input: False
881
+
Accept wildcard characters: False
882
+
```
883
+
884
+
### -ExceptIfHasSenderOverride
885
+
The ExceptIfHasSenderOverride parameter specifies an exception for the rule that looks for messages where the sender chose to override a DLP policy. Valid values are:
886
+
887
+
- $true: Look for messages where the sender took action to override a DLP policy.
888
+
- $false: Don't look for messages where the sender took action to override a DLP policy.
889
+
890
+
You can use this exception in DLP policies that are scoped only to Exchange.
891
+
892
+
```yaml
893
+
Type: Boolean
894
+
Parameter Sets: (All)
895
+
Aliases:
896
+
Applicable: Security & Compliance Center
897
+
898
+
Required: False
899
+
Position: Named
900
+
Default value: None
901
+
Accept pipeline input: False
902
+
Accept wildcard characters: False
903
+
```
904
+
815
905
### -ExceptIfHeaderContainsWords
816
906
The HeaderContainsWords parameter specifies an exception for the DLP rule that looks for words in a header field.
817
907
@@ -850,6 +940,33 @@ Accept pipeline input: False
850
940
Accept wildcard characters: False
851
941
```
852
942
943
+
### -ExceptIfMessageTypeMatches
944
+
The ExceptIfMessageTypeMatches parameter specifies an exception for the rule that looks for messages of the specified type. Valid values are:
945
+
946
+
- ApprovalRequest: Moderation request messages sent to moderators.
947
+
- AutomaticForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook on the web or Outlook).
948
+
- AutomaticReply: Out of office (OOF) messages configured by the user.
949
+
- Calendaring: Meeting requests and responses.
950
+
- Encrypted: Encrypted messages.
951
+
- PermissionControlled: Messages that have specific permissions configured.
952
+
- ReadReceipt: Read receipts.
953
+
- Signed: Digitally signed messages.
954
+
955
+
You can use this exception in DLP policies that are scoped only to Exchange.
956
+
957
+
```yaml
958
+
Type: MessageTypes
959
+
Parameter Sets: (All)
960
+
Aliases:
961
+
Applicable: Security & Compliance Center
962
+
963
+
Required: False
964
+
Position: Named
965
+
Default value: None
966
+
Accept pipeline input: False
967
+
Accept wildcard characters: False
968
+
```
969
+
853
970
### -ExceptIfProcessingLimitExceeded
854
971
The ExceptIfProcessingLimitExceeded parameter specifies an exception for the DLP rule that looks for files where scanning couldn't complete. Valid values are:
The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception for the rule that looks for words in the Subject field or body of messages.
1127
+
1128
+
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
1129
+
1130
+
You can use this exception in DLP policies that are scoped only to Exchange.
1131
+
1132
+
```yaml
1133
+
Type: <MultiValuedProperty>
1134
+
Parameter Sets: (All)
1135
+
Aliases:
1136
+
Applicable: Security & Compliance Center
1137
+
1138
+
Required: False
1139
+
Position: Named
1140
+
Default value: None
1141
+
Accept pipeline input: False
1142
+
Accept wildcard characters: False
1143
+
```
1144
+
1145
+
### -ExceptIfSubjectOrBodyMatchesPatterns
1146
+
The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception for the rule that looks for text patterns in the Subject field or body of messages. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
1147
+
1148
+
You can use this exception in DLP policies that are scoped only to Exchange.
1149
+
1150
+
```yaml
1151
+
Type: <MultiValuedProperty>
1152
+
Parameter Sets: (All)
1153
+
Aliases:
1154
+
Applicable: Security & Compliance Center
1155
+
1156
+
Required: False
1157
+
Position: Named
1158
+
Default value: None
1159
+
Accept pipeline input: False
1160
+
Accept wildcard characters: False
1161
+
```
1162
+
1008
1163
### -ExpiryDate
1009
1164
This parameter is reserved for internal Microsoft use.
The FromScope parameter specifies a condition for the rule that looks for the location of message senders. Valid values are:
1259
+
1260
+
- InOrganization: The sender is a mailbox, mail user, group, or mail-enabled public folder in your organization or The sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain, and the message was sent or received over an authenticated connection.
1261
+
- NotInOrganization: The sender's email address isn't in an accepted domain or the sender's email address is in an accepted domain that's configured as an external relay domain.
1262
+
1263
+
You can use this condition in DLP policies that are scoped only to Exchange.
1264
+
1265
+
```yaml
1266
+
Type: FromScope
1267
+
Parameter Sets: (All)
1268
+
Aliases:
1269
+
Applicable: Security & Compliance Center
1270
+
1271
+
Required: False
1272
+
Position: Named
1273
+
Default value: None
1274
+
Accept pipeline input: False
1275
+
Accept wildcard characters: False
1276
+
```
1277
+
1102
1278
### -GenerateAlert
1103
1279
The GenerateAlert parameter specifies an action for the DLP rule that notifies the specified users when the conditions of the rule are met. Valid values are:
The SenderOverride parameter specifies a condition for the rule that looks for messages where the sender chose to override a DLP policy. Valid values are:
1324
+
1325
+
- $true: Look for messages where the sender took action to override a DLP policy.
1326
+
- $false: Don't look for messages where the sender took action to override a DLP policy.
1327
+
1328
+
You can use this condition in DLP policies that are scoped only to Exchange.
1329
+
1330
+
```yaml
1331
+
Type: Boolean
1332
+
Parameter Sets: (All)
1333
+
Aliases:
1334
+
Applicable: Security & Compliance Center
1335
+
1336
+
Required: False
1337
+
Position: Named
1338
+
Default value: None
1339
+
Accept pipeline input: False
1340
+
Accept wildcard characters: False
1341
+
```
1342
+
1146
1343
### -HeaderContainsWords
1147
1344
The HeaderContainsWords parameter specifies a condition for the DLP rule that looks for words in a header field.
The MessageTypeMatches parameter specifies a condition for the rule that looks for messages of the specified type. Valid values are:
1438
+
1439
+
- ApprovalRequest: Moderation request messages sent to moderators.
1440
+
- AutomaticForward: Messages automatically forwarded to an alternative recipient (by Exchange, not by auto-forwarding rules that users configure in Outlook on the web or Outlook).
1441
+
- AutomaticReply: Out of office (OOF) messages configured by the user.
1442
+
- Calendaring: Meeting requests and responses.
1443
+
- Encrypted: Encrypted messages.
1444
+
- PermissionControlled: Messages that have specific permissions configured.
1445
+
- ReadReceipt: Read receipts.
1446
+
- Signed: Digitally signed messages.
1447
+
1448
+
You can use this condition in DLP policies that are scoped only to Exchange.
1449
+
1450
+
```yaml
1451
+
Type: MessageTypes
1452
+
Parameter Sets: (All)
1453
+
Aliases:
1454
+
Applicable: Security & Compliance Center
1455
+
1456
+
Required: False
1457
+
Position: Named
1458
+
Default value: None
1459
+
Accept pipeline input: False
1460
+
Accept wildcard characters: False
1461
+
```
1462
+
1239
1463
### -Moderate
1240
1464
The Moderate parameter specifies an action for the DLP rule that sends the email message to a moderator. This parameter uses the syntax: `@{ModerateMessageByManager = <$true | $false>; ModerateMessageByUser = @("emailaddress1","emailaddress2",..."emailaddressN")}`.
The SubjectOrBodyContainsWords parameter specifies a condition for the rule that looks for words in the Subject field or body of messages.
1878
+
1879
+
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
1880
+
1881
+
You can use this condition in DLP policies that are scoped only to Exchange.
1882
+
1883
+
```yaml
1884
+
Type: <MultiValuedProperty>
1885
+
Parameter Sets: (All)
1886
+
Aliases:
1887
+
Applicable: Security & Compliance Center
1888
+
1889
+
Required: False
1890
+
Position: Named
1891
+
Default value: None
1892
+
Accept pipeline input: False
1893
+
Accept wildcard characters: False
1894
+
```
1895
+
1896
+
### -SubjectOrBodyMatchesPatterns
1897
+
The SubjectOrBodyMatchesPatterns parameter specifies a condition for the rule that looks for text patterns in the Subject field or body of messages. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
1898
+
1899
+
You can use this condition in DLP policies that are scoped only to Exchange.
1900
+
1901
+
```yaml
1902
+
Type: <MultiValuedProperty>
1903
+
Parameter Sets: (All)
1904
+
Aliases:
1905
+
Applicable: Security & Compliance Center
1906
+
1907
+
Required: False
1908
+
Position: Named
1909
+
Default value: None
1910
+
Accept pipeline input: False
1911
+
Accept wildcard characters: False
1912
+
```
1913
+
1652
1914
### -WhatIf
1653
1915
The WhatIf switch doesn't work in Security & Compliance Center PowerShell.
0 commit comments