Skip to content

Commit 6d860fb

Browse files
chrisdachrisda
committed
Revert "Removed preset security policy cmdlets"
This reverts commit 9a9c792.
1 parent 9a9c792 commit 6d860fb

17 files changed

+2887
-0
lines changed

‎exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md

Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://docs.microsoft.com/powershell/module/exchange/disable-atpprotectionpolicyrule
4+
applicable: Exchange Online, Exchange Online Protection
5+
title: Disable-ATPProtectionPolicyRule
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Disable-ATPProtectionPolicyRule
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the cloud-based service.
16+
17+
Use the Disable-ATPProtectionPolicyRule and Disable-EOPProtectionPolicyRule cmdlets together to turn off the Standard preset security policy or the Strict preset security policy in organizations with Microsoft Defender for Office 365.
18+
19+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20+
21+
## SYNTAX
22+
23+
```
24+
Disable-ATPProtectionPolicyRule [-Identity] <RuleIdParameter>
25+
[-Confirm]
26+
[-WhatIf]
27+
[<CommonParameters>]
28+
```
29+
30+
## DESCRIPTION
31+
The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled.
32+
33+
For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://docs.microsoft.com/microsoft-365/security/office-365-security/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
34+
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://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
36+
37+
## EXAMPLES
38+
39+
### Example 1
40+
```powershell
41+
Disable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Disable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"
42+
```
43+
44+
In organizations with Defender for Office 365, this example turns off the Standard preset security policy. The State property value of both rules is now Disabled.
45+
46+
## PARAMETERS
47+
48+
### -Identity
49+
The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
50+
51+
- Name
52+
- Distinguished name (DN)
53+
- GUID
54+
55+
By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy.
56+
57+
```yaml
58+
Type: RuleIdParameter
59+
Parameter Sets: (All)
60+
Aliases:
61+
Applicable: Exchange Online, Exchange Online Protection
62+
63+
Required: True
64+
Position: 0
65+
Default value: None
66+
Accept pipeline input: True (ByPropertyName, ByValue)
67+
Accept wildcard characters: False
68+
```
69+
70+
### -Confirm
71+
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.
72+
73+
- 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.
74+
- 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.
75+
76+
```yaml
77+
Type: SwitchParameter
78+
Parameter Sets: (All)
79+
Aliases: cf
80+
Applicable: Exchange Online, Exchange Online Protection
81+
82+
Required: False
83+
Position: Named
84+
Default value: None
85+
Accept pipeline input: False
86+
Accept wildcard characters: False
87+
```
88+
89+
### -WhatIf
90+
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
91+
92+
```yaml
93+
Type: SwitchParameter
94+
Parameter Sets: (All)
95+
Aliases: wi
96+
Applicable: Exchange Online, Exchange Online Protection
97+
98+
Required: False
99+
Position: Named
100+
Default value: None
101+
Accept pipeline input: False
102+
Accept wildcard characters: False
103+
```
104+
105+
### CommonParameters
106+
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).
107+
108+
## INPUTS
109+
110+
## OUTPUTS
111+
112+
## NOTES
113+
114+
## RELATED LINKS

