ra2 studio - Fotolia

Get started Bring yourself up to speed with our introductory content.

Gauge your readiness to move to Office 365

We break down the important questions Exchange admins must answer before migrating to Office 365.

Microsoft Exchange has been a core business application for years, but Microsoft's introduction of Office 365 gives enterprises email as a service. The notion of Exchange email without the need for an Exchange infrastructure sounds compelling. But the move from Exchange to Office 365 requires planning and preparation to ensure a smooth and successful migration.

Are you ready to move to Office 365? There are a few important questions you need to ask to gauge your readiness before making the switch.

A company's identity is closely tied to its domain name, so it's important to plan ahead and decide how Office 365 will interact with Active Directory and the domain name.

How will you handle your domain name and Active Directory in a move to Office 365?

You'll need to redirect email traffic from your local Exchange servers to the Office 365 service.

The easiest way to do this is through partial re-delegation. This is where the company retains control of the domain, but the administrative console for Office 365 adds the company's domain name to the service.

However, Microsoft can't simply abscond with any domain's email; there has to be some proof that you actually control the domain name. This normally involves providing the logon credentials for the domain name system (DNS) server. Microsoft adds a text record to the DNS server and verifies its existence. If successful, Microsoft acknowledges that you own the domain and allows email to redirect to Office 365 services instead of local Exchange Servers.

The alternative to partial re-delegation is an approach called identity federation. This is where end users log on to Office 365 using their regular Active Directory credentials and the company handles authentication and continues to manage password policies. The difference here is that a local Active Directory Federation Services server provides a token that then passes to Office 365 to handle the logon for email services.

In effect, this offers a single sign-on approach to Office 365 that does not expose the company's DNS server information. However, identity federation can pose additional complexities for a company. Small and medium-sized organizations will almost always use partial re-direction, which does not require any additional local servers or services.

Next Steps

This is part one of the Exchange admin's Office 365 migration checklist. Stay tuned for part two, which covers user migration and account management.

This was last published in October 2014

Dig Deeper on MS Office 365

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

6 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

NO, we are not ready. We do NOT want to give our Data to the Vendor (Microsoft).
Cancel
Bob2014, why the hesitation to move to Office 365? Do you think at some point your organization will migrate to it?
Cancel
@Michael, do you understand "We do NOT want to give our Data to the Vendor (Microsoft)".
Cancel
@Michael, Per revelations, Microsoft Public Cloud services & Google Public Cloud services have Back-door Access....Once your Data is in the Public Cloud services, the Vendor OWNS your Data & who knows who have access to your Data….
Cancel
@Michael, Per NSA PRISM revelations..........
Cancel
damn.. ill never let em take my data's 
Cancel

-ADS BY GOOGLE

SearchWindowsServer

SearchEnterpriseDesktop

SearchCloudComputing

SearchSQLServer

Close