Jul 17 2017 09:18 AM
Jul 17 2017 09:18 AM
In the current article, we will review:
The term Hybrid configuration or a Hybrid environment, describe a scenario in which two separated Exchange organizations that belong to different Active Directory forests are working as a “one unit”.
The term Hybrid configuration was created, for describing this type of relationship between the Exchange On-Premise infrastructure and the cloud (Exchange Online) infrastructure.
For example, in the following diagram, we see the logical concept of Hybrid environment.
The Public Domain name: o365info.com, configured as a “shared Domain”. The meaning is that two separate Exchange infrastructure “represent” this domain name or shared between them the same domain name.
When looking at the diagram, we can see two recipients: Bob@o365info.com andAlice@o365info.com
Technically, the recipient mailboxes must be configured on the Exchange on-Premises server or at the Exchange Online server, but logically, Bob and Alice don’t know where their mailboxes hosted.
In case that Bob mailbox is hosted on the Exchange on-Premises server and Alice’s mailbox is hosted on an Exchange Online server, Bob and Alice will have all the standard Exchange services such as: Free\Busy time, mail tips and more as if they are hosted in the same Exchange organization. The reason is that the Hybrid environment, “connect” the two distinct Exchange environments and making them appear as one entity.
Hybrid configuration relationships and Trust concept
As mentioned before, the Hybrid configuration was designed for “connecting” two different Exchange environments and make them operate as one entity. A trust concept implements the “glow” between the two distinct environments.
The Hybrid configuration and the “Trust model” enable each of the “end points” (Exchange on-Premises and Exchange Online) to:
Simple Exchange on-Premises environment versus complicated environment.
The term “Hybrid configuration” could use in describing a very simple scenario in which the organization has only one Exchange on-Premises server, who serves as a Hybrid server and is responsible for creating the “communication channel” between the on-Premises environment and the “cloud” (Exchange Online).
Another scenario of Hybrid configuration could be a more complicated scenario, which is more common in enterprise environments that have complicated Exchange on-Premises infrastructure.
In this scenario, the “relationship” between the Exchange Online and the “on-Premises Exchange infrastructure” could be divided into many “communication channels” with different\separated Exchange on-Premises servers.
For example – the mail flow between Exchange on-Premises and Exchange Online could be implemented by using a “dedicated” Exchange on-Premises server which will be configured for sending mail to Exchange Online and, other Exchange on-Premises server which will be configured to “accept” mail from Exchange Online.
Another Exchange on-Premises server could assign to different roles\services such as dedicated Exchange on-Premises server who will provide AutoDiscover services, dedicated Exchange on-Premises server who will provide EWS services and so on.
Pre-requirements for Hybrid deployment in Office 365
In the next sections, we will review each of the components that includes in the “Pre-requirements for Hybrid environment list.”
1. Exchange Hybrid Server Version
The term “Exchange Hybrid server” is just a logical term that describes Microsoft Exchange server which can be a part of a Hybrid environment.
Note – the Hybrid environment based on two different “end point” such as Exchange on-Premises environment and the “cloud” (Exchange Online) environment. At the current time, the “cloud side” of the Hybrid configuration is based on Exchange 2013 SP1 technology.
The Exchange on-Premises server “Hybrid server” could be implemented by using:
Exchange 2010 SP3 as Hybrid server
In case that we want to use an Exchange 2010 as a Hybrid server, the minimum requirement is service pack 3. Besides of the requirement for Service Pack 3, the best practice is: to install the most updated Exchange Rollup versions because each of the software updates (Exchange Rollup) includes a solution to issues\problem that was discovered and the fixed is included in the Rollups.
Many times the customer or the organization IT will “resist” to the recommendation of “installing the most updated Exchange rollup“ but, it’s important to emphasize that installing the most updated Rollups can prevent many of the future problems and consider as an important factor in the process of building the Hybrid environment.
The following quotation relates to Rollups 4 for Exchange 2010 SP3, but you get the idea.
Additionally, we recommend installing future Update Rollups 4 for Exchange 2010 SP3 on all your hybrid servers. Microsoft releases update rollup packages approximately every six to eight weeks. The rollup packages are available via Microsoft Update and the Microsoft Download Center. In the Search box on the Microsoft Download Center, type “Exchange 2010 SP3 updates rollup” to find links to the rollup packages for Exchange 2010 SP3.
[Source of information: Understanding Hybrid Servers in Exchange 2010 Hybrid Deployments ]
Download link for the required Exchange on-Premises server software updates Exchange 2010 | How can I know what is the current Exchange Rollup?
In case that you want to get information about the existing status of the Exchange 2010 on-Premises server, you can view the current version by using the Help menu and click on the About Exchange server 2010.
In the following screenshot, we can see that the Exchange on-Premises server version is:14.03.0.195.001
So the next question could be: how can I know what is the Exchange on-Premises server service pack or rollup version based on this number? To be able to “translate” the value to a clearer information, we can use the article: Exchange Server and Update Rollups Build Numbers
In the following screenshot, we can see that the version number: 220.127.116.11 is “telling” us that the Exchange 2010 on-Premises server includes an installation of Service Pack 3 + Rollup 6 for Exchange 2010 SP3.
In this case, we will need to download and install to most updated Rollup (for example Rollup 9)
The Cumulative Update (CU), Rollup, and Service Packs you have running on the on-premises server should also not be overlooked. Under normal circumstances we support you being no more than two updates behind the currently released update for Exchange; however, for hybrid environments, we are stricter, and you should not be more than one build behind.
If the latest update is Exchange 2013 CU9, then you must have either Exchange 2013 CU9 or CU8 to be considered in a supported state. We are stricter with our hybrid requirements because of how tightly the on-premises and Exchange Online environments will be coupled together. For more information on our available updates please go here.
[Source of information – Keep Exchange up to date]
New Hybrid server versus existing Exchange On-Premise
In case that the organization Exchange infrastructure based on older versions of Exchange such as Exchange 2003, 2007, we will need to “add” or install a new Exchange on-Premises server (2010 SP3 or 2013) that will serve as the “Hybrid server.”
The “New” Exchange On-Premise Hybrid server can implement as Exchange 2010 or Exchange 2013 or Exchange 2016 but, the best practice is to install Exchange 2016 server instead Exchange 2013 or 2010 because Exchange 2016 includes improving features that relate to the Hybrid environment.
You can read more information about the improvement in Exchange On-Premise 2016:
Exchange Server 2016 Hybrid Perks
Microsoft released its Exchange Server 2016 product back in October. While the new product is an Exchange Server 2013 facelift of sorts, it was built based on Microsoft's Exchange Online service. Exchange Server 2016 has improved backend search and e-discovery capabilities, plus improved Outlook client support, among other features.
It has other hybrid support benefits, according to a Microsoft TechNet library article updated in late January. Those benefits include:
2. Exchange On-Premise Hybrid Server | Public IP Address And Public Name (FQDN)
Hybrid configuration is all about enabling Exchange On-Premise server which is configured as “Hybrid server” to create a communication channel with the Exchange Online infrastructure that exists in a public network.
To be able to communicate hosts or “endpoint” on a Public network, the Exchange Hybrid server must have:
Note – In case that we use more complicated scenario in which the on-Premises environment is “represented” by more than one Exchange on-Premises server, each of the Exchange On-Premise servers will need to have a dedicated Public IP.
For example, in case that the Outbound mail flow based on two Exchange on-Premises servers who can send mail to the Exchange Online server, each of this server will need to have a dedicated Public IP address.
How can I know what is the Public name of the Exchange On-Premise?
The simple answer is that if you are the Exchange On-Premise Administrator, you supposed to know what the Exchange On-Premise public name is but, in some scenarios, we will have to configure and hybrid deployment in an environment which we are not familiar with.
One option to get information about the “Public name” of the Exchange On-Premise server is by looking at the “External URL” that appears in the “client access” section under server configuration in the Exchange MMC (when we use Exchange 2010 MMC).
In the following example, we will look under the “Server configuration\Client access\EX01”
Exchange server “publish a ” couple of services. In our example, we look at the ECP tab (the ECP tab includes the Internal + External URL of the Exchange server using the web management interface).
We can see that the “pubic name” (External URL) of the Exchange On-Premise is:mail.o365info.com
Note – the External URL information includes parts that are only relevant for the URL syntax. Part of the URL is the host FQDN (Fully Qualified Domain Name). In our scenario, we are looking only for the Public Exchange server name (mail.o365info.com).
Verify that the Exchange Hybrid Server Public name (FQDN) is mapped to his Public IP
The verification process of the Exchange On-Premise Public IP is very simple. Open the command prompt and Ping the Public name of the Exchange On-Premise server. In our example, the Exchange On-Premise public name is: mail.o365info.com
In the following screenshot, we can see that we got as an “answer” the public IP of the Exchange On-Premise server.
One of the most common misconceptions is – that there is a problem because we got a “Request timed out”.
This response is not a sign of a problem because, the host whom we “ping” (Exchange On-Premise in our scenario), was not supposed to reply to the ping request. This is a foreseeable result because most of the time the organization Firewall blocks the ICMP protocol (that used for the Ping reply).
To recap: the fact that we got a response the Public IP is the required results, meaning the Exchange on-Premises server have a public name + Public IP address.
Note – besides of verifying the Exchange Hybrid server public name and Public IP; we will need to check additional parameters such as the ability to access the Exchange Hybrid server using a particular protocol and so on. In the next sections, we will review these other requirements
3. Exchange On-Premise Hybrid Server | Port Number And Protocols
Hybrid configuration based on sharing data and services between Exchange Online and Exchange on-Premises server. The communication channel implemented by using two communications protocols:
The underlying assumption is that – the Exchange on-Premises server protected by a Firewall. To be able to implement the communication channel, between the Exchange on-Premises server and the Exchange Online successfully, we will need to verify that the Firewall includes the following inbound and outbound rules:
Reference from Microsoft article
The following screenshot is taken from a Microsoft article and includes a table the describe the port number and the services that need to enabled for Hybrid configuration
4. Exchange On-Premise Hybrid Server| Public IP Address And Static NAT
An important factor that we need to verify is that the Exchange on-Premises server is using the public IP address that was assigned to him when he responds to a communication request of external hosts or when he initializes a connection to an external host.
The technical term for this scenario could be as a “two-way static NAT”.
For example: when using the Exchange 2010 Hybrid configuration wizard, we need to provide the public IP of the Exchange on-Premises server which is “allowed” to send an E-mail to the Exchange Online server.
When the Exchange on-Premises server communicates the Exchange Online, it is important that the Exchange on-Premises server use the public IP that configured in the Exchange hybrid wizard.
Other examples could be when the Exchange Online starts a communication process to the public IP of the Exchange on-Premises server. In this case, the Exchange Online server is “waiting” for a response from the IP address that used for starting the communication channel.
An example for the static NAT rule could be:
n the following diagram, we can see an example of static NAT rule. When external hosts such as Exchange Online try to communicate with the Public IP of the Exchange On-Premise server, the “response” from the Exchange on-Premises server implemented by using the same public IP address that we use for “publishing” the Exchange on-Premises server.
5. ISA-TMG Server And A Firewall Server
When using ISA\TMG server to publish an Exchange On-Premise server, the configurations are a little bit different compares to a “standard Firewall” because, ISA\TMG is a Proxy server and additionally, Firewall server.
When using a “Standard Firewall,” we redirect the communication to the internal Exchange On-Premise server by using a simple “access rule”.
When using ISA\TMG Firewall, redirection to the internal Exchange On-Premise server is implemented by using a: Web publishing rule.
The ISA\TMG web publishing rule relates to a particular or pre-configured Exchange On-Premise “path” such as -OWA, EWS an additional component that used in the ISA\TMG environment is the Authentication settings.
Because ISA\TMG is a proxy server, many times the configuration of the authentication process implemented in the following way: external host authenticates (provide his credential) to the ISA\TMG, the ISA\TMG server approves or disapproves the credentials and if the complete successfully ISA\TMG will “forward in” the communication request of the external hosts.
In the hybrid environment, this configuration will cause problem and errors. In simple words: when we publish Exchange On-Premise server using ISA\TMG server, we need to cancel or disable the option in which ISA\TMG server is authentication external host’s communication request.
6. Firewall Inbound And Outbound Access Policy | Office 365 And Exchange Online Public IP Range
In many organizations, because of a regulation or other security requirements, there is an implementation of outbound and inbound policy that restricts access only to a dedicated or a predefined IP range.
For example: when we say:” Exchange on-Premises server is creating a communication channel with Exchange Online,” what does is mean from the “IP range” point of view?
Does Exchange Online infrastructure represented by a particular or a predefined public IP range?
The answer to this question is: “Yes.”
All the Office 365 environment such as – the Windows Azure Active Directory, Exchange Online, SharePoint Online and so on, based on a “publish” or well-known public IP range.
The implementation of Outbound and inbound firewall rules that restrict the access only to a specific or a predefined IP range consider as “good practice” from the security point of view. But, at the same time, can complicate and interrupt the process of the “first-time configuration” that we use for building the “Hybrid communication channel” between the Exchange On-Premise and the Exchange Online server.
Apr 30 2018 06:03 AM
What a great article!
I have an Exchange Server 2010 on premise server setup in Hybrid Mode.
This server also has OWA configured and I remember needing to do this as I wanted to migrate my Public Folders over to Exchange Online.
This I have now done so all mailboxes and Public Folders are over in Office 365.
Do I need to maintain the presence of the OWA locally still?
Apr 30 2018 07:17 AM
Thanks for liking my article and for getting an expert opinion for your Exchange Hybrid from me, as you are using exchange 2010 which is not supporting silent OWA redirection (2013 and 2016) supported and if no mailbox is on-premise you do not need to change the actual OWA URL name but redirect the URL from old to Office 365 deleting the old DNS A record and adding a new CNAME entry e.g if you on premise OWA name is mail.contoso.com then you can add a new CNAME record as Host Name "mail.contoso.com" and point to address is "outlook.office.com" so every time when your users try to access the old OWA they will be redirected to new URL.
Hope this will help you
Apr 30 2018 07:26 AM
Thanks for the advice.
So I understand this, can I remove the OWA role from my on premise Exchange 2010 server?
Just wanted to make sure that there was no impact on the Hybrid functionality.
Users are going straight to office.com for their email needs, web wise.
Apr 30 2018 07:36 AM
you can remove the CAS role and also need to change the Autodiscover entry to Office 365 because your exchange front-end (CAS) on premise look for user's mailbox using autodiscover service using CAS Role and if there is no mailbox change the autodiscover DNS entry and remove the CAS role so your client will use Office 365 CAS for mailbox discovery process.
Hope you understand the whole process
May 21 2018 04:13 AM
May 21 2018 04:13 AM
May 25 2018 03:05 AM
May 25 2018 03:05 AM
if you want Hybrid then your Anywhere, EWS and Autodiscover URL's should be available publicly and published in your exchange servers because autodiscover service will do the autodicsovery of mailboxes either user's mailbox in the cloud or on-premises and EWS will give you the advantage of organization relationships with exchange online organization for unified GAL, calendar and free/busy information sharing and if your exchange do not have EWS Public names published on your exchaneg then your Hybrid Wizard will be failed saying :Organization relationships failed......." because it need to make a trust relationship with your exchange and MFG (Microsoft ForeFront Gateway) for free/busy and calendar sharing.
if your OWA not published it will not gives your users access to Exchange online URL access as a scilent redirection but each users need to open Exchange online URL i.s. https://mail.office365.com and for every user migrated to cloud you need to tell that now your mailbox is in the cloud and you need to use https://mail.office365.com as OWA address and this will not be seamless transaction for your users.
i hope this answer your queries and do let me know if you need further help from my end.
May 25 2018 03:15 AM
if all mailboxes and Public Folders moved to cloud the you can simply redirect OWA URL's to Exchange online OWA creating CNAME record on your public DNS so your users can use seamless access experience with the old URL.
for example if your OWA address is mail.microsoft.com then your CANME on the public will be
Record Type: CNAME
host Name : mail
Point to Address: mail.office365.com
also please note that if your local Domain name is different then the Public Domain name then you need to have the same CNAME record under your local DNS server
hope this answer your query.
Jun 14 2018 12:27 AM
HI,Thanks a lot for your reply.But one question I do have suppose my internal owa url is mail.domain.com then do i need to keep the same url which would be externally published or i can keep different URL as well.But i know for that i need to communicate with my users.
now when i will run Hybrid Wizard it will ask me FQDN name for connector.So can I put the same name which is my externally published owa URL or it should be dedicated one.
If I do have F5 in the environment do i need to separately put the third party certificate in the excange server or Load balancer will suffice the purpose(ssl offloading).So while running Hybrid wizard what certificate i will choose if i will not put in my ex server,
Jun 14 2018 12:39 AM
Jun 18 2018 04:01 AM
Sorry for the late reply because we have public holidays here in Qatar and regarding your question on the external name please have a look at part#2 where you can see how to find your exchange public names FQDN:
you can use external name as different with the one you are using for internal.
Jun 18 2018 04:04 AM
Jun 18 2018 04:04 AM
yes, otherwise your hybrid
Can you tell me is that external url for owa/oa/ews have to be there in exchange on -premise.
What happen if OWA is not accessible by users externally currently.And they want to move to office 365.We are running exchange 2013 .Autodiscover is currently pointing to on premise internal cas url.So will it must to create EWS/OA/OWA external url in exchange onpremise before running the HYbrid Wizard
configuration wizard will failed.
Jun 18 2018 06:40 AM
Jul 24 2019 02:25 AM
Hi there , its been really great help as per the above. Can you also guide me that if i need to move almost 600 GB mailbox data from my exchange 2010 environment to exchange online (office 365) what are the require environment & network bandwidth is needed.Is it must to have azure express route ? is there any possibilities if we sync the mailbox data all day long !
Jul 24 2019 02:26 AM
Hi there ,its been really great help as per the above.Can you also guide me that if i need to move almost 600 GB mailbox data from my exchange 2010 environment to exchange online (office 365) what are the require environment & network bandwidth is needed.Is it must to have azure express route ? is there any possibilities if we sync the mailbox data all day long !@Ahmed Bilal
Jul 24 2019 01:07 PM
Hello avishek, in my most recent project with Aramco Rowan, we migrate 8TB of data using Exchange 2013 as Hybrid server without express route but in our case we place DC, Hybrid Exchange, ADFS, MFA on Microsoft Azure UK region and our Tenant was also registered for UK region.