{"id":5694,"date":"2023-02-07T13:57:39","date_gmt":"2023-02-07T18:57:39","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5694"},"modified":"2023-02-07T13:57:40","modified_gmt":"2023-02-07T18:57:40","slug":"migrating-from-exchangedefender-to-m365","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2023\/02\/migrating-from-exchangedefender-to-m365\/","title":{"rendered":"Migrating from ExchangeDefender to M365"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/a>
A quick guide for email migration to M365.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

If you’re currently on ExchangeDefender (our Exchange or other email services) and migrating to M365 there are a few important steps to take to make sure everything is secure and mail moves appropriately to the new destination.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Step 1: If you’re leaving our Hosted Exchange platform<\/h3>\n\n\n\n
<\/div>\n\n\n\n

If you’re leaving our Exchange first you need to remove the domain from the Service Manager. Go to https:\/\/support.exchangedefender.com<\/a> and after login click on Service Manager.<\/p>\n\n\n\n

From there just select your Exchange organization<\/strong> and click on Delete<\/strong>.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

You will be presented with a confirmation screen, follow the instructions and system will schedule your organization for removal from our Exchange network. Next, let’s take care of ExchangeDefender.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Step 2: Moving the ExchangeDefender pointer and MX records<\/h3>\n\n\n\n
<\/div>\n\n\n\n

When you setup your M365 Exchange service Microsoft will issue you an MX record that is typically formatted like this: DOMAIN.mail.protection.outlook.com<\/strong><\/a><\/p>\n\n\n\n

<\/div>\n\n\n\n

Go to\u00a0https:\/\/admin.exchangedefender.com\/domain-sp-login.php<\/a>\u00a0and login either as the domain administrator (userid:\u00a0domain.com<\/a>) or ExchangeDefender Service Provider (userid: sp) and proceed to Mail Delivery tab.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/a>

On the Mail Delivery tab<\/strong> you should set your mail server as “Office 365, Gmail, or multihomed MX record (3rd party MX record)” and provide your M365 MX record below. <\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Click Save <\/strong>and routing tables will be updated within the hour. In the meantime please follow these instructions to lock down your M365 tenant to only allow secure email delivery via ExchangeDefender this step is required or mail will not be delivered<\/strong>! <\/p>\n\n\n\n

<\/div>\n\n\n\n
\n
Visit our Documentation<\/a><\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n

This process takes only a few minutes but it’s absolutely crucial.<\/strong><\/p>\n\n\n\n

<\/div>\n\n\n\n

That’s all you need to properly deliver mail to M365 via ExchangeDefender. If you’re not interested in securing your mail flow and protecting your M365 instance from malware & phishing you can always delete all the domains and references from ExchangeDefender.<\/p>\n\n\n\n

<\/div>\n\n\n\n

If you run into any issues please open a support request at https:\/\/support.exchangedefender.com<\/a> with the M365 MX record and M365 admin credentials and we’ll take care of the process for you.<\/p>\n\n\n\n

Thank you for trusting us to secure your email.<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":50,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[202,201],"class_list":["post-5694","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-m365","tag-migration"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5694","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=5694"}],"version-history":[{"count":8,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5694\/revisions"}],"predecessor-version":[{"id":5706,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5694\/revisions\/5706"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5694"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5694"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5694"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}