1. Office 365 – Understanding Migrations: Hybrid migrations
Microsoft Office365
9/8/2018
Office 365 – Understanding Migrations: Hybrid migrations
October 2013
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Session Overview
This session details Step 3 (Enhanced) Hybrid migrations for deploying Office 365 services. Understand the implications of this deployment approach and the steps required to expand the service offerings as part of FastTrack Enhanced phase.

3. Agenda Summary of migration options
Introduction to Hybrid capabilities
Exchange Server 2013 Hybrid improvements
Infrastructure dependencies
Step by steps deployments
Hybrid migration

4. Summary of Migration Options *
PST Migration
Import of Archived/Offline Mail
IMAP migration (IMAP)
Supports wide range of platforms
only (no calendar, contacts, or tasks)
Cutover Exchange Migration (CEM)
Good for fast, cutover migrations – up to 2,000 mailboxes
No migration tool or computer required on-premises
Staged Exchange Migration (SEM)
No server required on-premises
Identity federation with on-premises directory
Hybrid
Hybrid deployment
Manage users on-premises and online
Enables cross-premises calendaring, smooth migration, and easy off-boarding
PST Migration
IMAP migration
Cutover migration
Staged migration
Hybrid 2010
Hybrid 2013
Exchange 5.5 X
Exchange 2000
Exchange 2003
Exchange 2007
Exchange 2010
Exchange 2013 x
Notes/Domino
GroupWise
Other
Here is a summary of the migration tools and options we have with Exchange Online. Customers have choices to move to the cloud quickly with native migration options, to take a more measured approach to the cloud according to their business requirements or maintaining mailboxes on-premises and online for a longer period of time.
Note: Exchange 2013 hybrid does not work with Exchange However, Exchange 2003 customers will be able to deploy Exchange 2010 hybrid with Exchange Online 15 in order to have a smoother experience to migrate to the cloud if other options are not ideal for their business requirements. (more details in the hybrid deployment section later in the module)
* Additional options available with tools from migration partners

5. Self Service or Admin Driven Options
Control
Deployment Type
Description
Self Service
New mailbox
User receives new “green field” mailbox. i.e. user is on boarded to without data migration.
New mailbox + Outlook PST
User receives new mailbox and either attaches or imports PST files for access to pre-Office 365 data.
New mailbox + Connected Accounts
User receives new mailbox and configures connected accounts via OWA.
Admin-Driven
New mailbox + PST import (central)
User receives a new mailbox and admin uses PST Export features of Exchange and 3rd Party tools to import PST data into the user’s Exchange Online mailbox.
These are “non-migration” options for onboarding to Exchange Online.
This options are not discussed further in this module other than for awareness here.
Additional information about Connected Accounts &mode=Desktop&helpid=ms.exch.owao.New
Additional information about the PST Capture Tool

6. Hybrid Deployments Microsoft Office365 9/8/2018-
- and
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

7. Hybrid Key Features and Benefits
Delegated authentication for on-premises/cloud web services
Enables Free/Busy, calendar sharing, message tracking, online archive, and more
Federation Trust
Manage all of your Exchange functions, whether cloud or on-premises from the same place - Exchange Administration Center (EAC)
Integrated Admin Experience
Remote move migration (Online mailbox moves)
Preserve the Outlook profile and offline file (OST)
Leverages the Mailbox Replication Service (MRS)
Native Mailbox Move
Authenticated and encrypted mail flow
Preserves the internal Exchange messages headers
Support for compliance mail flow scenarios (central transport)
Secure Mail Flow

