|Long description||Hybrid migration provides integration between an on-premises Exchange organization and Microsoft 365 Exchange Online. It can be used in two scenarios: as a method of migration between an on-premises Exchange Server and Microsoft 365 (Exchange Online) or as a permanent state for your on-premises Exchange and Microsoft 365 organizations.|
A hybrid deployment offers companies the ability to extend the functionality of an existing on-premises Microsoft Exchange to Exchange Online. This provides a single space between an on-premises Exchange organization and Exchange Online in Microsoft 365.
The following topology example provides an overview of a typical Exchange 2016 deployment. With a single-forest, single-domain organization with two domain controllers and one Exchange 2016 server installed, we start deploying and configure a required Azure AD Connect server and use the Azure AD Connect password synchronization feature to let users log in with the same credentials for both their on-premises network account and their Microsoft 365 account. Then we complete the hybrid deployment prerequisites and use the Hybrid Configuration wizard to select options for the hybrid deployment.
Your new topology will have the following configuration:
Users can log in to the on-premises and Exchange Online organizations
with the same username and password ("single sign-on").
User mailboxes located on-premises and in the Exchange Online organizations will use the same email address domain.
All outbound mail is delivered to the Internet by the on-premises organization. The on-premises organization controls all messaging transport and serves as a relay for the Exchange Online organization ("centralized mail transport").
On-premises and Exchange Online organization users can share calendar free/busy information. Organization relationships configured between on-premises and Exchange Online also enable cross-premises message tracking, MailTips, and message search.
The same URL is used for the connection to mailboxes for both on-premises and Exchange Online users.
IT Partner responsibilities: #
- Analyze the current Exchange On-Premises solution
- Prepare the current configuration of Exchange and Active Directory for synchronization
- Set up synchronization of users and passwords
- Provide informational letters for users
- Migrate mailboxes
- Provide break-fix support related to migration issues
Client responsibilities #
- Coordinate Client resources and staff schedules
- Provide a dedicated point of contact responsible for working with IT Partner
- Provide access to physical and virtual servers and/or systems and services as needed. Provide remote and/or physical access to facility and systems required to complete the work
- Configure workstations and mobile devices
- Perform changes to internal and external DNS, as required
- Assist with identification of high-risk users (top executives and VIP users, users with 50 GB mailboxes or larger and/or 30 GB deleted folders or larger)
- Coordinate any outside vendor resources and schedules
- Configure all network equipment, such as load balancers, routers, firewalls, and switches.
- Review and approve engagement deliverables in a timely manner
Additional cost items not provided by the project #
- Customer team training (could be added as an additional service)
- Desktop software settings
- Unified Messaging (US) features cannot be used in a hybrid solution in conjunction with Microsoft 365. If you use this feature in your infrastructure, additional settings can be required depending on the solution you are using.
Upon completion of the project, we will provide a project closeout report. This document will indicate the final project status, including acceptance criteria matching, outstanding issues (if any), and the final budget. If you require more extensive documentation, it can be provided for an additional fee.
- You must have a Microsoft 365 tenant with Exchange Online licenses
- You must have access to your email domain DNS zone
- You need a full installation of Exchange 2010, 2013, or 2016 server in your environment with a valid UCC SSL certificate
The plan may vary depending on your needs.
- Kickoff meeting
- Pre-migration source system health check
- Creating users or AD connect tool configuration
- Migration planning
- Email migration start
- Email migration check
- Changing MX record to the new Microsoft 365 tenant
- Final email migration
- Post-migration tasks
Success Criteria #
- Users can access Exchange Online on their desktop PCs, mobile phones, and tablets from any place, any time
- Mailbox data is successfully migrated to Exchange online and accessible to all users
- All necessary transport rules are created and working
- Mail can be sent and received using Exchange online
- Exchange Online Protection is configured and working