Set-InboundConnector
Applies to: Exchange Online
Topic Last Modified: 2013-04-16
This cmdlet is available only in the cloud-based service.
Use the Set-InboundConnector cmdlet to change an existing Inbound connector in your cloud-based organization.
For information about the parameter sets in the Syntax section below, see Syntax.
Set-InboundConnector -Identity <InboundConnectorIdParameter> [-AssociatedAcceptedDomains <MultiValuedProperty>] [-BypassValidation <$true | $false>] [-CloudServicesMailEnabled <$true | $false>] [-Comment <String>] [-Confirm [<SwitchParameter>]] [-ConnectorSource <Default | Migrated | HybridWizard>] [-ConnectorType <OnPremises | Partner>] [-DomainController <Fqdn>] [-Enabled <$true | $false>] [-Name <String>] [-RequireTls <$true | $false>] [-RestrictDomainsToCertificate <$true | $false>] [-RestrictDomainsToIPAddresses <$true | $false>] [-SafeListIPAddresses <$true | $false>] [-SenderDomains <MultiValuedProperty>] [-SenderIPAddresses <MultiValuedProperty>] [-TlsSenderCertificateName <TlsCertificate>] [-WhatIf [<SwitchParameter>]]
This example makes the following configuration changes to the existing Inbound connector named Contoso.com Inbound Connector.
-
Require TLS transmission for all incoming messages on the connector.
-
Require that the TLS certificate that is used to encrypt communications contain the domain name contoso.com
Set-InboundConnector "Contoso Inbound Connector" -RequireTls $true -TlsSenderCertificateName contoso.com
Inbound connectors accept email messages from remote domains that require specific configuration options.
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 "Inbound and Outbound connectors" entry in the Feature Permissions in Exchange Online topic.
| Parameter | Required | Type | Description |
|---|---|---|---|
| Identity | Required | Microsoft.Exchange.Configuration.Tasks.InboundConnectorIdParameter | The Identity parameter specifies the Inbound connector you want to change. |
| AssociatedAcceptedDomains | Optional | Microsoft.Exchange.Data.MultiValuedProperty | The AssociatedAcceptedDomains parameter specifies the accepted domains that the connector applies to, thereby limiting its scope. For example, you can apply the connector to a specific accepted domain in your organization, such as contoso.com. |
| BypassValidation | Optional | System.Boolean | This parameter is reserved for internal Microsoft use. |
| CloudServicesMailEnabled | Optional | System.Boolean | Set to |
| Comment | Optional | System.String | The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: |
| 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. |
| ConnectorSource | Optional | Microsoft.Exchange.Data.TenantConnectorSource | The ConnectorSource parameter specifies how the connector was created. Valid input for this parameter includes the following values:
The default value for connectors you create is |
| ConnectorType | Optional | Microsoft.Exchange.Data.TenantConnectorType | The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid input for this parameter includes the following values:
|
| DomainController | Optional | Microsoft.Exchange.Data.Fqdn | This parameter is reserved for internal Microsoft use. |
| Enabled | Optional | System.Boolean | The Enabled parameter enables or disables the connector. Valid input for this parameter is |
| Name | Optional | System.String | The Name parameter specifies a descriptive name for the connector. |
| RequireTls | Optional | System.Boolean | The RequireTLS parameter specifies that all messages received by this connector require TLS transmission. Valid values for this parameter are |
| RestrictDomainsToCertificate | Optional | System.Boolean | The RestrictDomainsToCertificate parameter, when set to |
| RestrictDomainsToIPAddresses | Optional | System.Boolean | The RestrictDomainsToIPAddresses parameter, when set to Valid input for this parameter is |
| SafeListIPAddresses | Optional | System.Boolean | The SafeListIPAddresses parameter includes or exempts the IP addresses specified by the SenderIPAddresses parameter from anti-spam filtering. Valid input for this parameter is |
| SenderDomains | Optional | Microsoft.Exchange.Data.MultiValuedProperty | The SenderDomains parameter specifies the remote domains from which this connector accepts messages, thereby limiting its scope. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: You can specify multiple domains separated by commas. |
| SenderIPAddresses | Optional | Microsoft.Exchange.Data.MultiValuedProperty | The SenderIPAddresses parameter specifies the remote IP addresses from which this connector accepts messages. You enter the IP addresses using the following syntax:
You can specify multiple IP addresses separated by commas. |
| TlsSenderCertificateName | Optional | Microsoft.Exchange.Data.TlsCertificate | The TlsSenderCertificateName parameter specifies the certificate used by the sender’s domain when the RequireTls parameter is set to You can't embed a wildcard character, as shown in the following example: |
| 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.
