Solved

Office 365 Tenant Questtion - Migration from Exchange 2010 SP3

Posted on 2014-11-26
5
256 Views
Last Modified: 2015-01-11
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.protection.outlook.com

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
0
Comment
Question by:lapavoni
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40468525
I would say yes to the new tenant. But I don't see what you would be merging.

The way I see it. New tenant, Migrate to that new tenant. Discontinue the tenant that has EOP.
0
 

Author Comment

by:lapavoni
ID: 40472952
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 ?
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40473033
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.
0
 

Accepted Solution

by:
lapavoni earned 0 total points
ID: 40473037
We've got about 70 users, all on laptops. 10-15 are travelling at any given time.  I would like to do a "cutover" migration, but I understand that if you've enabled and used DirSync, that's not possible. I don't fully understand the reason, though. I do know that user accounts have been created in our tenant, but are obviously not licensed yet (just used for EOP purposes).   I also don't fully understand the "hybrid" scenario.  I'd like to manage user accounts on-premises and have Exchange attributes and passwords synched to Office 365, so I've been told that we need to maintain an on-premises Exchange server to do so (transport disabled, but not sure what roles, if any, still necessary).  My goal is to not have users maintain two sets of passwords.  All users will be using the Office 2013 client, so web mail is not that big an issue.
0
 

Author Closing Comment

by:lapavoni
ID: 40542882
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.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
Find out what the Office 365 disclaimer function is, why you would use it and its limited ability to create Office 365 signatures.
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question