An update to "Important notice for Office 365 email customers who have configured connectors"

Since we posted this blog post, we have received positive responses from many of our customers, who have proceeded with changing their connectors (as per instructions in the post), thereby protecting their email/domain reputation. However, we are also aware of customers who are either in the midst of making this change or need some additional time to complete their changes. We understand a change like this can take some time, so we have decided to move our deadline from Feb 1st, 2017 to July 5th, 2017.

We have also added more details in the original post. If you are an Office 365 email customer and your organization is hybrid (you have an on-premise environment), please take some time to read it!

Carolyn Liu

Comments (2)
  1. Suresh says:

    Hi Carolyn,

    I have environment in which many applications and devices sending emails to my organization and external users. How can i achieve this using O365 SMTP? I cant authenticate all the devices. So i cant use client submission I want to send email to external addresses. So i cant use direct send. I am left with SMTP relay. I am not sure i can just create a connector and just add my firewall Public IP address to receive emails on O365 and to send to external addresses. Or do i have to send emails to SMTP server in on premises and then set up SMTP server to send emails to O365.

    Detailed instructions appreciated.

  2. Hi Carolyn,

    We don´t have Hybrid config but we use “Windows SMTP Server Service” to relay messages from apps, printers, devices, etc., to Office365 smarthost. Do we need to implement Exchange Server to relay?

    Last question: Why comments are closed on the main post? You should have a place where all kind of questions regarding this change could be resolved.

Comments are closed.

Skip to main content