Office 365 Tenant Questtion - Migration from Exchange 2010 SP3
Greetings, everyone.
We have on-premises Exchange 2010 SP3. We've used the Exchange Online Protection (formerly Forefront Online Protection for Exchange) service for years.
When FOPE was converted to EOP, Microsoft created an Office 365 Tenant for us. It exists just to give us access to the Exchange Online Protection interface. It also uses DirSync to synchronize user accounts into that tenant ... for the sole purpose of filtering e-mail.
We are a non-profit and had our tenant converted to non-profit status.
We are prepared to add our E1 service, with the necessary number of user licenses, to our account.
Microsoft is unable to give me a straight answer to the next question, so I'm asking the Experts here:
--------------------------
Our MX record is currently:
our_domain_name-org.mail.p
The "outbound" connector in EOP is our internal Exchange 2010 SP3 server, as expected.
Question - When I purchase/acquire E1 licenses, does the separate "Exchange Online Protection" service continue to function - i.e. filter our e-mail and send it on its merry way to our internal Exchange 2010 SP3 server, or does the Office 365 E1 built-in filtering take over and need to be reconfigured to allow e-mail to be sent to our internal Exchange server ?
I'm pretty sure Office 365 (Exchange Online) uses a different MX record to route mail than our current one.
--------------------------
I've spoken with Microsoft about this and they seem to be confused. The same tech says "yes, no problem" and "you'll need to create a new tenant and then merge them" in the same sentence.
I am confused. Can anyone shed light on this scenario ?
Thanks much.
-Stephen
We have on-premises Exchange 2010 SP3. We've used the Exchange Online Protection (formerly Forefront Online Protection for Exchange) service for years.
When FOPE was converted to EOP, Microsoft created an Office 365 Tenant for us. It exists just to give us access to the Exchange Online Protection interface. It also uses DirSync to synchronize user accounts into that tenant ... for the sole purpose of filtering e-mail.
We are a non-profit and had our tenant converted to non-profit status.
We are prepared to add our E1 service, with the necessary number of user licenses, to our account.
Microsoft is unable to give me a straight answer to the next question, so I'm asking the Experts here:
--------------------------
Our MX record is currently:
our_domain_name-org.mail.p
The "outbound" connector in EOP is our internal Exchange 2010 SP3 server, as expected.
Question - When I purchase/acquire E1 licenses, does the separate "Exchange Online Protection" service continue to function - i.e. filter our e-mail and send it on its merry way to our internal Exchange 2010 SP3 server, or does the Office 365 E1 built-in filtering take over and need to be reconfigured to allow e-mail to be sent to our internal Exchange server ?
I'm pretty sure Office 365 (Exchange Online) uses a different MX record to route mail than our current one.
--------------------------
I've spoken with Microsoft about this and they seem to be confused. The same tech says "yes, no problem" and "you'll need to create a new tenant and then merge them" in the same sentence.
I am confused. Can anyone shed light on this scenario ?
Thanks much.
-Stephen
ASKER
The current tenant has our domains already set up - DNS, MX, TXT and Autodiscover have already been modified. Since I can't use the same domain names in two tenants, that would probably involve some downtime, yes ?
If you are only using it for Exchange Online Protection then you would only have a TXT record, to verify the domain, and the MX record to direct mail flow. Autodiscover should still be pointing to your on premise server, as would be all other DNS records.
What kind of a migration are you planning? How many users do you have? That will determine the amount of downtime.
What kind of a migration are you planning? How many users do you have? That will determine the amount of downtime.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The final answer to my question was that we needed to move our filtering service to a third-party provider temporarily. Once the cutover/migration is completed, then filtering will occur on the new cloud (Office 365) mailboxes.
The way I see it. New tenant, Migrate to that new tenant. Discontinue the tenant that has EOP.