Hybrid Deployment

Hybrid Deployment
Hybrid Architecture
Provisioned via DirSync
Exchange 2010 (HUB/CAS)
Secure Mail flow
Exchange Federation (Free/Busy, Mail Tips, Archive, etc.)
Exchange 2013 CAS & MBX
Mailbox data via Mailbox Replication Service (MRS)
On-premises Exchange org (Exchange 2007+)
Office 365
Hybrid – Features
 Cloud Based Email Archiving
 Secure Mail Routing between on premise / online
 Unified Global Address List
 Centralized mail flow – Outbound
 Single Outlook WebApp URL for Online / on Premise
 Move Mailbox On Premise to Online
 Centralized Management Console
 Message Tracking / Mail Tips / MultiMailbox Search
Hybrid – Deployment Components
 Microsoft Office 365
 Hybrid Configuration Wizard – Exchange On Premise
 Hybrid Servers – Minimum HUB + CAS
 Microsoft Federation Gateway
 Active Directory Synchronization
Hybrid – Deployment Types
 Exchange 2010 Based Hybrid Deployment :
 Exchange 2010-based hybrid deployments can either be on-premises organizations that are
homogenous Exchange 2010 organizations, or Exchange 2003 and Exchange 2007 on-premises
organizations that have added Exchange 2010 servers as part of configuring a hybrid deployment
with Office 365
 Exchange 2013 Based Hybrid Deployment
 All on-premises Exchange 2013 servers must have installed Cumulative Update 1 (CU1) or greater
for Exchange 2013 to support hybrid functionality with Office 365.
SSO with Hybrid Deployments
 Exchange Online Archiving
 Policy Control
 Access Control
 Security
 Support for Strong Authentication
Hybrid with Certificates
 Active Directory Federation Services
 Exchange Services – Autodiscover / Transport / OWA / Web Services
 Exchange Federation
 Third party certificate – multiple server or each server
 Support for Strong Authentication
Hybrid Deployment Compatibility
On-premises Exchange
environment
Exchange 2010-based
hybrid with v14 tenant
Exchange 2010-based
hybrid with v15 tenant
Exchange 2013-based
hybrid with v15 tenant
Exchange 2013 (CU1)
Not Supported
Not applicable
Supported
Exchange 2010 SP3
Supported
Supported
Supported
Exchange 2010 SP2
Supported
Not supported
Not supported
Exchange 2010 SP1
Supported
Not supported
Not supported
Exchange 2007 SP3 RU10
Supported
Supported
Supported
Exchange 2007 SP3
Supported
Not supported
Not supported
Exchange 2003 SP2
Supported
Supported
Not supported
Hybrid – Prerequisites
 Exchange 2010(SP2) CAS & HUB, if legacy free busy via PF then with MBX role too / Exchange
2013 CAS/HUB
 Office 365 Subscription (Enterprise) & SMTP domain to be registered
 MS Directory Tool Server Installed & Enabled on Office 365 Portal
 Adding Exchange online to EMC
 Publishing EWS & Autodiscover with public certificate – to access on premise from Cloud
 AD Federation Services for SSO (Optional)
 Remote Connectivity Analyzer will be of great help to check webservices
Hybrid – Improvements







Hybrid Deployment Process
Sign up for
Office 365
Register
domains
with Office
365
Deploy Office
365
Directory
Sync
Install
Exchange
2010 (HUB /
CAS)/2013
CAS & MBX
Servers
(Edge opt)
Publish the
CAS Server
(Assign SSL
certificate,
firewall rules)
Run the
Hybrid
Wizard
Hybrid 2010 – Hybrid Configuration Wizard
DEMO
Exchange 2010 Hybrid Support
 Exchange 2010 SP3 will be compatible with current and new O365 tenants
 Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from
Exchange 2003)
Hybrid – End User Experience
 Multiple Identity Options – DirSync / ADFS / Cloud only
 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
Hybrid Configuration Engine
Step 2
The Hybrid Configuration Engine reads
the “desired state” stored on the
HybridConfiguration Active Directory
object.
Step 3
The Hybrid Configuration Engine
connects via Remote PowerShell to
both the on-premises and Exchange
Online organizations.
Step 4
The Hybrid Configuration Engine
discovers topology data and current
configuration from the on-premises
Exchange organization and the
Exchange Online organization.
Step 5
Based on the desired state, topology
data, and current configuration, across
both the on-premises Exchange and
Exchange Online organizations, the
Hybrid Configuration Engine
establishes the “difference” and then
executes configuration tasks to
establish the “desired state.”
EXCHANGE ONLINE
ORGANIZATION
ON-PREMISES EXCHANGE ORGANIZATION
Exchange Server Level
Configuration
Domain Level
Configuration Objects
Organization Level
Configuration Objects
(Mailbox Replication Service
Proxy, Certificate Validation,
Exchange Web Service Virtual
Directory Validation, & Receive
Connector)
(Accepted Domains, Remote
Domains, &
E-mail Address Policies)
(Exchange Federation Trust,
Organization Relationship,
Availability Address Space, &
Send Connector)
2
4
REMOTE
POWERSHELL
5
INTERNET
Step 1
The Update-HybridConfiguration
cmdlet triggers the Hybrid
Configuration Engine to start.
Organization Level
Configuration Objects
(Exchange Federation Trust,
Organization Relationship,
Forefront Inbound Connector,
& Forefront Outbound
Connector)
5
Hybrid Configuration
Object
REMOTE
POWERSHELL
1
Exchange
Management
Tools
4
Hybrid Configuration Engine
Domain Level
Configuration Objects
(Accepted Domains &
Remote Domains)
Third Party Email
Security System
External recipient
Secure Mail
Diana
On-premises mailbox
Exchange
Encrypted & authenticated
mail flow
Charles
Cloud mailbox
Exchange Hybrid Mail Flow
Cutover migration
Staged migration
Hybrid
X
Exchange 2000
X
Exchange 2003
X
X
X
X
Exchange 2007
X
X
X
X
Exchange 2010
X
X
Notes/Domino
X
GroupWise
X
Other
X
IMAP migration
Exchange 5.5
X
Questions?

Download Report