This post is a reference for the future. It shows the older EOP connectors that were created by the Exchange Hybrid Configuration Wizard (HCW) and then the format of the newer connectors. Note that the names etc. will likely be changed again at some point in the future - change is inevitable.
This is how things looked in late 2017 / early 2018.
EOP Connector Names - Circa 2015
The connector below was created by the older HCW with a name of "Hybrid Mail Flow Inbound Connector".
If we look at the details, note that we see the source IP that was specificed in the HCW and also the FQDN of the on-premises endpoint. That should not be a thing as it should have been one or the other at that point.
Verbiate for search engines:
This connector is currently set up to use both a certificate name and an IP address to identify email from your email server. This option isn't supported. Please make sure you've selected the option you want, and we'll delete any existing settings for the other option when the connector is saved. Alternatively, you can create two connectors if you have email servers in different locations. For example, if you have an email server in one location that uses a certificate and one in another location that doesn't.
EOP Connector Names PowerShell - Circa 2015
If we look at the same connector using PowerShell, the details are below.
Newer HCW Connector - Circa 2017
Note that the name of the connector has changed. The new format is "Inbound from XXXXXX-XXXX-XXXXX". Where the GUID is the on-premises Exchange organisation GUID.
Only the FQDN is present. This is expected as the source IP was a construct from the original Exchange 2010 HCW. Back then the IP was used to regognise the on-premises endpoint but that was replaced as a TLS certificate is resilient to IP address changes.
Newer HCW Connector In PowerShell - Circa 2017
As before here are the connector details shown in PowerShell.
Cheers,
Rhoderick