8. Hybrid Coexistence Feature Comparison
Simple
Hybrid
Mail routing between on-premises and cloud (recipients on either side) 
Mail routing with shared namespace (if desired) on both sides
Unified GAL
Free/Busy and calendar sharing cross-premises
Out of Office understands that cross-premises is “internal” to the organization
Mailtips, messaging tracking, and mailbox search work cross-premises
OWA redirection cross-premise (single OWA URL for both on-premises and cloud)
Single tool to manage cross-premises Exchange functions (including migrations)
Mailbox moves support both onboarding and offboarding
No outlook reconfiguration or OST resync required after mailbox migration
Preserve auth header (ensure internal is not spam, resolve against GAL, etc.)
Centralized mail flow , ensures that all routes inbound/outbound via on-prem
This is what you get when you have Hybrid coexistence.
Some features are optional and require more configuration than others.

9. Hybrid Coexistence Feature Example
Cross-Premises Free/Busy and Calendar Sharing
Creates the look and feel of a single, seamless organization for meeting scheduling and management of calendars
Works with any supported Outlook client

10. Hybrid Coexistence Feature Example
Cross-Premises MailTips
Correct evaluation of “Internal” vs. “External” organization context
Allows awareness and correct Outlook representation of MailTips

11. Hybrid Coexistence Feature Example
Cross-Premises Mail Flow
Preserves internal organizational headers (e.g. auth header)
Message is considered “trusted” and resolve the sender to rich recipient information in the GAL (not SMTP address)
Restrictions specified for that recipient are honored

