This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 41%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I am implementing an EOP (stand alone) and I have to create an office 365 inbound connector. About that I have a couple of concerns:
1) What is the difference (in terms of configuration) between the options: "your organization's email server" and "Partner organization" ?
2) In the next session "How should O365 identify email from ...." choosing the first option (picture below="by verifying that the subject name ...." etc ...) it is not clear to me what kind of steps O365 take place to accept the inbound mail-flow from the FQDN domain we are going to insert.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hi @Marc
Andy has given quite helpful replies below. Is there any update about your question? Have you succeed creating the connector now?
Thank you once again Andy.
in this case will EOP identify the authorized server as contoso.com to receive all emails or will be the domain that EOP will use to accept only emails directed to contoso.com like john@Company portal .com?
The cert is used to identify and authorize those servers as yours. Its all about attribution:
https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-message-attribution/ba-p/749143
You can send any from any valid accepted domain through that from on-prem to EOP and/or out through to the internet from EOP.
If this is a partner inbound connector, you use the cert to authorize it as well. The difference is that for a partner connector, you also defined the allowed domains that can be sent inbound from that partner to your 365 tenant.
All the certificate does is tell EOP that its really your server sending these messages. You can also scope by IP, but certs are better