An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title		Description	Details
	RecipientDomains	The RecipientDomains parameter specifies the domain names to which the Outbound connector routes mail. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: .contoso.com. However, you can't embed a wildcard character, as shown in the following example: domain..contoso.com.You can specify multiple domains separated by commas.	Field Name: RecipientDomains.[n] Type: Array
	SmartHosts	The SmartHosts parameter specifies the smart hosts the Outbound connector uses to route mail. This parameter is required if you set the UseMxRecord parameter to $false and must be specified on the same command line. The SmartHosts parameter takes one or more FQDNs, such as server.contoso.com, or one or more IP addresses, or a combination of both FQDNs and IP addresses. Separate each value by using a comma. If you enter an IP address, you may enter the IP address as a literal, for example: 10.10.1.1, or using Classless InterDomain Routing (CIDR), for example, 192.168.0.1/25. The smart host identity can be the FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record.	Field Name: SmartHosts.[n] Type: Array
AdminDisplayName			Field Name: AdminDisplayName Type: String
OrganizationId			Field Name: OrganizationId Type: String
	ValidationRecipients	PARAMVALUE: String[]	Field Name: ValidationRecipients.[n] Type: Array
TlsSettings		The TlsSettings parameter specifies the TLS authentication level that's used for outbound TLS connections established by this Outbound connector. Valid values are: EncryptionOnly TLS is used only to encrypt the communication channel. No certificate authentication is performed. CertificateValidation TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed. DomainValidation In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter.	Field Name: TlsSettings Type: String
WhenCreatedUTC			Field Name: WhenCreatedUTC Type: String Format: date-time
PSShowComputerName			Field Name: PSShowComputerName Type: Boolean
CloudServicesMailEnabled		Note: We recommend that you don't use this parameter unless you are directed to do so by Microsoft Customer Service and Support, or by specific product documentation. Instead, use the Hybrid Configuration wizard to configure mail flow between your on-premises and cloud organizations. For more information, see Hybrid Configuration wizard. The CloudServicesMailEnabled parameter specifies whether the connector is used for hybrid mail flow between an on-premises Exchange environment and Microsoft Office 365. Specifically, this parameter controls how certain internal X-MS-Exchange-Organization-* message headers are handled in messages that are sent between accepted domains in the on-premises and cloud organizations. These headers are collectively known as cross-premises headers. Valid values are: • Promoted for inbound messagesX-MS-Exchange-CrossPremises-* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-* headers that already exist in messages. $false The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.	Field Name: CloudServicesMailEnabled Type: Boolean
	ObjectClass		Field Name: ObjectClass.[n] Type: Array
PSComputerName			Field Name: PSComputerName Type: String
LinkForModifiedConnector		PARAMVALUE: Guid	Field Name: LinkForModifiedConnector Type: String
IsTransportRuleScoped		The IsTransportRuleScoped parameter associates the Outbound connector with a transport rule. Valid input for this parameter is $true or $false. A transport rule is scoped to a specific Outbound connector using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations using the specified Outbound connector.	Field Name: IsTransportRuleScoped Type: Boolean
ConnectorSource		The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values: Default: The connector is manually created. HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard. Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange. The default value for connectors you create is Default. It isn't recommended that you change this value.	Field Name: ConnectorSource Type: String
RouteAllMessagesViaOnPremises		The RouteAllMessagesViaOnPremises parameter indicates all messages serviced by this connector are first routed through the on-premises messaging system. Valid input for this parameter is $true or $false. The default value is $false. If you set RouteAllMessagesViaOnPremises to $true, you must set the value of the ConnectorType parameter to OnPremises in the same command.	Field Name: RouteAllMessagesViaOnPremises Type: Boolean
ConnectorType		The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid input for this parameter includes the following values: Partner: The connector services domains that are external to your organization. OnPremises: The connector services domains that are used by your on-premises organization.	Field Name: ConnectorType Type: String
Identity		The Identity parameter specifies the Outbound connector you want to view.	Field Name: Identity Type: String
TestMode		PARAMVALUE: $true \| $false	Field Name: TestMode Type: Boolean
DistinguishedName			Field Name: DistinguishedName Type: String
IsValidated		PARAMVALUE: $true \| $false	Field Name: IsValidated Type: Boolean
OriginatingServer			Field Name: OriginatingServer Type: String
Name *		The Name parameter specifies a descriptive name for the connector.	Field Name: Name Type: String
LastValidationTimestamp		PARAMVALUE: DateTime	Field Name: LastValidationTimestamp Type: String Format: date-time
AllAcceptedDomains		When this parameter is set to $true, the connector applies to all accepted domains.	Field Name: AllAcceptedDomains Type: Boolean
Enabled		The Enabled parameter enables or disables the connector. Valid input for this parameter is $true or $false. The default value is $true.	Field Name: Enabled Type: Boolean
WhenCreated			Field Name: WhenCreated Type: String Format: date-time
ExchangeVersion			Field Name: ExchangeVersion Type: String
RunspaceId			Field Name: RunspaceId Type: String
TlsDomain		The TlsDomain parameter specifies the domain name that the Outbound connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection. This parameter is only used if the TlsSettings parameter is set to DomainValidation. Valid input for the TlsDomain parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: .contoso.com. However, you can't embed a wildcard character, as shown in the following example: domain..contoso.com	Field Name: TlsDomain Type: String
Comment		The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".	Field Name: Comment Type: String
ObjectCategory			Field Name: ObjectCategory Type: String
IsValid			Field Name: IsValid Type: Boolean
WhenChanged			Field Name: WhenChanged Type: String Format: date-time
WhenChangedUTC			Field Name: WhenChangedUTC Type: String Format: date-time
ObjectState			Field Name: ObjectState Type: String
UseMXRecord		The UseMXRecord parameter enables or disables DNS routing for the connector. Valid input for this parameter is $true or $false. The default value is $true. To bypass DNS routing and use a smart host as the destination for the connector, set the value of UseMXRecord to $false and specify the FQDN or IP address of the smart host using the SmartHosts parameter in the same command.	Field Name: UseMXRecord Type: Boolean
Guid			Field Name: Guid Type: String
Id			Field Name: Id Type: String

Model: device/exchangeonline/OutboundConnector

Model Details: device/exchangeonline/OutboundConnector