Enable-EOPProtectionPolicyRule
This cmdlet is available only in the cloud-based service.
Use the Enable-EOPProtectionPolicyRule cmdlet to turn on 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 Enable-ATPProtectionPolicyRule cmdlet to turn on the policy.
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax.
Syntax
Enable-EOPProtectionPolicyRule
[-Identity] <RuleIdParameter>
[-Confirm]
[-WhatIf]
[<CommonParameters>] Description
The State property in rules that are associated with preset security policies indicates whether the rule is Enabled or Disabled.
For more information about preset security policies in PowerShell, see Preset security policies in Exchange Online PowerShell.
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.
Examples
Example 1
Enable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"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 Enabled.
Example 2
Enable-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy"; Enable-ATPProtectionPolicyRule -Identity "Standard Preset Security Policy"In organizations with Defender for Office 365, this example turns on the Standard preset security policy. The State property value of both rules is now Enabled.
Parameters
-Confirm
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.
- 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.
- 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.
| Type: | SwitchParameter |
| Aliases: | cf |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-Identity
The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
- Distinguished name (DN)
- GUID
By default, the available rules (if they exist) are named Standard Preset Security Policy and Strict Preset Security Policy.
| Type: | RuleIdParameter |
| Position: | 0 |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | True |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-WhatIf
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.
| Type: | SwitchParameter |
| Aliases: | wi |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |