Office 365 hybrid deployment with on-premises Exchange 2013 - overview questions
I'm tentatively proposing that one of my clients implement an Office 365 hybrid deployment.
The client is about ~25 employees. They currently have a pretty nice Microsoft server set up. Two on premises DCs (which replicate to each other), Fileservers (which replicate via DFSR), and two Exchange 2013 Servers (which replicate via a DAG). Each DC/FS/Exchange Server is a VM. They have two physical servers that run Hyper-V.
The problem they're having is that 1) remote users trying to access their mailboxes (via Outlook Anywhere or ActiveSync) are sucking up all the Internet bandwidth, and 2) They're also having trouble with spam issues for inbound/outbound email. Tons of spam arriving for inbound mail and outbound mail gets flagged as spam by other people. This is mostly because the on-premises Exchange Server is delivering outbound mail directly via MX records, and the inbound mail is scanned by an aging commercial anti-spam program (Symantec Mail Security) that does a pretty poor job.
This particular client is a non-profit and it turns out they're eligible to have as many free Office 365 E1 licenses as they want.
So what I'd like to do is deploy a hybrid Office 365 deployment where they can use their on-premises Exchange Server together with Office 365 and AD FS.
I'm hoping the end result will look like this:
1) Active Directory Federation Services provides single-sign-on and directory sync. This means the integration that users enjoy with the on-premises Exchange Server continues to work the same way: New user accounts that are created in Active Directory / Exchange Management Console have the same credentials as the users in Office 365, Outlook "automagically" configures itself when you open it just like it does with the on-premises Exchange Server. The Global Address Book is populated with the data in the on-premises directory, users don't have to remember two sets of passwords for their workstation + their email.
2) Mailbox data is replicated between the on-premises Exchange Servers and the Office 365 hosted servers
3) Users who are in the office access their mailbox directly via the on-premises Exchange Server like normal
4) Users who are out of the office or using smartphones access the mailbox via Office 365 cloud services
5) Outbound emails are routed through Office 365 and get delivered reliably and don't get flagged as spam by the recipient just like they would in a non-hybrid Office 365 subscription
6) Inbound emails pass through Office 365's anti-spam filters, and spam goes into the user's Junk Email just like they would in a non-hybrid Office 365 subscription
7) This is all doable with Office 365 E1 licenses
Technical implementation details aside.... is this an accurate picture of what the end result is going to look like assuming everything is done correctly?
Secondly... how long would it take to implement this assuming that you know what you're doing?
The client is about ~25 employees. They currently have a pretty nice Microsoft server set up. Two on premises DCs (which replicate to each other), Fileservers (which replicate via DFSR), and two Exchange 2013 Servers (which replicate via a DAG). Each DC/FS/Exchange Server is a VM. They have two physical servers that run Hyper-V.
The problem they're having is that 1) remote users trying to access their mailboxes (via Outlook Anywhere or ActiveSync) are sucking up all the Internet bandwidth, and 2) They're also having trouble with spam issues for inbound/outbound email. Tons of spam arriving for inbound mail and outbound mail gets flagged as spam by other people. This is mostly because the on-premises Exchange Server is delivering outbound mail directly via MX records, and the inbound mail is scanned by an aging commercial anti-spam program (Symantec Mail Security) that does a pretty poor job.
This particular client is a non-profit and it turns out they're eligible to have as many free Office 365 E1 licenses as they want.
So what I'd like to do is deploy a hybrid Office 365 deployment where they can use their on-premises Exchange Server together with Office 365 and AD FS.
I'm hoping the end result will look like this:
1) Active Directory Federation Services provides single-sign-on and directory sync. This means the integration that users enjoy with the on-premises Exchange Server continues to work the same way: New user accounts that are created in Active Directory / Exchange Management Console have the same credentials as the users in Office 365, Outlook "automagically" configures itself when you open it just like it does with the on-premises Exchange Server. The Global Address Book is populated with the data in the on-premises directory, users don't have to remember two sets of passwords for their workstation + their email.
2) Mailbox data is replicated between the on-premises Exchange Servers and the Office 365 hosted servers
3) Users who are in the office access their mailbox directly via the on-premises Exchange Server like normal
4) Users who are out of the office or using smartphones access the mailbox via Office 365 cloud services
5) Outbound emails are routed through Office 365 and get delivered reliably and don't get flagged as spam by the recipient just like they would in a non-hybrid Office 365 subscription
6) Inbound emails pass through Office 365's anti-spam filters, and spam goes into the user's Junk Email just like they would in a non-hybrid Office 365 subscription
7) This is all doable with Office 365 E1 licenses
Technical implementation details aside.... is this an accurate picture of what the end result is going to look like assuming everything is done correctly?
Secondly... how long would it take to implement this assuming that you know what you're doing?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.