Microsoft Exchange 2010/2013/2016/O365/Hybrid

Built with site to site fail-over in mind I designed and deployed Exchange 2016 in an Active-Active setup across 2 sites. A software load balancer (HAProxy) has been placed in front of each Exchange server to automatically switch clients to the remote site in the event of a local server failure. HAProxy will monitor each Exchange server for HTTP failure codes in addition to checking TCP failures. It monitors services on Exchange individually to control the fail-over.

Inbound and Outbound emails are routed through a Barracuda V400 Spam and Virus Firewall, which monitors and compares messages against Barracuda’s spam checking rules. The Barracuda Spam Firewalls were deployed along with the Outlook plugin and LDAP authentication. This allows users to check and monitor their Quarantine and Spam that hasn’t been delivered to their mailbox, and redeliver rejected messages. Reducing IT overhead.

Each Exchange 2016 server is capable of acting as a Unified Messaging server for Skype for Business 2015. I’ve also successfully configured Exchange Online Unified Messaging for our Hybrid Migration.

In 2017 and 2018 we tackled an Exchange Hybrid Migration allowing us to migrate users to Office 365 and Exchange Online. I was responsible for the setup and configuration of ADFS and Azure AD Connect. I’ve created routing rules to allow both environments to send emails back and forth. I’ve also written PowerShell automation libraries to simplify the maintenance and upkeep of users in both On-Premise and Exchange Online situations.