EOP fixes and general clean-up

Author: chrisda

exchange/exchange-ps/exchange/New-HybridConfiguration.md

@@ -14,7 +14,10 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-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 365 for enterprises organization.
+Use the New-HybridConfiguration cmdlet to manually create the HybridConfiguration object and manually set up a hybrid deployment between your on-premises Exchange organization and Exchange Online in Microsoft 365 for enterprises.
+
+> [!NOTE]
+> We strongly recommend that you use the Hybrid Configuration wizard to create the HybridConfiguration object and configure your hybrid deployment with Exchange Online.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -41,7 +44,9 @@ New-HybridConfiguration
 ```
 
 ## 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.
+A hybrid deployment offers organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Exchange organization to the cloud.
+
+The available settings in this cmdlet are configured when the Hybrid Configuration Wizard initially creates the the HybridConfiguration object.
 
 For more information, see [Exchange Server hybrid deployments](https://learn.microsoft.com/exchange/exchange-hybrid).
 
@@ -61,11 +66,13 @@ This example creates the hybrid configuration named Hybrid Configuration with th
 ### -ClientAccessServers
 This parameter is available only in Exchange Server 2010.
 
-The ClientAccessServers parameter specifies the Exchange Server 2010 SP2 servers with the Client Access server role installed that will be configured to support the hybrid deployment features. At least one Client Access server must be defined and be externally accessible from the Internet on ports 80 and 443. The servers will be configured to enable the following:
+The ClientAccessServers parameter specifies the Hub Transport servers in Exchange Server 2010 SP2 or later that are configured to support hybrid deployment features. You need to specify at least one Client Access server that's accessible from the internet on TCP ports 80 and 443. The servers are configured to enable the following features:
+
+- Mailbox Replication Service (MRS) Proxy: Enable the MRS Proxy service configuration.
+- Virtual Directories: Host the default web sites for Exchange Web Services (EWS), offline address books, and ActiveSync services.
+- Outlook Anywhere: Enabled.
 
-- Mailbox Replication Service (MRS) Proxy The MRS Proxy service configuration on the Client Access servers will be enabled.
-- Virtual Directories The Client Access servers will host the default Web sites for the Exchange Web Services (EWS), offline address books, and ActiveSync services.
-- Outlook Anywhere The Client Access servers will have Outlook Anywhere enabled.
+You can specify multiple servers separated by commas.
 
 ```yaml
 Type: MultiValuedProperty
@@ -116,7 +123,9 @@ Accept wildcard characters: False
 ```
 
 ### -Domains
-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.
+The Domains parameter specifies the domain namespaces used in the hybrid deployment. These domains must be configured as accepted domains in either on-premises Exchange or Exchange Online. The domains are used in configuring the organization relationships and Send and Receive connectors used by the hybrid configuration.
+
+You can specify multiple domains separated by commas.
 
 ```yaml
 Type: MultiValuedProperty
@@ -132,9 +141,14 @@ Accept wildcard characters: False
 ```
 
 ### -EdgeTransportServers
-The EdgeTransportServers parameter specifies the Edge Transport servers 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.
+The EdgeTransportServers parameter specifies the Edge Transport servers that are configured to support the hybrid deployment features. The Edge Transport server must be accessible from the internet on port 25. Valid values are:
+
+- The Edge Transport server FQDN (for example, edge.corp.contoso.com).
+- The Edge Transport server host name (for example, EDGE).
+
+You can specify multiple server separated by commas.
 
-When configuring the EdgeTransportServers parameter, you must configure the ReceivingTransportServers and SendingTransportServers parameter values to $null.
+If you use this parameter, don't use the the ReceivingTransportServers and SendingTransportServers parameters (their values must be blank or $null).
 
 ```yaml
 Type: MultiValuedProperty