12. Hybrid Coexistence Feature Example
Microsoft Office365
9/8/2018
Hybrid Coexistence Feature Example
Single OWA URL
Ensures a good end-user experience as mailboxes are moved in-and-out of the cloud since OWA URL remains unchanged (points to on-premises “hybrid” CAS)
Log in experience can be improved by adding domain name into your cloud URL so that you can access your cloud mailbox without the interruption of Go There page
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. Hybrid Features and Benefits Summary
Microsoft Office365
9/8/2018
Hybrid Features and Benefits Summary
Makes your on-premises organization and cloud organization work together like a single, seamless organization
Offers near-parity of features/experience on-premises and in the cloud
Seamless interactions between on-premises and cloud mailboxes
Migrations in and out of the cloud transparent to end-user
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. 2013 Hybrid Requirements Exchange 2013 CAS/MBX server on-premises
Microsoft Office365
9/8/2018
2013 Hybrid Requirements
Exchange 2013 CAS/MBX server on-premises
Hybrid configuration in place
On-premises config, O365 config, federation using MFG, certificates, etc.
Much of the config is automated by the Hybrid Configuration Wizard
SMTP domain(s) configured in O365 tenant
Directory Sync tool enabled in O365 tenant
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. 2013 Hybrid Limitations Exchange 2003 is not supported (*)
Microsoft Office365
9/8/2018
2013 Hybrid Limitations
Exchange 2003 is not supported (*)
Delegation Coexistence cross-premises (delegate permissions are migrated when users are in the same batch)
Migration of Send As/Full Access permissions
* For Exchange organization running Exchange 2003, consider using Exchange 2010 SP3 Hybrid deployment
Note that Exchange 2013 hybrid no longer supports Exchange 2003
Customers who have Exchange 2003 can still use Exchange 2010 hybrid
Customers must be aware that Exchange Server 2003 (SP2) will end of life on April 8th 2014
Exchange 2010 hybrid with service pack 3 (with latest RU always recommend – RU2 as of Sept. 2013) is able to connect to a ‘new Office 365’ tenant (wave 15)
See sp3.aspx
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Hybrid – User Experience
Microsoft Office365
9/8/2018
Hybrid – User Experience
If configured for SSO, users login with their AD credentials. Otherwise, admin needs to distribute new password to user.
User’s current Outlook profile is updated with the Exchange Online server name via Autodiscover.
Offline files (OST files) do not have to be recreated.
If using Outlook at the time of the mailbox move, user is prompted to close and reopen Outlook.
Mailbox moves from Exchange 2003 are offline moves. The mailbox is locked for the duration of the move. Exchange 2003 is only supported by an Exchange 2010 SP3 based hybrid deployment.
Mailbox moves from Exchange 2007, 2010 and 2013 are online moves. User can continue to use mailbox during the move. Once the move is completed, the user is prompted to closer and reopen Outlook.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. Hybrid User Experience - Autodiscover
Microsoft Office365
9/8/2018
Hybrid User Experience - Autodiscover
On-premises Systems
Office 365
Remote Mailbox
Primary SMTP address:
Remote Routing address:
Mailbox
Primary SMTP address:
Secondary SMTP address: AD
Forest
Outlook profile automatic reconfiguration post mailbox move when user first reconnect to his/her mailbox
Exchange 2013 CAS
Exchange Online
Outlook profile updated.
OST rebuild not required!
Mailbox server information
Local Exchange passes a redirect to “contoso.mail.onmicrosoft.com”
Where is my mailbox?
Authentication success
Outlook attempts to discover endpoint through DNS record “autodiscover.contoso.mail.onmicrosoft.com”
Request authentication
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. 2013 Hybrid Improvements (1 of 2)
Microsoft Office365
9/8/2018
2013 Hybrid Improvements (1 of 2)
Adaptive HCW HCW adapts to individual setup requirements and presents only necessary questions. Automatically gathers information whenever possible.
Integrated Support for Edge HCW supports configuring Exch2010 Edge Transport servers directly within the wizard.
Enhanced Secure Mail Simpler to configure and no longer dependent on static IP addresses in the connector configuration.
More information in these EHLO blogs: hybrid.aspx hybrid.aspx
See Hybrid on technet:
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19. 2013 Hybrid Improvements (2 of 2)
Microsoft Office365
9/8/2018
2013 Hybrid Improvements (2 of 2)
Flexible Exchange Online Protection (EOP) Connection and Internet Mail Routing Support for updating MX and directing all inbound Internet mail to EOP (*) at any stage of the hybrid deployment – before, during or after hybrid configuration. * May require additonnal standalone EOP licenses to cover on-premises users
Improved Centralized Mail Transport Added flexibility and capability – centralized mail transport is supported even when pointing MX to EOP.
Integrated Mailbox Migration and Move Wizard One wizard regardless of scenario – hybrid, staged, cutover, or IMAP.
More information in these EHLO blogs: hybrid.aspx hybrid.aspx
See Hybrid on technet:
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. 2013 Hybrid High-Level Architecture
Microsoft Office365
9/8/2018
2013 Hybrid High-Level Architecture
On-premises Exchange Org
Office 365
Office 365 Directory Synchronization
App
Users, Groups, Contacts via DirSync
Secure Mail Flow
Sharing (free/busy, MailTips, archive, etc.)
Mailbox Data via MRS
Existing Exchange 2007 or later
Exchange 2013 CAS and MBX
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21. Microsoft Office365
9/8/2018
Exchange 2013 hybrid deployment from an existing Exchange 2007 or 2010 environment—no Edge Transport server
1. Prepare
Install Exchange SP and/or RU/CU across the ORG
Prepare AD with Exchange 2013 (schema, Org, domains)
Clients
autodiscover.contoso.com
mail.contoso.com
Office 365
Autodiscover & EWS 5
SMTP
2. Deploy Exchange 2013 CU1 (or above) servers
Install both Exchange 2013 MBX and CAS servers
Set an ExternalUrl for the Exchange Web Services vDir 4 1 2
3. Exchange 2007 – Create legacy namespace
Create DNS record point to legacy Exchange 2007 CAS
Exchange 2010 or 2007 Servers
E2010 or 2007 Hub
E2010 or 2007 CAS 3
E2013 CAS
3 bis. Obtain and Deploy Certificates
Obtain and deploy certificates on Exchange 2013 CAS
Exchange Deploy certificates on Exchange 2007 CAS
SP/RU
SP/RU
For hybrid see:
Exchange Server 2010 org. : requires 2010 SP3 to be deployed on ALL server in the org.
Exchange Server 2007 org. : Requires 2007 SP3 RU10 (or above) to be deployed on ALL servers (caution setup doesn’t check against RU version – cannot check as not in AD)
vDir update is for Exchange 2007 (when legacy namespace is deployed)
Use to validate endpoints/connectivity
Intranet site
4. Publish protocols externally
Create public DNS A records for the EWS and SMTP endpoints
Validate using Remote Connectivity Analyzer 6 7
5. Switch autodiscover namespace to Ex2013 CAS
Change the public autodiscover DNS record to resolve to Exchange 2013 CAS and update vDirs (and re-validate)
E2010 or 2007 MBX
E2013 MBX
6. Run the Hybrid Configuration Wizard
Internet facing site
7. Move mailboxes
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

