![[UPDATED] Azure AD Connect: SyncRuleEditor.exe and why is targetAddress missing](https://blog.kloud.com.au/wp-content/uploads/2018/12/Kloud_vector_logo_mono_white.png){kind=logo}
[UPDATED] Azure AD Connect: SyncRuleEditor.exe and why is targetAddress missing
Originally blogged @ lucian.blog. Follow Lucian on Twitter @LucianFrango. Send Lucian an email.
Today is back to AAD Connect. I want to talk about Office 365 migrations and how they can be tricky with various options and scenarios around hybrid or non hybrid. On a recent project we were migrating a client from IBM Lotus Notes to Exchange Online in Office 365. The plan and proposed solution was designed to not use Exchange Server Hybrid on-premises and use Dell Software Migrator for a direct migration from on-premises to the cloud.
The client has never had Exchange Server on-premises before and was running a well-managed ADDS deployment spanning three sites across three continents. To allow for the schema requirements for Exchange Online, Exchange Server 2013 was downloaded and the ADDS schema was extended with that from Exchange Server 2013. All simple, standard stuff right?..