Applies to: Exchange Server 2013

Topic Last Modified: 2012-10-15

Use the New-HybridConfiguration cmdlet to create the HybridConfiguration object and set up a hybrid deployment between your on-premises Exchange organization and a Microsoft Office 365 for enterprises Exchange Online organization.

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

Syntax


`New-HybridConfiguration [-ClientAccessServers <MultiValuedProperty>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Domains <MultiValuedProperty>] [-EdgeTransportServers <MultiValuedProperty>] [-ExternalIPAddresses <MultiValuedProperty>] [-Features <MultiValuedProperty>] [-OnPremisesSmartHost <SmtpDomain>] [-ReceivingTransportServers <MultiValuedProperty>] [-SendingTransportServers <MultiValuedProperty>] [-TlsCertificateName <SmtpX509Identifier>] [-WhatIf [<SwitchParameter>]]`

New-HybridConfiguration [-ClientAccessServers
<MultiValuedProperty>] [-Confirm [<SwitchParameter>]]
[-DomainController <Fqdn>] [-Domains
<MultiValuedProperty>] [-EdgeTransportServers
<MultiValuedProperty>] [-ExternalIPAddresses
<MultiValuedProperty>] [-Features
<MultiValuedProperty>] [-OnPremisesSmartHost
<SmtpDomain>] [-ReceivingTransportServers
<MultiValuedProperty>] [-SendingTransportServers
<MultiValuedProperty>] [-TlsCertificateName
<SmtpX509Identifier>] [-WhatIf
[<SwitchParameter>]]

Examples

EXAMPLE 1

This example creates the hybrid configuration Hybrid Configuration with the default hybrid configuration settings.

	Copy Code
New-HybridConfiguration

Detailed Description

A hybrid deployment offers organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Microsoft Exchange organization to the cloud. The New-HybridConfiguration cmdlet is used with the Hybrid Configuration wizard and is typically configured when the hybrid deployment is initially created by the wizard. We strongly recommend that you use the Hybrid Configuration wizard to create the HybridConfiguration object and configure your hybrid deployment with the Exchange Online organization.

For more information, see Exchange Server 2013 Hybrid Deployments.

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 "Hybrid deployment configuration" entry in the Exchange and Shell Infrastructure Permissions topic.

Parameters

Parameter	Required	Type	Description
ClientAccessServers	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The ClientAccessServers parameter is deprecated and will be removed from Microsoft Exchange Server 2013.
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	The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.
Domains	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The Domains parameter specifies the domain namespaces that are used in the hybrid deployment. These domains must be configured as accepted domains in either the on-premises Exchange organization or the Exchange Online service. The domains are used in configuring the organization relationships and Send and Receive connectors used by the hybrid configuration.
EdgeTransportServers	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The EdgeTransportServers parameter specifies the Exchange servers with the Exchange 2010 Service Pack 2 (SP2) Edge Transport server role installed that are configured to support the hybrid deployment features. The Edge Transport server must be externally accessible from the Internet on port 25. The accepted values for the EdgeTransportServers parameter are either the full or short computer name of an Edge Transport server, for example, either edge.corp.contoso.com or edge. Separate server names with a comma if defining more than one Edge Transport server. When configuring the EdgeTransportServers parameter, you must configure the ReceivingTransportServers and SendingTransportServers parameter values to `$null`.
ExternalIPAddresses	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The ExternalIPAddresses parameter is a legacy parameter that specifies the publicly accessible inbound IP address of Microsoft Exchange Server 2010 Hub Transport servers. The only configuration change that should be made with this parameter is to change or clear the legacy Exchange 2010 Hub Transport server IP address value. The IP address must be Internet Protocol version 4 (IPv4) based only.
Features	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The Features parameter specifies the features that are enabled for the hybrid configuration. One or more of the following values separated by commas can be entered. When using the Hybrid Configuration wizard, all features are enabled by default. `OnlineArchive` Enables the Exchange Online archive for on-premises Exchange and Exchange Online organization users. `FreeBusy` Enables free/busy calendar information to be shared between on-premises Exchange and Exchange Online organization users. `MailTips` Enables MailTips information to be shared between on-premises Exchange and Exchange Online organization users. `MessageTracking` Enables message tracking information to be shared between on-premises Exchange and Exchange Online organization users. `OWARedirection` Enables automatic Microsoft Office Outlook Web App redirection to either the on-premises Exchange or Exchange Online organizations depending on where the user mailbox is located. `SecureMail` Enables secure message transport via Transport Layer Security (TLS) between the on-premises Exchange and Exchange Online organizations. `Centralized` Enables the on-premises servers to handle all message transport between the on-premises Exchange and Exchange Online organizations, including message delivering to the Internet for both organizations. If this value is `$false`, the on-premises server and Exchange Online organization are each responsible for their own Internet message delivery.
OnPremisesSmartHost	Optional	Microsoft.Exchange.Data.SmtpDomain	The OnPremisesSmartHost parameter specifies the FQDN of the on-premises Mailbox server used for secure mail transport for messages sent between the on-premises Exchange and Exchange Online organizations.
ReceivingTransportServers	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The ReceivingTransportServers parameter specifies the Exchange servers with the Client Access server role installed that are defined in the outbound connector configuration of the Microsoft Exchange Online Protection (EOP) service included as part of the Office 365 for enterprises tenant. The servers defined in the ReceivingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the Exchange Online organization to the on-premises Exchange organization in a hybrid deployment. At least one Client Access server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the ReceivingTransportServers parameter are either the full or short computer name of a Client Access server, for example, either CAS.corp.contoso.com or CAS. Separate server names with a comma if defining more than one Client Access server. If configuring the EdgeTransportServers parameter in the hybrid deployment, the ReceivingTransportServers parameter value must be `$null`.
SendingTransportServers	Optional	Microsoft.Exchange.Data.MultiValuedProperty	The SendingTransportServers parameter specifies the Exchange servers with the Mailbox server role installed that are defined in the inbound connector configuration of the EOP service included as part of the Office 365 for enterprises tenant. The servers defined in the SendingTransportServers parameter are designated as the receiving servers for secure mail messages sent from the on-premises Exchange organization to the Exchange Online organization in a hybrid deployment. At least one Mailbox server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises Exchange and Exchange Online organizations. The accepted values for the SendingTransportServers parameter are either the full or short computer name of a Mailbox server, for example, either MBX.corp.contoso.com or MBX. Separate server names with a comma if defining more than one Mailbox server. If configuring the EdgeTransportServers parameter in the hybrid deployment, the SendingTransportServers parameter value must be `$null`.
TlsCertificateName	Optional	Microsoft.Exchange.Data.SmtpX509Identifier	The TlsCertificateName parameter specifies the combination of the Issuer and Subject attributes of the Certification Authority (CA) issued X.509 certificate used for hybrid secure mail. The TlsCertificateName parameter is used to help authenticate the sender's certificate and to minimize the risk of fraudulent certificates. The Issuer portion of the TlsCertificateName value is derived from the certificate Issuer field and the Subject portion of the TlsCertificateName value is derived from the certificate Common Name field, for example, X509: <I>Issuer<S>Common Name.
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.

Input Types

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.

Return Types

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.