Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

Set-HostedConnectionFilterPolicy

Exchange 2013
 

Applies to: Exchange Online Protection, Exchange Online

Topic Last Modified: 2012-12-14

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

Use the Set-HostedConnectionFilterPolicy cmdlet to modify the settings of connection filter policies in your cloud-based organization.

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

Set-HostedConnectionFilterPolicy -Identity <HostedConnectionFilterPolicyIdParameter> [-AdminDisplayName <String>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-EnableSafeList <$true | $false>] [-IgnoreDehydratedFlag <SwitchParameter>] [-IPAllowList <MultiValuedProperty>] [-IPBlockList <MultiValuedProperty>] [-MakeDefault <SwitchParameter>] [-Name <String>] [-WhatIf [<SwitchParameter>]]

This example modifies the connection filter policy named Contoso Connection Filter Policy with the following settings:

  • Messages from 192.168.1.10 and 192.168.1.23 are never identified as spam.

  • Messages from 10.10.10.10/24 and 172.17.17.0/16 are always identified as spam.

Set-HostedConnectionFilterPolicy "Contoso Connection Filter Policy" -IPAllowList 192.168.1.10,192.168.1.23 -IPBlockList 10.10.10.10/24,172.17.17.0/16

This example modifies the connection filter policy named Contoso Connection Filter Policy with the following settings:

  • The following IP addresses are added to the existing values in the IP allow list: 192.168.2.10, 192.169.3.0/18, and 192.168.4.1-192.168.4.5.

  • The IP address 192.168.1.10 is removed from the existing values in the IP allow list.

Set-HostedConnectionFilterPolicy "Contoso Connection Filter Policy" -IPAllowList @{Add="192.168.2.10","192.169.3.0/18","192.168.4.1-192.168.4.5";Remove="192.168.1.10"}

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

Identity

Required

Microsoft.Exchange.Configuration.Tasks.HostedConnectionFilterPolicyIdParameter

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

AdminDisplayName

Optional

System.String

The AdminDisplayName parameter specifies a description for the connection filter policy. If the value contains spaces, enclose the value in quotation marks (").

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

This parameter is reserved for internal Microsoft use.

EnableSafeList

Optional

System.Boolean

The EnableSafeList parameter enables or disables use of the safe list. The safe list is a dynamic allow list in the Microsoft datacenter that requires no customer configuration. Valid input for this parameter is $true or $false. The default value is $false.

IgnoreDehydratedFlag

Optional

System.Management.Automation.SwitchParameter

This parameter is reserved for internal Microsoft use.

IPAllowList

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The IPAllowList parameter specifies IP addresses from which messages are always allowed. Messages from the IP addresses you specify won't be identified as spam, despite any other spam characteristics of the messages.

You enter the IP addresses using the following syntax:

  • Single IP   For example, 192.168.1.1.

  • IP range   You can use an IP address range, for example, 192.168.0.1-192.168.0.254.

  • CIDR IP   You can use Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25.

You can specify multiple IP addresses of the same type separated by commas. For example, <single IP1>, <single IP2> or <CIDR IP1>, <CIDR IP2>. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: @{Add="<single IP1>","<IP range1>",<CIDR IP1>...}.

IPBlockList

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The IPBlockList parameter specifies IP addresses from which messages are never allowed. Messages from the IP addresses you specify are blocked without any further spam scanning.

You enter the IP addresses using the following syntax:

  • Single IP   For example, 192.168.1.1.

  • IP range   You can use an IP address range, for example, 192.168.0.1-192.168.0.254.

  • CIDR IP   You can use Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25.

You can specify multiple IP addresses of the same type separated by commas. For example, <single IP1>, <single IP2> or <CIDR IP1>, <CIDR IP2>. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: @{Add="<single IP1>","<IP range1>",<CIDR IP1>...}.

MakeDefault

Optional

System.Management.Automation.SwitchParameter

The MakeDefault switch makes the specified policy the default connection filter policy. You don't have to specify a value with this switch.

Name

Optional

System.String

The Name parameter specifies a unique name for the connection filter policy.

WhatIf

Optional

System.Management.Automation.SwitchParameter

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.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.