Also tick “Only redirect requests to content in this directory (not subdirectories)” then click Apply.ģ) Double click on “Default Web Site” to return to the home menu then double click on SSL settings:Ĥ) Untick “Require SSL” then click on Apply:ĥ) Click on the Autodiscover virtual directory then double click on HTTP Redirect:Ħ) Untick “Redirect requests to this destination” then click Apply:ħ) Repeat steps 5 and 6 for the other virtual directories under the “Default Web Site” which are listed below:Ĩ) Reset IIS so that the settings take effect:ĩ) Confirm the settings are correct and that you can now open up OWA by browsing to : Then double click on “HTTP Redirect”Ģ) Tick “Redirect requests to this destination” and type in the full OWA URL e.g. To configure this redirect and also require SSL, go through the steps below:ġ) Click on “Default Web Site” in IIS on your Exchange 2013 CAS or multirole server or on your Exchange 2016 server. How to configure HTTP to HTTPS redirect for OWA

Keep reading for the recommended way to do this. The problem is that the Default Web Site is configured to require SSL:īefore you go ahead and just untick “Require SSL”, that’s a good start but it’s only part of the solution. So, as you can see, our Exchange server is listening for connections on port 80 as it is a listed port on the “Default Web Site”. The bindings for the Exchange Back End site include port 81 and 444:

The bindings for the “Default Web Site” include port 80 and 443: On each of these web sites, there are bindings which specify which server IP, port number and host header the web site is configured to respond to. The virtual directory is configured on an IIS website of which there are two when Exchange is installed: “Default Web Site” and “Exchange Back End”. OWA is set up as a virtual directory in IIS on Exchange 2013 CAS and MBX servers and on Exchange 2016 servers.

“The website declined to show this webpage (HTTP 403 Forbidden)” When we try to browse to OWA using the HTTP address, in our case, we get the error below: This simplifies the OWA URL and is easier for end users to remember as they don’t have to type OWA over HTTP In this post, I’ll demonstrate how to redirect HTTP OWA requests to HTTPS for both Exchange 20.

Exchange 2013 owa