Skip to content

Commit b645cac

Browse files
chrisdachrisda
authored
Merge pull request #11572 from MicrosoftDocs/ExOSecOps-chrisda
ExOSecOps-chrisda to Main
2 parents 9525808 + 9c8480a commit b645cac

10 files changed

+458
-320
lines changed

‎.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6944,6 +6944,21 @@
69446944
"source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentReport.md",
69456945
"redirect_url": "/powershell/module/exchange/get-contentmalwaremdoaggregatereport",
69466946
"redirect_document_id": false
6947+
},
6948+
{
6949+
"source_path": "exchange/virtual-folder/exchange/New-SecOpsOverrideRule.md",
6950+
"redirect_url": "/powershell/module/exchange/new-exosecopsoverriderule",
6951+
"redirect_document_id": false
6952+
},
6953+
{
6954+
"source_path": "exchange/virtual-folder/exchange/Remove-SecOpsOverrideRule.md",
6955+
"redirect_url": "/powershell/module/exchange/remove-exosecopsoverriderule",
6956+
"redirect_document_id": false
6957+
},
6958+
{
6959+
"source_path": "exchange/virtual-folder/exchange/Set-SecOpsOverrideRule.md",
6960+
"redirect_url": "/powershell/module/exchange/set-exosecopsoverriderule",
6961+
"redirect_document_id": false
69476962
}
69486963
]
69496964
}

‎exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md

Lines changed: 144 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,144 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://learn.microsoft.com/powershell/module/exchange/get-exosecopsoverriderule
4+
applicable: Exchange Online, Exchange Online Protection
5+
title: Get-ExOSecOpsOverrideRule
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Get-ExoSecOpsOverrideRule
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the cloud-based service.
16+
17+
Use the Get-ExOSecOpsOverrideRule cmdlet to view SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/microsoft-365/security/office-365-security/advanced-delivery-policy-configure).
18+
19+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20+
21+
## SYNTAX
22+
23+
```
24+
Get-ExoSecOpsOverrideRule [[-Identity] <ComplianceRuleIdParameter>]
25+
[-Confirm]
26+
[-DomainController <Fqdn>]
27+
[-Policy <Object>]
28+
[-WhatIf]
29+
[<CommonParameters>]
30+
```
31+
32+
## DESCRIPTION
33+
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
34+
35+
## EXAMPLES
36+
37+
### Example 1
38+
```powershell
39+
Get-ExOSecOpsOverrideRule
40+
```
41+
42+
This example returns detailed information about the one and only SecOps mailbox override rule.
43+
44+
## PARAMETERS
45+
46+
### -Identity
47+
The Identity parameter specifies the SecOps override rule that you want to view. You can use any value that uniquely identifies the rule. For example:
48+
49+
- Name
50+
- Id
51+
- Distinguished name (DN)
52+
- GUID
53+
54+
```yaml
55+
Type: ComplianceRuleIdParameter
56+
Parameter Sets: (All)
57+
Aliases:
58+
Applicable: Exchange Online, Exchange Online Protection
59+
60+
Required: False
61+
Position: 1
62+
Default value: None
63+
Accept pipeline input: True (ByPropertyName, ByValue)
64+
Accept wildcard characters: False
65+
```
66+
67+
### -Confirm
68+
This parameter is reserved for internal Microsoft use.
69+
70+
```yaml
71+
Type: SwitchParameter
72+
Parameter Sets: (All)
73+
Aliases: cf
74+
75+
Required: False
76+
Position: Named
77+
Default value: None
78+
Accept pipeline input: False
79+
Accept wildcard characters: False
80+
```
81+
82+
### -DomainController
83+
This parameter is reserved for internal Microsoft use.
84+
85+
```yaml
86+
Type: Fqdn
87+
Parameter Sets: (All)
88+
Aliases:
89+
Applicable: Exchange Online, Exchange Online Protection
90+
91+
Required: False
92+
Position: Named
93+
Default value: None
94+
Accept pipeline input: False
95+
Accept wildcard characters: False
96+
```
97+
98+
### -Policy
99+
The Policy parameter filters the results by SecOps mailbox override policy. You can use any value that uniquely identifies the policy. For example:
100+
101+
- Name
102+
- Id
103+
- Distinguished name (DN)
104+
- GUID
105+
106+
```yaml
107+
Type: PolicyIdParameter
108+
Parameter Sets: (All)
109+
Aliases:
110+
Applicable: Exchange Online, Exchange Online Protection
111+
112+
Required: False
113+
Position: Named
114+
Default value: None
115+
Accept pipeline input: False
116+
Accept wildcard characters: False
117+
```
118+
119+
### -WhatIf
120+
This parameter is reserved for internal Microsoft use.
121+
122+
```yaml
123+
Type: SwitchParameter
124+
Parameter Sets: (All)
125+
Aliases: wi
126+
Applicable: Exchange Online, Exchange Online Protection
127+
128+
Required: False
129+
Position: Named
130+
Default value: None
131+
Accept pipeline input: False
132+
Accept wildcard characters: False
133+
```
134+
135+
### CommonParameters
136+
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).
137+
138+
## INPUTS
139+
140+
## OUTPUTS
141+
142+
## NOTES
143+
144+
## RELATED LINKS

‎exchange/exchange-ps/exchange/Get-SecOpsOverrideRule.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.reviewer:
1212
# Get-SecOpsOverrideRule
1313

1414
## SYNOPSIS
15+
**Note**: The \*-SecOpsOverrideRule cmdlets in Security & Compliance PowerShell have been replaced by the \*-ExOSecOpsOverrideRule cmdlets in Exchange Online PowerShell.
16+
1517
This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
1618

