Skip to content

Latest commit

 

History

History
57 lines (28 loc) · 3.47 KB

Enable OnPremConnectors.md

File metadata and controls

57 lines (28 loc) · 3.47 KB

Enabling the creation of OnPremise Inbound Connectors on new M365 tenants

Whats the problem ?

Beginning with February 2023, Microsoft blocked the possibility to create new OnPrem inbound connectors.

This is also known as the Advisory posted to the Service Health with the ID EX505293.

OnPremise Connectors are a requirement for the integraton with SEPPmail.cloud in parallel mode or a SEPPmail Appliance.

How do i know i am affected ?

Customers and partners, configuring the integration with SEPPmail will use a PowerShell Module (SEPPmail365 or SEPPmail365cloud) to setup rules and connectors.

After creating the setup, the inbound connector will stay disabled and you cannot enable it via the GUI or Powershell

What do i need to do to solve the issue ?

Microsoft Support enabled inbound connectors in specific cases and they are documented in this link

Nevertheless there are 4 easy steps to speed up this process and avoid to run into a longer discussion with MS support.

  1. Rename the connectors "sent email identity" from the preconfigured .. to seppmail..

To give you a real world example, for a customer contoso.eu which wants to integrate SEPPmail.cloud Germany the sent email identity would be something like

d563a719-f13b-4427-b196-eb139b7a56a8.de.seppmail.cloud

Save this record somewhere - you will need it later

Login to your Exchange Admin Center (EAC), go to Mailflow ==> Connectors and edit the [SEPPmail] Inbound connector. Go to "Edit sent email identity". Change the name from the automatically set value to: seppmail.., so for our example seppmail.contoso.eu.

  1. Create a new "Accepted Domain" in your Exchange Online Tenant

Open M365 Admin Center, go to settings ==> domains and add a new domain. As domain name use the same name as in the inbound connector, i.e. seppmail.contoso.eu. Finish the Add-Domain wizard until the domain is visible in your domain list.

This domain does not have to exist, there will never be any mailflow with this domain, and we will delete it later on.

  1. Open a ticket with microsoft support

Contact Microsoft Support and request them to enable the inbound connector. You can adapt and use the following text-template:

We need the inbound connector for our trusted and valued E-Mail Security 3rd Party "SEPPmail.Cloud" from Swizerland. SEPPmail provides cryptographic E-Mail processing, which is a required standard of our company for business communication.

This issue is referenced to the Service Health advisory with the ID EX505293, and we have fulfilled all requirements according to the Microsoft documentation

Microsoft should then positively anser your request and enable the connector.

  1. Rebuild the Configuration

Open the Inbound Connector in EAC and set the "sent email identity" back to original value provided with the PowerShell Module .. ( the one you recorded in step 1).

Mail should now flow through SEPPmail(.cloud). As a cleanup action you may delete the seppmail.. from your tenant domain list of leave it as an emotional reference to this thrilling support experience.

If there are any further issues contact us at [email protected]