<div>
About 30 users, 50 mailboxes.<br />
Ultimately a Hybrid setup primarily to avoid disruption (3rd party app integration and EAS device etc..) and to slowly migrate all to cloud and decommission exchange.<br />
Not confident with cut over migration because of this.<br />
<br />
Of your list i would say i understand:<br />
<br />

<div class="bullet">
Plan for network devices that connect to Office 365 services<br />
Office 365 Firewall and Proxy Preparation<br />
Register Public and Private DNS Records for Office 365 workloads<br />
Customer to reduce MX DNS record TTL Value<br />
Implementation of SPF record for Exchange Online (if applicable)<br />
Add additional domains to office 365<br />
Prepare for setup with health, readiness, and connectivity checks<br />
Prepare to provision users through directory synchronization<br />
Clean Up Active Directory<br />
Run IdFix tool<br />
Deploy your directory synchronization server hardware<br />
Integrating your on-premises identities with Azure Active Directory<br />
Hybrid deployment prerequisites Exchange 2013<br />
Deploy your Exchange Hybrid Server Hardware (only if not already deployed)<br />
Acquire Certificates for Exchange 2013 Hybrid Server(s)<br />
Update Exchange 2013 to the latest Service Pack and Cumulative Update<br />
Verify On-Premises Hybrid/Exchange connectivity (EWS &amp;&nbsp;Autodiscover)<br />
Enable Mailbox Replication Service on Exchange 2013
</div>
<br />
So my question still stands and im concerned how far i can test without affecting production with a hybrid setup with adconnect...<br />
<br />
Were looking at just Exchange Online Plan 1 as we will not allow anywhere access, office, SharePoint etc..
</div>


<div>
Will i need to setup the federation in exchange or just install adconnect?<br />
Yes, read about cutover, but we'd prefer to run hybrid so less is affected on prem.
</div>


<div>
<div class="content wysiwyg-content">
Hello<br />
<br />
I am in the process of testing o365. &nbsp; &nbsp;Id now like to test a hybrid setup between our production exchange 2010 servers and o365 if possible.<br />
<br />
Can this be done easily? &nbsp;Does it change any ADExchange data? &nbsp;Can i revert to pure on premise after the test? <br />
Am i correct in saying i need to install Adconnect on a member server (to populate o365 account data) and/or run the hybrid setup wizard in the EAC on o365 to create the federated trust etc?<br />
<br />
Thanks
</div>
</div>


Hello

I am in the process of testing o365.    Id now like to test a hybrid setup between our production exchange 2010 servers and o365 if possible.

Can this be done easily?  Does it change any ADExchange data?  Can i revert to pure on premise after the test? 
Am i correct in saying i need to install Adconnect on a member server (to populate o365 account data) and/or run the hybrid setup wizard in the EAC on o365 to create the federated trust etc?

Thanks

Testing a Hybrid o365/Excahnge 2010 Setup

Office 365 is a group of software plus services subscriptions that provides productivity software and related services to its subscribers. Office 365 allows the use of Microsoft Office apps on Windows and OS X, provides storage space on Microsoft's cloud storage service OneDrive, and grants 60 Skype minutes per month. Office 365 includes e-mail and social networking services through hosted versions of Exchange Server, Skype for Business Server, SharePoint and Office Online, integration with Yammer, as well as access to the Office software. All of Office 365's components can be managed and configured through an online portal; users can be added manually, imported from a CSV file, or Office 365 can be set up for single sign-on with a local Active Directory using Active Directory Federation Services.

Microsoft 365

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.