‎exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://docs.microsoft.com/powershell/module/exchange/disable-eopprotectionpolicyrule
4+
applicable: Exchange Online, Exchange Online Protection
5+
title: Disable-EOPProtectionPolicyRule
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Disable-EOPProtectionPolicyRule
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the cloud-based service.
16+
17+
Use the Disable-EOPProtectionPolicyRule cmdlet to turn off the Standard preset security policy or the Strict preset security policy. If your organization has Defender for Office 365, you also need to use the Disable-ATPProtectionPolicyRule cmdlet to turn off the policy.
18+
19+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20+
21+
## SYNTAX
22+
23+
```
24+
Disable-EOPProtectionPolicyRule [-Identity] <RuleIdParameter>
25+
[-Confirm]
26+
[-WhatIf]
27+
[<CommonParameters>]
28+
```
29+
30+
## DESCRIPTION
31+
The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled.
32+
33+
For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://docs.microsoft.com/microsoft-365/security/office-365-security/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
34+
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://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
36+
37+
## EXAMPLES
38+
39+
### Example 1
40+
```powershell
41+
Disable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"
42+
```
43+
44+
In organizations without Defender for Office 365, this example turns off the Standard preset security policy. The State property value of the rule is now Disabled.
45+
46+
### Example 2
47+
```powershell
48+
Disable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Disable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy"
49+
```
50+
51+
In organizations with Defender for Office 365, this example turns off the Standard preset security policy. The State property value of both rules is now Disabled.
52+
53+
## PARAMETERS
54+
55+
### -Identity
56+
The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
57+
58+
- Name
59+
- Distinguished name (DN)
60+
- GUID
61+
62+
By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy.
63+
64+
```yaml
65+
Type: RuleIdParameter
66+
Parameter Sets: (All)
67+
Aliases:
68+
Applicable: Exchange Online, Exchange Online Protection
69+
70+
Required: True
71+
Position: 0
72+
Default value: None
73+
Accept pipeline input: True (ByPropertyName, ByValue)
74+
Accept wildcard characters: False
75+
```
76+
77+
### -Confirm
78+
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.
79+
80+
- 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.
81+
- 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.
82+
83+
```yaml
84+
Type: SwitchParameter
85+
Parameter Sets: (All)
86+
Aliases: cf
87+
Applicable: Exchange Online, Exchange Online Protection
88+
89+
Required: False
90+
Position: Named
91+
Default value: None
92+
Accept pipeline input: False
93+
Accept wildcard characters: False
94+
```
95+
96+
### -WhatIf
97+
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
98+
99+
```yaml
100+
Type: SwitchParameter
101+
Parameter Sets: (All)
102+
Aliases: wi
103+
Applicable: Exchange Online, Exchange Online Protection
104+
105+
Required: False
106+
Position: Named
107+
Default value: None
108+
Accept pipeline input: False
109+
Accept wildcard characters: False
110+
```
111+
112+
### CommonParameters
113+
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).
114+
115+
## INPUTS
116+
117+
## OUTPUTS
118+
119+
## NOTES
120+
121+
## RELATED LINKS

‎exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md

Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://docs.microsoft.com/powershell/module/exchange/enable-atpprotectionpolicyrule
4+
applicable: Exchange Online, Exchange Online Protection
5+
title: Enable-ATPProtectionPolicyRule
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Enable-ATPProtectionPolicyRule
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in the cloud-based service.
16+
17+
Use the Enable-ATPProtectionPolicyRule and Enable-EOPProtectionPolicyRule cmdlets together to turn on the Standard preset security policy or the Strict preset security policy in organizations with Microsoft Defender for Office 365.
18+
19+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20+
21+
## SYNTAX
22+
23+
```
24+
Enable-ATPProtectionPolicyRule [-Identity] <RuleIdParameter>
25+
[-Confirm]
26+
[-WhatIf]
27+
[<CommonParameters>]
28+
```
29+
30+
## DESCRIPTION
31+
The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled.
32+
33+
For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://docs.microsoft.com/microsoft-365/security/office-365-security/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
34+
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://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
36+
37+
## EXAMPLES
38+
39+
### Example 1
40+
```powershell
41+
Enable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Enable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"
42+
```
43+
44+
In organizations with Defender for Office 365, this example turns on the Standard preset security policy. The State value of both rules is now Enabled.
45+
46+
## PARAMETERS
47+
48+
### -Identity
49+
The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
50+
51+
- Name
52+
- Distinguished name (DN)
53+
- GUID
54+
55+
By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy.
56+
57+
```yaml
58+
Type: RuleIdParameter
59+
Parameter Sets: (All)
60+
Aliases:
61+
Applicable: Exchange Online, Exchange Online Protection
62+
63+
Required: True
64+
Position: 0
65+
Default value: None
66+
Accept pipeline input: True (ByPropertyName, ByValue)
67+
Accept wildcard characters: False
68+
```
69+
70+
### -Confirm
71+
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.
72+
73+
- 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.
74+
- 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.
75+
76+
```yaml
77+
Type: SwitchParameter
78+
Parameter Sets: (All)
79+
Aliases: cf
80+
Applicable: Exchange Online, Exchange Online Protection
81+
82+
Required: False
83+
Position: Named
84+
Default value: None
85+
Accept pipeline input: False
86+
Accept wildcard characters: False
87+
```
88+
89+
### -WhatIf
90+
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
91+
92+
```yaml
93+
Type: SwitchParameter
94+
Parameter Sets: (All)
95+
Aliases: wi
96+
Applicable: Exchange Online, Exchange Online Protection
97+
98+
Required: False
99+
Position: Named
100+
Default value: None
101+
Accept pipeline input: False
102+
Accept wildcard characters: False
103+
```
104+
105+
### CommonParameters
106+
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).
107+
108+
## INPUTS
109+
110+
## OUTPUTS
111+
112+
## NOTES
113+
114+
## RELATED LINKS

0 commit comments

Comments
 (0)