How you will run the Hybrid Configuration Wizard?
We can download the HCW tool from ECP console or from Microsoft website https://aka.ms/HybridWizard we need to Exchange Org Admin credential and Office 365 Global Admin account to run the Hybrid Configuration Wizard.
What are the Exchange Hybrid Configuration features?
Below are the Hybrid Configuration feature
- Free/Busy Sharing: Free/Busy sharing enables calendar sharing between on-premise and Exchange Online users.
- MailTips: Both On-Premise and Exchange online senders can adjust messages they are composing to avoid NDR between organization.
- Online Archiving: Exchange Online organization hosts archive mailbox for both on-premise and Exchange Online users
- Outlook on the web redirection: Outlook on the web redirection provides single, common URL to access both on-premise and Exchange online mailboxes.
- Exchange Active Sync Redirection: Exchange ActiveSync clients will automatically have reconfigured when mailbox moved to Exchange online.
- Secure Mail: Secure mail enabled secure message delivery between the on-premise and Exchange Online organization via TLS protocol. On-Premise Exchange and Exchange Online mutually authentication through digital certificate subjects and email headers.
- Message Tracking to understand the mail flow
- Mailbox on boarding to Office 365 and off boarding to On-premise Exchange.
Where you will find the Hybrid Configuration Wizard logs?
Hybrid Configuration Wizard writes many information about the existing On-Premise Exchange Configuration and the changes done to implement the Hybrid Deployment. You can find the logs at this location %UserProfile%\AppData\Roaming\Microsoft\Exchange Hybrid Configuration from which Server the Hybrid Configuration Wizard was configured.
What are the benefits of Hybrid Configuration?
- Exchange On-Premise and Exchange Online users can share the free/busy information
- Secure Mail flow using Hybrid Configuration where the email routes via Exchange Online Protection
You can answer all the points under this question – What are the Exchange Hybrid Configuration features?
What is Hybrid Exchange Environment?
Hybrid Exchange Environment is the Cross forest Exchange deployment having mailboxes in On-Premise Exchange Infrastructure and also in Office 365 but both the users appear to have Same Email domain alias and other Exchange functionality.
What is the use of OAuth Authentication between Exchange and Exchange Online?
OAuth is an Authentication Protocol enables MRM, Exchange In-Place Discovery and Exchange In-Place Archiving on Cross Exchange Forest like Exchange Hybrid Environment. Hybrid Configuration Wizard will configure OAuth only when the environment is having Exchange 2013 Alone. On a mixed environment, HCW will not prompt for OAuth configuration but we can follow a series of steps to implement it manually.
How the free/busy sharing working between Exchange On-Premise and Exchange Online?
Implementing Federated sharing allow users in Exchange On-Premise to see the free/busy information for the user in Exchange Online. Running the Hybrid Configuration Wizard will configure the Organization Relationship with Exchange Online which helps the free/busy sharing working between On-Premise Exchange & Office 36.
What is federated sharing and federated delegation? – Low Priority
Federated Sharing (Organization Relationship) in Exchange 2013 allows users in Exchange 2013 or later organization to share free/busy information with other Exchange Organization. It provides granular control on the calendar sharing.
Federated Delegation formally known as Federated sharing in Exchange 2010. Federated delegation uses the Microsoft Federation Gateway, a cloud-based service offered by Microsoft, as the trust broker between your on-premises Exchange 2010 organization and other federated Exchange 2010 organizations.
How to Configure Federated Sharing and Federated Delegation? – Low Priority
If we want to enable free busy sharing between Exchange 2013 organizations, then configuring Federated Sharing helps to achieve it.
- Create a Federation Trust (between a Microsoft Exchange 2013 organization and the Azure Active Directory authentication system)
- Creation an Organization Relationship
- Create a Sharing Policy
- Create Autodiscover Public DNS Record
If we want to enable Free Busy sharing between an Exchange 2013 and Exchange 2010 Organization, Federated Sharing enabled at Exchange 2013 Organization and Federated Delegation to be done at Exchange 2010 SP2 side. Below the Federated Delegation steps done on Exchange 2010 Organization
- Create a Federation Trust (between a Microsoft Exchange 2010 organization and the Microsoft Federation Gateway)
- Create TXT records for Federated Delegation
- Configure the domain for Federation Delegation
- Create CNAME record for Autodiscover
- Create an Organization Relationship