Wouldn’t it be awesome to the do the following with Outlook Web Access being published in your on-premises environment today?

• Cheap proxy solution to prevent direct internet access to your servers
• Mask the IPs of your on-premises infrastructure
• Enable Azure MFA (Multi-Factor Authentication) for OWA?
• Have a Single-Sign on experience into Outlook Web Application via federation?
• Have the application be selectable from your “My Apps” page (myapps.microsoft.com)
• Have the application be selectable from the “Waffle Menu” of Office 365

If you are looking for any of the above, you are in-luck and we can enable this easily through Azure AD Application Proxy.  If you organization is using Office 365 or Azure AD already and have licensing for Azure AD Premium or Basic, you are good to go.  If you have the Enterprise Mobility Suite, this will grant you to Azure AD Premium licensing which should make you good to go as well.

Configuration

1. Prerequisite: Enable Kerberos Authentication for Outlook Web Access On-Premises
   1. Login to one of your domain controllers and open up Active Directory Users and Computers
      
   2. Find the Computer object within your organization we will run the Azure AD Connector on later in the tutorial and right click Properties on it
      
   3. Select the Delegation tab, select Trust this computer for delegation to specified services only, check Use any authentication protocol, and click on Add…
      
   4. Select Users or Computers…
      
   5. Type in the machine name and click OK
      
   6. Select http and click OK
      
   7. Click OK on the Add Services page
2. Pre-Requisite: Enable Exchange On-Premises to use Integrated Windows Authentication (instructions for Exchange 2010 or 2013 can be found below)
   1. Exchange 2010
      1. Open the Exchange Management Console for your Exchange server
         
      2. Expand Server Configuration, select Client Access, under Outlook Web App, right click on your web app and select Properties
         
      3. Select the Authentication tab and check Use one or more standard authentication methods.  Once checked, check Integrated Windows authentication and click the Apply and OK buttons.
         
      4. Open a command prompt
         
      5. Execute the iisreset command
         
   2. Exchange 2013
      1. Open the Exchange Administrative Center
         
      2. Login to the admin center, click on Servers and select the Virtual Directories tab
         
      3. Select server and then double click on the OWA Virtual Directory and select the applications tab
         
      4. On the authentication tab, select Use one or more standard authentication methods, select Integrated Windows authentication, and click save
         
      5. Open a command prompt
         
      6. Execute the iisrest command
         
3. Login to the Azure Portal
   1. https://portal.azure.com
4. Select All services -> Azure Active Directory on the left side
   
5. Select Application proxy in the sub blade and select + Configure app
   
   
6. Enter in the following information for the application:
   1. Name: Outlook Web Access
   2. Internal URL: https://owa.yourdomain.com/owa/ (this is the internal URL to owa)
   3. Pre-Authentication: Azure Active Directory
   4. Connector Group: Default
   5. Click + Add
      
      
   6. Select OK if not prompted about having a connector
      
7. Once your application is created, you should be redirected to Azure Active Directory -> Enterprise Applications -> Outlook Web Access.  On this blade, select Single sign-on and then select the Windows Integrated Authentication button
   
   
8. Use the following configuration
   1. Internal Application SPN: http/owa.yourdomain.com
      1. This is the Service Principal Name to the Exchange Server.  The value for this was provided earlier in this tutorial.
   2. Delegated Login Identity: User Principal Name
   3. Click Save
      
   4. Note: If you cannot do Kerberos based authentication (Integrated Windows Authentication) in your environment, you can Discard the changes continue to use Azure AD Application proxy, however the end user will be prompted for credentials just as if they browsed directly to OWA.
9. Go back to All Services -> Azure Active Directory -> Application Proxy and click the Download connector service button
   
   
   1. Click the Accept terms & Download button
      
   2. Note: Although the download has a generic name, the download is customized specifically for your application (Outlook Web Access in this case).  If you create other applications within your Azure AD tenant, make sure you always use the Download button inside of each application so it generates the correct installer.
10. Copy the AADApplicationProxyConnectorInstaller.exe connector to any server in your environment that can access your OWA instance internally and run the installer
    
11. Check I agree to the license terms and conditions and click Install
    
12. Type in your Global Administrator credentials to register the agent to your Azure AD tenant and click Sign in
    
13. Click Close if it shows Setup Success
    Optional: You can run the Connector Troubleshooter if you would like.  It will install a quick application that will show you the results of the test in your web browser once it has completed.
    
14. Go back to the Azure Portal and navigate to Azure Active Directory -> Enterprise Applications -> Outlook Web Access.  Select Users and groups and click the +Add user button to assign the group or users that should use the application.
    
    1. Note: This group could be synchronized from on-premises to Azure AD or created in the cloud
    2. Note: Assigning a user or group to this application will automatically make the application show up in the My Apps portal
    3. Note: Users or Groups must be defined to use the application or they will receive an error upon logging in

Test

1. Login to https://myapps.microsoft.com as one of the assigned users to the Outlook Web Access application
2. Select the Outlook Web Access application

If all went well, you should be logged into Outlook Web Access on-premises and see your corresponding mailbox.  At this point, I would proceed with adding a vanity domain name that matches your organization as well as corresponding SSL certificate for the domain name instead of leveraging the default msapprpoxy.net domain name.  Additionally, you can always find a nice little icon for the application to make it look like OWA as well ?