Microsoft has a feature in their Azure stack called Conditional Access. This feature allows Azure customers to apply policies to either the log-in process to Office 365 or specific apps and tiles within Office 365/Azure. Using this feature, Azure customers can restrict access to applications, such as Outlook, SharePoint, and others, based on several different factors.
Recently, Microsoft added a function to Conditional Access called a 'custom control'. These custom called custom controls. Custom controls allow third-party integration into Conditional Access. This process involved involves having a registered application by the third - party to be white-listed globally by Microsoft and then providing OpenID Connect (OIDC) endpoints for use by the Azure customer to call out to the third - party's authorization process.
This guide is intended for those end-users and customers who require information on installing and configuring administrators who need to install and configure Microsoft Conditional Access for use with SecureAuth IdP.
Before configuring this, you must have completed You must ensure that you have the following items:
- Have administrative access of Microsoft Azure
- Have installed Install a SecureAuth IdP appliance version 9.1 + or 9.2 and configured one or more realms for that appliance Have Internet Information Services (IIS) for Windows Server installed and configured
- If you are interested in this integration, contact firstname.lastname@example.org , open a support ticket, and mention "Tailoring - Conditional Access"
Configuring SecureAuth IdP
To configure SecureAuth IdP for use with Microsoft Conditional Access, perform the following procedure:
1. Log into your SecureAuth IdP Web Admin Console.
- refer to the SecureAuth IdP Realm Guide
- Configure the following tabs in the Secure Auth IdP Web Admin
- console before configuring any other tabs:
must be defined
- Overview: Define the description of the realm and SMTP connections
the way in which
- An enterprise directory must be integrated with SecureAuth IdP.
must be defined
- Define how users access the target
- Multi-Factor Methods: Define the Multi-Factor Authentication methods that are used to access the target
) must be defined
- , if any
The new realm is significantly customized starting with Step 6.
- Gain administrative access of Microsoft Azure.
- Install and configure Internet Information Services (IIS) for Windows Server.
- Set up Modern Authentication in your server environment. See the Hybrid Modern Authentication overview and prerequisites for using it with on-premises Skype for Business and Exchange servers article on the Microsoft website.
- Contact email@example.com, open a support ticket, and mention "Tailoring - Conditional Access" if you will use this integration. Request the following items so you have them on hand during the configuration:
- ASPX and code-behind pages (in "Configure SecureAuth IdP," step 4)
- Import Rules (in "Configure SecureAuth IdP," step 5d)
- JSON file (in "Configure Microsoft Custom Control," step 7)
SecureAuth IdP configuration steps
Create a SecureAuth IdP realm and configure it for use with Microsoft Conditional Access.
1. Log into your SecureAuth IdP Admin console.
2. Copy the ASPX and code-behind pages then copy them under the root of the newly-defined realm, which is located in D:\SecureAuth\SecureAuthRealm_number, for example, D:\SecureAuth\SecureAuth5
A custom pre-authentication page is used to retrieve the user ID from Microsoft for this request. Microsoft sends a HTTP POST with the OIDC parameters and an additional parameter called id_token_hint. This parameter is includes a JSON web token (JWT) and a number of claims, including the unique id ID for the user and their user principal name (UPN. We need to grab ). SecureAuth IdP must obtain that information and validate the JWT.
53. Using IIS Manager, create an inbound rule for Conditional Access in this new realm by completing the following this proceduresteps:
- Start the IIS Manager (Start | Run then type inetmgr and hit Enter): Open Run, type inetmgr, and click Enter.
- In IIS, select the Default Web Site.
- Under Features View, click click URL Rewrite.
- At On the right hand side, under the Actions pane, click on click Import Rules and import the rules you received from SecureAuth Support. (Contact SecureAuth Support per the Prerequisites steps, if you did not already request this information.)
- Set an inbound rewrite rule under the realm folder (for example, SecureAuth3) as shown in 1.
, shown in the following image, captures requests and
places them on the custom page
to decode the JWT that Microsoft sends over VIA POST
information about the URL rewrite rule,
6. Return to the newly-defined realm in IdP Web Admin Console and click the Data tab.
see the Creating Rewrite Rules for the URL Rewrite Module article, on the Microsoft website.
4. Select the Data tab.
5. Create a connection based on the data store type (, such as Active Directory or SQL Server) in this manner:
a. Scroll down to the 'Set Profile Fields' section and make the following designations:
a. In the Profile Fields section, set the following auxiliary values:
Aux ID 1 – userPrincipalName
Anchor aux1 aux1
Aux ID 2 – otherLoginWorkstations
Anchor aux2 aux2
- Aux ID 5 – otherIpPhone and and make it writable. (This field is set from custom pre- authentication page – MSConditionalAccess.aspx.vb)
- Go to the Web.Config file for this specific realm and add this line to modify the AuxID 5 definition:
b. Scroll down to the 'In the Global Aux Fields' section and designate section, designate Global Aux ID 1 as as Validated.
FIGURE 4. Global Aux Fields Section
6. Select the Workflow tab.
a. In the 'the Login Screen Options' section section, assign set the following values to the designated fields.:
- Set Default Workflow – to Username | Second Factor.
- Set Public/Private Mode – to Public Mode Only.
FIGURE 5. Login Screen Options
b. In the 'the Customer Identity Consumer' section section, perform set the following taskvalues:
- Set Receive Token – to Token.
- Leave other fields as set to the default.
FIGURE 6. Custom Identity Consumer
7. Select the Multi-Factor Configuration page and supply the following values Methods tab.
a. Scroll to the 'In the Phone Settings' section and supply the following values to the designated fields:
section, configure the Multi-Factor Authentication methods that you want enabled. The following example shows how to set the email and text (SMS) methods.
- Set Phone Field 1 to One-Time Passcode via Phone Call and SMS.
- Set Phone Field 2 – select to One-Time Passcode via Phone Call and SMS.
FIGURE 7. Phone Settings Section
b. Scroll down to the 'Email Settings' section and supply the following value to the designated field:In the Email Settings section, set Email Field 1
to One-Time Passcode via HTML Email.
FIGURE 8. Email Settings Section
10. Click the Post Authentication tab then supply the following values to the designated fields:
Post Authentication tab
8. Select the Post Authentication tab.
a. In the Post Authentication section, set the Authenticated User Redirect dropdown to OpenID Connect/OAuth2.
b. In the 'the User ID Mapping' section section, supply set the following values:
- Set User ID Mapping – select to Authenticated User ID. The user can choose to map Map other parameters, if needed.
Set Name ID Format – select to urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.
- Set Encode to Base64 – select to False.
c. Scroll down to the 'c. In the OpenID Connect/OAuth 2.0 – Settings' section and provide section, set the following values:
- Enable – Set Enabled to True.
- Set Issuer – Should be the FQDN to the fully qualified domain name (FQDN)/Hostname of the IdP appliance, for example, idp.company.com. This must be publicly facing and have a valid SSL certificate.
- Set Signing Algorithm – Can be either to either RSA SHA256 (RS256) or or HMAC SHA256 (HS256).
- RSA SHA256 (RS256) is an asymmetric algorithm, which means it uses a public/private key pair. SecureAuth uses the private key for signing and provides you with the public key to use to validate the signature.
- HMAC SHA256 (HS256) is a symmetric algorithm, which means one secret key is shared between SecureAuth and the end-user. The same key is used to create the signature and to validate it. This key must be kept secret at all times.
- Set Signing Cert to any certificate that is a private key readable by SecureAuth IdP. Do not use wild cards in a certificate.
- Set Auto Accept User Consent – True. This provides a cleaner to True to provide a clean user experience.
- Set Enable User Consent Storage – True. This provides a cleaner user experience and enables to True to provide a clean user experience and to enable check session endpoints.
- Set Consent Storage Attribute – The to the AUX ID 2 value that was mapped to a string attribute in step 7a (for example, otherLoginWorkstations).
Leave the following fields set to the default: '
- Authorization Code Lifetime
- Access Token Lifetime
- Refresh Token Lifetime
Refer to for an example.
d. Scroll down to the 'd. In the OpenID Connect/OAuth 2.0 – Scopes' section and provide the following value:
section, set the Discoverable check box for the openid scope.
e. Scroll down to the '
- Set Name to ConditionalAccess or another appropriate name.
- Set Client ID – supply to the appropriate client ID for this client.
- Set the Enabled/Disabled – check this check box.
FIGURE 12. OIDC - Clients Settings
f. Scroll down to the 'In the OpenID Connect/OAuth 2.0 - Client Details' section and provide section, set the following values in the designated fields:
- Set Enabled – to True.
- Name – Set to an appropriate name such as ConditionalAccess
- Set Name to ConditionalAccess or another appropriate name.
- Set JSON Web Encryption – to Disabled.
- Set JSON Web Key URI – Blank
- to Blank.
g. Scroll down to the 'Allowed Flows' section and provide the following values in the designated fields:
- Authorization Code – True
- Implicit – True
- Hybrid – False
- Client Credentials – False
- Resource Owner – False
- Refresh Token – True
- Introspection – True
- Revocation – True
FIGURE 14. Allowed Flows Section
h. Scroll down to the 'g. In the Allowed Flows section, set the following values:
- Set Authorization Code to True.
- Set Implicit to True.
- Set Hybrid to False.
- Set Client Credentials to False.
- Set Resource Owner to False.
- Set Refresh Token to True.
- Set Introspection to True.
- Set Revocation to True.
h. In the OpenID Connect/OAuth 2.0 - Client Redirect URIs' section and provide the following value: section, click the Add Redirect URI button and set the Client Redirect URI
i. Scroll down to the 'i. In the OpenID Connect/OAuth 2.0 – Claims' section and supply this value section, set the following values:
- Set Sub
- to the AUX ID field assigned
- the userPrincipalName
- value (as shown
- in step 7a)
- Set the Discoverable check box.
j. Scroll down to the 'In the OpenID Connect/OAuth 2.0 – Custom Claims' section and assign section, click the Add Custom Claim button and set the following values:
- Set Claim – to SecureAuthMFA.
- Set Profile Property – to Global Aux ID 1.
- Discoverable – Checked
- Set the Discoverable check box.
FIGURE 17. OIDC - Custom Claims Section
System Info tab
9. Select the System Info tab.
- In the Links section at the bottom of the screen, click Click to edit Web Config file to edit the web.config file.
- Add the following key under the <appSettings> section:
<add key="MSConditionalAccess-ProfileField" value="AuxID5" />
For information about editing the web.config file, see the System Info Tab Configuration document.
10. Save all changes made to this configuration and exit.
Configure Microsoft Custom Control
To create Create and configure a new custom control for Microsoft Conditional Access, perform the following steps.
- Log into in to Microsoft Azure.
- Click Click Azure Active Directory from in the left vertical menupane.
- Click Security | Conditional Access.
- Click Manage | Custom Control.
- Click New custom control.In the Security section, click Conditional access.
- In the Manage section, click Custom controls.
- Click New custom control.
- Enter the JSON for customized controls as shown in in the fill-in field.
7. Supply Enter the following values for JSON fields as shown in
- App ID – enter the data applications that MSFT has referenced.
- ClientID – retrieve from the designated realm under the 'OpenID Connect/OAuth 2.0 – Clients' section (refer to ).
Creating a New Policy
JSON provided by SecureAuth Support, then click Save
Create a Policy
Create a Microsoft Conditional Access policy.
- Log into Microsoft Azure.
- Click on Click Azure Active Directory from in left vertical menupane.
- Click Click Security | > Conditional Access | - Policies | > New Policy.
FIGURE 20. New Policy Button
4. Specify the users, apps, and controls as requiredthat you want to assign the policy to.
FIGURE 21. Policy Assignments
5. When you have finished, click Save.
5. Save your changes.
Test Microsoft Conditional Access with SecureAuth IdP
Test that Microsoft Conditional Access works with SecureAuth IdP. In this scenario, you will test with Microsoft Teams, but you could also test with Outlook or Skype for Business.
- Log in to Microsoft Teams: https://teams.microsoft.com
- Enter your email address in the following screen:
- Enter your password in the following screen:
- Select the kind of two-factor authentication method to use to log into Microsoft Teams. The following example shows the text message (SMS) method.
- In the following screen, enter the one-time passcode that was sent to you:
- The following Microsoft Teams screen is displayed if the configuration between Microsoft Conditional Access and SecureAuth IdP is successful.
If you do not see this screen or if you receive an error message, contact SecureAuth Support.