22. 2013 Hybrid Deployment Flow from an existing Exchange 2007 or 2010 environment—with Edge Transport server (2010 Edge)
1. Prepare
Install Exchange SP and/or updates across the ORG
Prepare AD with E2013 schema
Clients
autodiscover.contoso.com
mail.contoso.com
Office 365
Autodiscover & EWS 5
SMTP
2. Deploy Exchange 2013 servers
Install both E2013 MBX and CAS servers
Install E2010 EDGE servers (if not already deployed)
Set an ExternalUrl for the Exchange Web Services vdir 1 2 4
E2010 EDGE
Exchange 2010 or 2007 Servers
3. Obtain and Deploy Certificates
Obtain and deploy certificates on E2013 CAS servers
& E2010 EDGE servers
If Exchange 2007 – create legacay namespace (DNS and certs)
E2010 or 2007 Hub
E2010 or 2007 CAS 3
E2013 CAS
SP/RU
SP/RU
4. Publish protocols externally
Create public DNS A records for the EWS and SMTP endpoints
Validate using Remote Connectivity Analyzer
E2007 rollup (SP3 RU10 and above) and E2010 (SP3) – Edge transport servers require the same SP/RU as MBX/CAS/HT
Note that E2013 MBX is required (in E2013 transport service runs on MBX server)
Cert on E2013 CAS for Autodiscover and on E2013 MBX server for secure mail flow (sending) to O365
We refer to Edge Transport 2010 – it could be an Edge server 2007 if source org is running Exchange server 2007
Intranet site 6
5. Switch autodiscover namespace to E2013 CAS
Change the public autodiscover DNS record to resolve to E2013 CAS
E2010 or 2007 MBX 7
E2013 MBX
6. Run the Hybrid Configuration Wizard
Internet facing site
7. Move mailboxes

23. Hybrid Configuration Wizard
Microsoft Office365
9/8/2018
Hybrid Configuration Wizard
Start HWC from on-premises EAC
Sign-in to Office 365 (non ADFS)*
and re-launch the HCW
Confirm running the wizard
Select hybrid domain*
View/Copy domain proof token*
Choose transport options
Choose receive 2013 CAS server(s)
Choose send 2013 MBX server(s)
Select transport certificate
Enter external FQDN 2013 CAS
Enter Org Management AD account
Enter Global Admin O365 account
Choose Update to configure hybrid
Wait for HCW updates to complete
Review instructions post HCW completion
EAC user interface has significant changes.
Requirements and sequence of tasks is very similar to Exchange 2010 SP2.
Step 3 is adaptive – question is not asked if tenant has a single verified domain.
Step 4 is adaptive – question is not asked if the domain has already been federated.
* Adaptive steps
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24. Exchange 2013 Tenant Compatibility
Microsoft Office365
9/8/2018
Exchange 2013 Tenant Compatibility
Exchange 2013 is only supported against the new Office 365 tenant (*)
Former O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises
Exchange 2013 Setup and HCW include a tenant version check
* Tenants with the updated bleu UI
“New Office 365” is ‘Wave 15’
Version checks
Test #1 – version 15 or above
Test #2 – wave 14 tenant has been fully upgraded to 15
Exchange 2013 CU1 minimum
The setup check occurs once during the PrepareAD phase
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25. Exchange 2010 Hybrid Support
Microsoft Office365
9/8/2018
Exchange 2010 Hybrid Support
Exchange 2010 SP3 is compatible with Office 365 and new Office 365 tenants
Exchange 2010 based hybrid deployments will continue to support Exchange 2003 coexistence (*) with the new O365 tenants
Once the new O365 service is launched, Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)
* Exchange 2003 is going to end-of-life in April 2014
Office 365 = Wave 14
New Office 365 = Wave 15
Be aware that Exchange 2003 is going to end of life in April 2014
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

