23 C
Dubai
Friday, March 29, 2024

Configuring Mimecast with Office 365

Lets see how to synchronize azure active directory users by providing Azure Active Directory API Permissions with mimecast directory synchronization and configure inbound and outbound mail flow with mimecast. Currently On-Premise Exchange server Configured in Hybrid Mode and Azure AD Connect is Configured with Password hash Synchronization. We will move Mail flow to mimecast and start moving mailboxes to the cloud.This Configuration is suitable for Office 365 Cloud users and Hybrid users.

Log into the mimecast console

First Add the TXT Record and verify the domain.

image

Once the domain is Validated. Choose Next.

image

Now we need to Configure the Azure Active Directory Synchronization.

Now we need three things.

  • Application/Client ID
  • Key
  • Tenant Domain

lets see how to configure them in the Azure Active Directory .

image

Log into Azure Active Directory Admin Center

image

Azure Active Directory – App Registrations – New Registration

image

Enter a friendly Name _

Choose – Accounts in this organizational directory only (Azure365pro – Single tenant)

image

  • Copy the Application (client) ID for Mimecast Console

image

Click on Certificates and Secrets

Create Client Secret _ Copy the new Client Secret value. You won’t be able to retrieve it after you perform another operation or leave this blade.

So store the value in a safe place so that we can use (KEY) it in the mimecast console.

image

image

Get the default domain which is the tenant domain in mimecast console.

image

Now Add below permissions  _

Microsoft Graph – Application Permissions – User.Read.All Read all users’ full profiles

image

Azure Active Directory Graph – Application Permissions – Directory.Read.All Read directory data

Azure Active Directory Graph –  Delegated Permissions – User.Read.All Read all users’ full profiles

image

Samples _

image

image

In the End it should look like below. it will prepare for consent and Click on “Grant Admin Consent”

image

Once the permission is granted . Wait for few minutes

Now  _ Get to the mimecast Admin Console fill in the details which we collected earlier and click on synchronize.

image

Now Synchronization is configured.

image

Choose Next Task to allow authentication for mimecast apps .

image

Now lets whitelist mimecast IPs in Connection Filter.

Login to Exchange Admin Center _ Protection _ Connection Filter

Choose Default _ Edit (Pen Icon)

image

Now Choose Default Filter and Edit the filter to allow IP ranges . you can get from the mimecast console.

or you refer below link for updated IP ranges for whitelisting inbound mail flow.

and Check Enable Safe list.

https://community.mimecast.com/s/article/Adding-Network-Ranges-to-Office-365

image

Get the mx value of the domain

Microsoft 365 Admin Center _ Domains _ MX value

image

Now you can test the inbound mail flow.

image

Now inbound to Office 365 works fine.

image

Lets do the outbound email now.

image

Configuring SPF.

In my case its a hybrid. So mails are going out via on-premise servers as well

So I added only include line in my existing SPF Record.as per the screenshot.

my spf looks like v=spf1 include:eu._netblocks.mimecast.com  a:mail.azure365pro.com ip4:148.50.16.90 ~all

image

Lets create a connector to force all outbound emails from Office 365 to Mimecast

At this point we will create connector only . Only the transport rule will make the connector active.

image

Outbound to Mimecast

image

Choose  – Only when i have a transport rule set up that redirects messages to this connector

Choose – Next

image

  • Route email through these smart hosts

Get the smart hosts via mimecast administration console.

image

image

Leave it default.

Choose “Always use Transport Layer Security (TLS) to secure the connection (recommended)

Issued by a trusted certificate authority (CA)

image

Now create a transport rule to utilize this connector.

Once you turn on this transport rule . your mail flow will start flowing through mimecast. Its recommended to move your outbound mail flow first for a week so that it can do the learning then move your mx to mimecast to have very few false positives. Still its going to work great if you move your mx on the first day.

image

image

Now you are good to move your MX record.

image

Now Secure your inbound email

image

image

Use the Sender’s domain

image

image

image

Add the listed IP ranges

image

 

image

Whenever you wish to sync Azure Active Director Data

image

Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Related Articles

2 COMMENTS

LEAVE A REPLY

Please enter your comment!
Please enter your name here

× How can I help you?