1719
Use the Get-SecOpsOverrideRule cmdlet to view SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/microsoft-365/security/office-365-security/advanced-delivery-policy-configure).

‎exchange/exchange-ps/exchange/New-SecOpsOverrideRule.md renamed to ‎exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md

Lines changed: 31 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,64 +1,50 @@
11
---
22
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3-
online version: https://learn.microsoft.com/powershell/module/exchange/new-secopsoverriderule
4-
applicable: Security & Compliance
5-
title: New-SecOpsOverrideRule
3+
online version: https://learn.microsoft.com/powershell/module/exchange/new-exosecopsoverriderule
4+
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
5+
title: New-ExOSecOpsOverrideRule
66
schema: 2.0.0
77
author: chrisda
88
ms.author: chrisda
99
ms.reviewer:
1010
---
1111

12-
# New-SecOpsOverrideRule
12+
# New-ExoSecOpsOverrideRule
1313

1414
## SYNOPSIS
15-
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
15+
This cmdlet is available only in the cloud-based service.
1616

17-
Use the New-SecOpsOverrideRule cmdlet to create SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/microsoft-365/security/office-365-security/advanced-delivery-policy-configure).
17+
Use the New-ExOSecOpsOverrideRule cmdlet to create SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/microsoft-365/security/office-365-security/advanced-delivery-policy-configure).
1818

1919
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2020

2121
## SYNTAX
2222

23+
### Default
2324
```
24-
New-SecOpsOverrideRule [-Name] <String> -Policy <PolicyIdParameter>
25+
New-ExoSecOpsOverrideRule -Policy <PolicyIdParametert>
2526
[-Comment <String>]
2627
[-Confirm]
27-
[-SentTo <MultiValuedProperty>]
28+
[-DomainController <Fqdn>]
29+
[-Name <String>]
2830
[-WhatIf]
2931
[<CommonParameters>]
3032
```
3133

3234
## DESCRIPTION
33-
You need to be assigned permissions in the Security & Compliance before you can use this cmdlet. For more information, see [Permissions in the Security & Compliance](https://learn.microsoft.com/microsoft-365/security/office-365-security/scc-permissions).
35+
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
3436

3537
## EXAMPLES
3638

3739
### Example 1
3840
```powershell
39-
New-SecOpsOverrideRule -Name SecOpsOverrideRule -Policy SecOpsOverridePolicy
41+
New-ExOSecOpsOverrideRule -Policy SecOpsOverridePolicy
4042
```
4143

4244
This example creates the SecOps mailbox override rule with the specified settings.
4345

4446
## PARAMETERS
4547

46-
### -Name
47-
The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be SecOpsOverrideRule\<GUID\> where \<GUID\> is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
48-
49-
```yaml
50-
Type: String
51-
Parameter Sets: Default
52-
Aliases:
53-
Applicable: Security & Compliance
54-
55-
Required: True
56-
Position: 0
57-
Default value: None
58-
Accept pipeline input: False
59-
Accept wildcard characters: False
60-
```
61-
6248
### -Policy
6349
The Policy parameter specifies the phishing simulation override policy that's associated with the rule. You can use any value that uniquely identifies the policy. For example:
6450

@@ -71,7 +57,6 @@ The Policy parameter specifies the phishing simulation override policy that's as
7157
Type: PolicyIdParameter
7258
Parameter Sets: Default, PublishComplianceTag, ComplianceTag, SetRawXml
7359
Aliases:
74-
Applicable: Security & Compliance
7560

7661
Required: True
7762
Position: Named
@@ -87,7 +72,6 @@ The Comment parameter specifies an optional comment. If you specify a value that
8772
Type: String
8873
Parameter Sets: Default
8974
Aliases:
90-
Applicable: Security & Compliance
9175

9276
Required: False
9377
Position: Named
@@ -97,16 +81,12 @@ Accept wildcard characters: False
9781
```
9882
9983
### -Confirm
100-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
101-
102-
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
103-
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
84+
This parameter is reserved for internal Microsoft use.
10485
10586
```yaml
10687
Type: SwitchParameter
10788
Parameter Sets: (All)
10889
Aliases: cf
109-
Applicable: Security & Compliance
11090

11191
Required: False
11292
Position: Named
@@ -115,14 +95,28 @@ Accept pipeline input: False
11595
Accept wildcard characters: False
11696
```
11797
118-
### -SentTo
98+
### -DomainController
11999
This parameter is reserved for internal Microsoft use.
120100
121101
```yaml
122-
Type: MultiValuedProperty
102+
Type: Fqdn
103+
Parameter Sets: (All)
104+
Aliases:
105+
106+
Required: False
107+
Position: Named
108+
Default value: None
109+
Accept pipeline input: False
110+
Accept wildcard characters: False
111+
```
112+
113+
### -Name
114+
The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:SecOpsOverrid:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
115+
116+
```yaml
117+
Type: String
123118
Parameter Sets: Default
124119
Aliases:
125-
Applicable: Security & Compliance
126120
127121
Required: False
128122
Position: Named
@@ -132,13 +126,12 @@ Accept wildcard characters: False
132126
```
133127

134128
### -WhatIf
135-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
129+
This parameter is reserved for internal Microsoft use.
136130

137131
```yaml
138132
Type: SwitchParameter
139133
Parameter Sets: (All)
140134
Aliases: wi
141-
Applicable: Security & Compliance
142135
143136
Required: False
144137
Position: Named

0 commit comments

Comments
 (0)