@@ -150,7 +164,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExternalIPAddresses
-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.
+The ExternalIPAddresses parameter is a legacy parameter that specifies the publicly accessible inbound IP address of Microsoft Exchange Server 2010 Hub Transport servers.
+
+You should use this parameter to change or clear legacy Exchange 2010 Hub Transport server IP address values only. IPv6 addresses aren't supported.
 
 ```yaml
 Type: MultiValuedProperty
@@ -166,16 +182,18 @@ Accept wildcard characters: False
 ```
 
 ### -Features
-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.
+The Features parameter specifies the features that are enabled for the hybrid configuration. Valid values are:
+
+- OnlineArchive: Enables the Exchange Online archive for on-premises Exchange and Exchange Online users.
+- FreeBusy: Enables calendar free/busy sharing between on-premises Exchange and Exchange Online users.
+- MailTips: Enables MailTips between on-premises Exchange and Exchange Online users.
+- MessageTracking: Enables message tracking between on-premises Exchange and Exchange Online.
+- OWARedirection: Enables automatic Outlook on the web (formerly known as Outlook Web App or OWA) redirection to on-premises Exchange or Exchange Online, depending on where the user mailbox is located.
+- SecureMail: Enables secure message transport via Transport Layer Security (TLS) between on-premises Exchange and Exchange Online.
+- Centralized: Enables the on-premises Exchange servers to handle all message transport between on-premises Exchange and Exchange Online, including message delivery to the internet for both organizations. If you don't use this value, on-premises Exchange and Exchange Online are each responsible for their own internet message delivery.
+- Photos: Enables the sharing of user photo data between the on-premises Exchange and Exchange Online. This feature works in tandem with the PhotosEnabled parameter in the OrganizationRelationship cmdlets in a hybrid deployment. If you use this value, the PhotosEnabled parameter is automatically set to $true. If you don't use this value, the PhotosEnabled parameter is automatically set to $false.
 
-- 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 Outlook on the web 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.
-- Photos: Enables the sharing of user photo data between the on-premises Exchange and Exchange Online organizations. This feature works in tandem with the PhotosEnabled parameter in the OrganizationRelationship cmdlets in a hybrid deployment. If the Photos parameter is $true, the PhotosEnabled parameter is automatically set to $true. If the Photos parameter is $false, the PhotosEnabled parameter is automatically set to $false. When running the Hybrid Configuration wizard for the first time, the default value is $true.
+You can specify multiple values separated by commas. When you use the Hybrid Configuration wizard, all features are enabled by default.
 
 ```yaml
 Type: MultiValuedProperty
@@ -191,7 +209,7 @@ Accept wildcard characters: False
 ```
 
 ### -OnPremisesSmartHost
-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.
+The OnPremisesSmartHost parameter specifies the FQDN of the on-premises Exchange Mailbox server used for secure mail transport between on-premises Exchange and Exchange Online.
 
 ```yaml
 Type: SmtpDomain
@@ -207,9 +225,16 @@ Accept wildcard characters: False
 ```
 
 ### -ReceivingTransportServers
-The ReceivingTransportServers parameter specifies the Mailbox servers that are defined in the outbound connector configuration of the Microsoft Exchange Online Protection (EOP) service included as part of the Microsoft 365 organization. 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 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 ReceivingTransportServers 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.
+The ReceivingTransportServers parameter specifies the Mailbox servers defined in the outbound connector configuration in Exchange Online. Valid values are:
+
+- The Mailbox server FQDN (for example, mbx.corp.contoso.com).
+- The Mailbox server host name (for example, MBX).
+
+You can specify multiple servers specified by commas.
+
+The specified servers receive secure email messages from Exchange Online to on-premises Exchange in a hybrid deployment. You need to specify at least one publicly accessible Mailbox server to enable secure mail.
 