26. Hybrid Deployments/configuration Questions?
Microsoft Office365
9/8/2018
Hybrid Deployments/configuration Questions?
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

27. Migration Interfaces EAC and PowerShell Microsoft Office365 9/8/2018
For remote mailbox migration - See < US/library/ms.exch.eac.NewMigrationBatch_RemoteMove(EXCHG.150).aspx?v= &l=1&s=BPOS_S_E15 _0>
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

28. Exchange Admin Center (EAC)
In EAC, select
recipients | migration
Migration Tool
launched from
Exchange Admin Center (EAC)
Select Migrate to Exchange Online
All migration types can be launched from EAC
Hybrid mailbox move is now an option here.
Start migration wizard
Choose hybrid remote move and follow prompts

29. Migration Tool also available via PowerShell Set of Migration Cmdlets
> New-MigrationBatch
> Start-MigrationBatch
> Get-MigrationBatch
> Get-MigrationStatus
> Complete-Migration
> Test-MigrationServerAvailability
New!
> Get-MigrationBatch -Diagnostic
Set of Hybrid Move Cmdlets
> New-MoveRequest
> Get-MoveRequest
> Get-MoveRequestStatistics
> Suspend-MoveRequest
> Resume-MoveRequest
> Remove-MoveRequest
Migration Tool
also available
via PowerShell
Diaginostic switch improves troubleshooting
Migration Batch cmdlets can also start a hybrid move
These are the PowerShell cmdlets used with migrations.
“MigrationBatch” cmdlets can now also be used with hybrid mailbox moves.
“MoveRequest” cmdlets continue to work with hybrid mailbox moves.
Hybrid move cmdlets continue to be available

30. Mailbox migrations (remove move) Questions?
Microsoft Office365
9/8/2018
Mailbox migrations (remove move) Questions?
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

31. Users and mailboxes management

32. Mailboxes / users management
Microsoft Office365
9/8/2018
Mailboxes / users management
As dirsync is in place, AD on-premises is mastering the directory objects
Mailbox creation is a remote mailbox creation
Impact of on-premises objects deletion
When deleting the user’s object dirsync will flow the deletion and mailbox will be deleted
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

33. Questions?

34. 9/8/2018
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

35. Additional Resources Simple Migrations Outlook.com Help
Microsoft Office365
9/8/2018
Outlook.com Help
Migration to Exchange online
IMAP Migrations
Cutover Exchange Migrations
Staged Exchange Migrations
Additional Resources
Simple
Migrations
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

36. Additional Resources Hybrid Deployments Exchange Team Blog TechNet
Microsoft Office365
9/8/2018
Exchange Team Blog
Introduction to Hybrid
Deploying Hybrid (Exchange 2013)
Managing Hybrid (Exchange 2013)
Decommissioning Hybrid (2010 related article)
TechNet
Hybrid Deployments
Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard
Additional Resources
Hybrid
Deployments
Introduction to HCW in Technet:
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

37. Additional Resources Tools Exchange Remote Connectivity Analyzer
Microsoft Office365
9/8/2018
Exchange Remote Connectivity Analyzer
Free & Busy troubleshooter
Server -
Client -
Exchange Client Network Bandwidth Calculator
PST Capture
PowerShell Scripts
Additional Resources
Tools
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

38. 9/8/2018
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.