Sophos Email customers using IP-based mailflow rule connectors must migrate to certificate-based configuration by March 31st. To see if you're affected Click Here.

Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 25 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 16832 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Outbound Emails sent from Sophos" Connector Failed to Setup

it_samurai

I am attempting to setup Sophos Mailflow for a O365 tenant with Microsoft Basic Business licenses. The "Outbound Emails sent from Sophos" inbound connector fails to enable and when I try to enable it manually I get the error: 

Error executing request. For this service offering, you can't enable an inbound connector. Please contact Support to enable it. Organization '0f4eda73-53b3-4e46-ad7f-aec9d9ff6dad', Service Offering: 'O365_BUSINESS_ESSENTIALS'.

Apparently Microsoft made an unannounced change, that took affect 01/01/2023, restricting admins from activating newly-created inbound connectors for new tenants. This change affects the following SKUs:

 
Microsoft 365 Business Standard
Microsoft 365 Business Basic
Exchange Online Essentials

These connectors are created as “Disabled” by default. Customers that experience this behavior must contact Microsoft support with a business justification to enable an Inbound connector of OnPremises type within their tenant.

I have opened a ticket with Microsoft to enable the connector. I will update this post with my experience and steps.

https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/inbound-connector-faq



This thread was automatically locked due to age.
Parents
  • 0

    Adding my experience to this conversation for anyone still reading it.
    After waiting for over a month for Microsoft 365 support escalation, they informed me that they will not enable an inbound connector for Sophos Mailflow. Their response is below. I've opened a new Sophos case to find a solution for our client.
    -----

    As discussed, Sophos is currently non-compliant in how it integrates with M365. 

    So far, we have been rejecting to enable connectors in this regard as confirmed from the backend team (and the fact that Sophos (and some other vendors) chose to build a solution on top of an unverified scenario which isn't supported: See more details in https://aka.ms/EmailAddOnService

Reply
  • 0

    Adding my experience to this conversation for anyone still reading it.
    After waiting for over a month for Microsoft 365 support escalation, they informed me that they will not enable an inbound connector for Sophos Mailflow. Their response is below. I've opened a new Sophos case to find a solution for our client.
    -----

    As discussed, Sophos is currently non-compliant in how it integrates with M365. 

    So far, we have been rejecting to enable connectors in this regard as confirmed from the backend team (and the fact that Sophos (and some other vendors) chose to build a solution on top of an unverified scenario which isn't supported: See more details in https://aka.ms/EmailAddOnService

Children
No Data
Unfiltered HTML