-If configuring the EdgeTransportServers parameter in the hybrid deployment, the ReceivingTransportServers parameter value must be $null.
+Don't use this parameter with the EdgeTransportServers parameter. The value of this parameter must be blank ($null) when you use the EdgeTransportServers parameter.
 
 ```yaml
 Type: MultiValuedProperty
@@ -227,7 +252,7 @@ Accept wildcard characters: False
 ### -SecureMailCertificateThumbprint
 This parameter is available only in Exchange Server 2010.
 
-The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate cannot be self-signed, must be obtained from a trusted certificate authority (CA) and must be installed on all Hub Transport servers defined in the TransportServers parameter.
+The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to use as the certificate for hybrid deployment secure message transport. This certificate can't be self-signed, must be obtained from a trusted certification authority (CA), and must be installed on all Hub Transport servers specified in the TransportServers parameter.
 
 ```yaml
 Type: String
@@ -243,9 +268,16 @@ Accept wildcard characters: False
 ```
 
 ### -SendingTransportServers
-The SendingTransportServers parameter specifies the Exchange Mailbox servers that are defined in the inbound connector configuration of the EOP service included as part of the Microsoft 365 organization. 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.
+The SendingTransportServers parameter specifies the Mailbox servers defined in the inbound connector configuration in Exchange Online. Valid values are:
 
-If configuring the EdgeTransportServers parameter in the hybrid deployment, the SendingTransportServers parameter value must be $null.
+- The Mailbox server FQDN (for example, mbx.corp.contoso.com).
+- The Mailbox server host name (for example, MBX).
+
+You can specify multiple servers specified by commas.
+
+The specified servers send secure email messages from on-premises Exchange to Exchange Online in a hybrid deployment. You need to specify at least one publicly accessible Mailbox server to enable secure mail.
+
+Don't use this parameter with the EdgeTransportServers parameter. The value of this parameter must be blank ($null) when you use the EdgeTransportServers parameter.
 
 ```yaml
 Type: MultiValuedProperty
@@ -261,7 +293,11 @@ Accept wildcard characters: False
 ```
 
 ### -ServiceInstance
-The ServiceInstance parameter should only be used by organizations manually configuring hybrid deployments with Office 365 operated by 21Vianet in China. All other organizations should use the Hybrid Configuration wizard to configure a hybrid deployment with Microsoft 365. The valid values for this parameter are 0 (null) or 1. The default value is 0 (null).For organizations connecting with Office 365 operated by 21Vianet in China, set this value to 1 when manually configuring your hybrid deployment.
+This parameter is meaningful only in Office 365 operated by 21Vianet in China.
+
+To manually configure a hybrid deployment with Office 365 operated by 21Vianet in China, set the value of this parameter to 1. Otherwise, the default value is 0.
+
+All other Microsoft 365 organizations should use the Hybrid Configuration wizard to configure a hybrid deployment.
 
 ```yaml
 Type: Int32
@@ -277,7 +313,14 @@ Accept wildcard characters: False
 ```
 
 ### -TlsCertificateName
-The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter.
+The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. Valid syntax for this parameter is `"<I>X.500Issuer<S>X.500Subject"`:
+
+- `X.500Issuer`: The value in the certificate's Issuer field.
+- `X.500Subject`: The value in the certificate's Subject field.
+
+You can find these values by running the Get-ExchangeCertificate cmdlet.
+
+Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, use the thumbprint value in the command `$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"`, and then use the value `$TLSCertName` for this parameter.
 
 ```yaml
 Type: SmtpX509Identifier
@@ -295,7 +338,11 @@ Accept wildcard characters: False
 ### -TransportServers
 This parameter is available only in Exchange Server 2010.
 
-The TransportServers parameter specifies the Exchange Server 2010 SP2 servers with the Hub Transport server role installed that are configured to support the hybrid deployment features. At least one Hub Transport server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises and cloud-based organizations.
+The TransportServers parameter specifies the Hub Transport servers in Exchange Server 2010 SP2 or later that are configured to support hybrid deployment features.
+
+You need to specify at least one Hub Transport server that's accessible from the internet for secure mail between on-premises Exchange and Exchange Online.
+
+You can specify multiple servers separated by commas.
 
 ```yaml
 Type: MultiValuedProperty