Cutover Migration, ADFS and Dirsync question
-
lunedì 16 aprile 2012 19:03
I am reading the online document at http://community.office365.com/en-us/w/exchange/835.aspx and the instructions say’s to implement ADFS after all the on-prem mailboxes have been converted to MEU’s. A cutover migration is used to migrate ALL mailboxes to the cloud at the same time, and once all email data is synced with the O365 mailbox the MX records are moved to O365. My questions are below
#1 Once all on-prem mailboxes are synced with the O365 mailbox can I convert the on-prem mailboxes to MEU’s while still pointing the MX record to the on-prem Exchange server?
#2 Will the on-prem MEU along with the internal DNS CNAME record redirect the ALREADY configured outlook profile to the O365 mailbox? I don’t want to recreate new outlook profiles for users to connect to the O365 mailbox.
#3 Can I install and configure ADFS before converting the on-prem mailboxes to MEU’s? Once all on-prem mailboxes have been converted to MEU’s users now have to access the O365 mailbox. It appears to me that installing and configuring ADFS after on-prem mailboxes are converted to MEU’s puts me in a rush to get ADFS setup and configured properly. Is there a way to install and configure ADFS before the on-prem mailboxes are converted, so I can test and make sure ADFS is working correctly?
Bulls on Parade
Tutte le risposte
-
lunedì 16 aprile 2012 22:12Moderatore
Thanks for the great questions!
1. Yes, the MX record doesn't have to be altered as long as mail continues to flow properly (forwarders associated with the MEU to the O365 accounts via a secondary domain (such as user@domain.onmicrosoft.com). This is called simple co-existence and is completely possible.
2. If you configure the on-premises autodiscover record to point to Office 365's endpoint, then it should definitely work. As for recreating profiles ... since it IS the same mail, I would think it should work properly, but this would have to be tested since I don't know HOW it is determined to be new/old. I know this functions properly for BPOS to Office 365 transition customers, but I don't know if there is any magic done on the back-end to fix it.
3. ADFS can be configured at ANY time after your tenant has been provisioned in Office 365 (generally ~24 hours after tenant provisioning and enabling ADFS, actually) and can be fully tested prior to migrating your users. The post-deployment recommendation is to get users used to the new environment and stable before adding another layer of complexity to the hosted solution ... just a safe-guard, but nothing preventing going around this.
Have a great day,
Dan
www.insecurityinc.info
- Proposto come risposta Daniel TrautmanModerator lunedì 16 aprile 2012 22:12

