Export (0) Print
Expand All
Expand Minimize


Exchange 2013

Applies to: Exchange Online Protection, Exchange Online

Topic Last Modified: 2014-03-20

This cmdlet is available only in the cloud-based service.

Use the Remove-HostedContentFilterPolicy cmdlet to remove content filter policies from your cloud-based organization.

When a policy is removed and there are rules associated with it, the rules are not removed when the policy is removed. This is by design. If you want to remove the associated rules, you need to do this separately via the Remove-HostedContentFilterRule cmdlet.

For information about the parameter sets in the Syntax section below, see Syntax.

Remove-HostedContentFilterPolicy -Identity <HostedContentFilterPolicyIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

This example removes the content filter policy named Contoso Content Filter Policy.

Remove-HostedContentFilterPolicy "Contoso Content Filter Policy"

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Anti-spam" entry in the Feature permissions in Exchange Online topic.


Parameter Required Type Description




The Identity parameter specifies the content filter policy you want to remove. You can use any value that uniquely identifies the policy, For example, you can use the name, GUID or distinguished name (DN) of the content filter policy.




The Confirm switch can be used to suppress the confirmation prompt that appears by default when this cmdlet is run. To suppress the confirmation prompt, use the syntax -Confirm:$False. You must include a colon ( : ) in the syntax.




This parameter is reserved for internal Microsoft use.




The Force switch specifies whether to suppress warning or confirmation messages. This switch can be used when the task is run programmatically and prompting for administrative input is inappropriate. If the Force switch isn't provided in the command, you're prompted for administrative input. You don't have to specify a value with this parameter.




The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft