PowerShellRay

Configuring Azure Multifactor Authentication with Exchange 2013

Posted on: October 18, 2015

Intro about MFA how it works

clip_image002

clip_image004

Configuring Azure Multifactor Authentication with Exchange 2013 SP1

We will see how to configure Azure Cloud MFA with Exchange 2013 SP1 on premise, this will be a long blog with multiple steps done at multiple levels, so I suggest to you to pay a very close attention to the details because it will be tricky to troubleshoot the config later.

Here are the high level steps:

  • Configure Azure AD
  • Configure Directory Sync.
  • Configure multifactor Authentication Providers.
  • Install/Configure MFA Agent on the Exchange server.
  • Configure MFA Agent to use basic and form based settings.
  • Sync Users into MFA agent.
  • Configure users from the desired login type.
  • Enroll users and test the config.

Setting up Azure AD/MFA:

Setting up Azure AD/MFA is done by visiting https://manage.windowsazure.com , here you have 2 options (I will list them because I had them both and it took me a while to figure it out):

  • If you have never tried azure, you can sign up for a new account and start the configuration.
  • If you have Office 365 enterprise subscription, then you will get Azure AD configured, so you can sign in into Azure using the same account in Office 365 and you will find Azure AD configured for you (I had this option so I had to remove SSO from the previous account and setting it up again).

Once you login to the portal, you can setup Azure AD by clicking add:

clip_image006

Since I had Office 365 subscription, It was already configured, so if you click on the directory, you can find list of domains configured in this directory:

clip_image008

If you will add a new domain, click on add and add the desired domain, you will need to verify the domain by adding TXT or MX record to prove you domain ownership, once done you will find the domain verified and you can configure it, the following screenshots illustrates the verification process:

Once done, go to Directory Integration  and choose to activate directory integration:

clip_image009

One enabled, download the DirSync tool on a computer joined to the domain:

clip_image010

clip_image011

clip_image012

clip_image013

clip_image014

clip_image015

Once installed, you will run through the configuration wizard which will ask you about the azure account and the domain admin account to configure the AD Sync:

clip_image016

clip_image017

clip_image018

clip_image019

clip_image020

clip_image021

clip_image022

clip_image023

Once done, you can check the users tab in Azure AD to make sure that users are sync’d to Azure successfully:

clip_image025

If you select a user, you can choose to Manage Multifactor Authentication

clip_image027

you will be prompt to add a multifactor authentication provider, the provider essentially controls the licensing terms for each directory because you have per user or per authentication payment, once selected you can click on manage to manage it:

clip_image029

clip_image031

Once you click manage, you will be taken to the phone factor website to download the MFA agent:

clip_image033

clip_image034

click on downloads to download the MFA agent, you will install this agent on:

  • A server that will act as MFA agent and provides RADIUS or windows authentication from other clients or
  • Install the agent on the Exchange server that will do the authentication (frontend servers or CAS servers).

Since we will use Exchange, you will need to install this agent on the Exchange server, once install you will need to activate the server using the email and password you acquired from the portal:

clip_image036

Once the agent installed, it is time to configure the MFA Agent.

clip_image038

clip_image039

clip_image041

clip_image043

Put name of group

Click No

clip_image044

clip_image046

clip_image048

Once the agent installed, it is time to configure the MFA Agent.

Configuring the MFA Agent:

The first step is to make sure tha you have correct name space and SSL certificate in place, typically you will need users to access the portal using specific FQDN, since this FQDN will point to the Exchange server so you will need to publish the following:

  • Extra directories for MFA portal, SDK and mobile app.
  • or Add a new DNS record and DNS name to the SSL certificate and publish it.

In my case, I chose to use a single name for Exchange and MFA apps, I chose https://mfa.azureinaction.com, MFA is just a name so it could be anything.

SSL certificate plays a very important role, this is because the portal and mobile app speaks to SDK over SSL (you will see that later) so you will need to make sure that correct certificate in place as well as DNS records because the DNS record must be resolvable internally.

Once the certificate/DNS issue is sorted, you can proceed with the install, first you will install the user portal, users will use this portal to enroll as well as configuring their MFA settings.

From the agent console, choose to install user portal:

clip_image049

It is very important to choose the virtual directory carefully, I highly recommend changing the default names because they are very long, in my case I chose using MFAPORTAL as a virtual directory.

clip_image050

clip_image051

clip_image052

clip_image053

once installed, go the user portal URL and enter the URL (carefully as there is no auto detection or validation method)

clip_image055

Once done, Proceed with SDK installation, again, I highly recommend changing the name, I chose MFASDK

clip_image056

clip_image057

Once installed, you are ready to proceed with the third step, installing the mobile app portal, to do this browse to the MFA agent installation directory, and click on the mobile app installation, also choose a short name, I chose MFAMobile

clip_image058

clip_image059

Once Installed, you will have to do some manual configuration in the web.config files for the portal and the mobile app.

You will have to specify SDK authentication account and SDK service URL, this configuration is a MUST and not optional.

To do so, first make sure to create a service account, the best way to do it is to fire you active directory users and computers management console, find PFUP_MFAEXCHANGE account and clone it.

Once cloned, open c:intepubwwwroot<MFAportal Directory> and <MFA Mobile App Directory> and edit their web.config files as following:

For MFA portal:

clip_image061

clip_image063

For MFA mobile App:

clip_image064

clip_image066

Once done, you will need to configure the MFA agent to do authentication for IIS.

Configure MFA to do authentication from IIS:
To configure MFA agent to kick for OWA, you will need to configure OWA to do basic authentication, I searched on how to do FBA with MFA, but I didn’t find any clues (if you have let me know).

Once you configured OWA/ECP virtual directories to do basic authentication, go to the MFA agent , from there go to IIS Authentication , HTTP tab, and add the OWA URL:clip_image068

Go to Native Module tab, and select the virtual directories where you want MFA agent to do MFA authentication (make sure to configure it on the front end virtual directories only):

clip_image069

Go to the MFA agent , from there go to IIS Authentication , Form-Based tab, and add the OWA URL:clip_image071

clip_image073

To get the variables and login URL is the login website of OWA, the variables is username and password as shown below when you click F12 on internet explorer

clip_image075

Why we configured HTTP and Form-Based

We used HTTP configuration as the IIS on Exchange Front End/CAS servers is basic authentication and we need to configure the Form-Based authentication because the login page is Form-Based because Exchange behavior after taking the authentication from the Form-Based site and changed to basic authentication on the server to match the IIS so form based configuration is needed to detect the username that is logging

You can also configure a user to do phone app auth:

Once all set, finally, you can enroll users.

Users can enroll by visiting the user portal URL and signing with their username/password, once signed they will be taken to the enrolment process.

for phone call MFA, they will receive a call asking for their initial PIN created during their configuration in MFA, once entered correctly, they will be prompted to enter a new one, once validated the call will end.

In subsequent logins, they will receive a call asking them to enter their PIN, once validated successfully, the login will be successful and they will be taken into their mailbox.

In mobile app, which will see here, they will need to install a mobile app on their phones, once they login they can scan the QR code or enter the URL/Code in the app:

clip_image077

clip_image079

clip_image081

Once validated in the app, you will see a screen similar to this:

clip_image083

Next time when you attempt to login to OWA, the application will ask you to validate the login:

clip_image085

Once authentication is successful, you will see:

clip_image087

and you will be taken to OWA.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: