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 custom controls. Custom controls allow third-party integration into Conditional Access. This process involves having a registered application by the third party to be allowed 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 administrators who need to install and configure Microsoft Conditional Access for use with SecureAuth IdP.


You must ensure that you have the following items:

SecureAuth IdP configuration steps

Create a SecureAuth IdP realm and configure it for use with Microsoft Conditional Access.

Configure Internet Information Server (IIS) for Windows Server 

1. Log into your SecureAuth IdP Admin console.

2. Copy the ASPX and code-behind pages under the root of the newly-defined realm, which is located in D:\SecureAuth\SecureAuthRealm_number, for example, D:\SecureAuth\SecureAuth5

(Contact SecureAuth Support per the Prerequisites steps, if you did not already request the ASPX and code-behind pages.)

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 includes a JSON web token (JWT) and a number of claims, including the unique ID for the user and their user principal name (UPN). SecureAuth IdP must obtain that information and validate the JWT.

3. Using the IIS Manager, create an inbound rule for Conditional Access in this new realm by completing the following steps:

    1. Start the IIS Manager: Open Run, type inetmgr, and click Enter.
    2. In IIS, select the Default Web Site.
    3. Under Features View, click URL Rewrite.
    4. Set an inbound rewrite rule under the realm folder (for example, SecureAuth3).

The URL rewrite rule, shown in the following image, captures requests and places them on the custom page to decode the JWT that Microsoft sends over VIA POST.

For more information about the URL rewrite rule, see the Creating Rewrite Rules for the URL Rewrite Module article, on the Microsoft website .

4. Using the IIS Manager, change the query string setting for the SecureAuth realm number (for example, SecureAuth3). 

    1. In the IIS Manager, focus on the appropriate realm.
    2. Right-click Request Filtering and select Open Feature .
    3. Select the Query Strings tab.
    4. On the right side of the page, click Edit Feature Settings.
    5. Set  Maximum URL length (Bytes) to 6144.
    6. Set Maximum query string (Bytes) to 4096.
    7. Click OK to save the changes.

5. Ensure that  is accessible from the SecureAuth server. 

Data tab settings 

1. Select the Data tab.

2. Create a connection based on the data store type, such as Active Directory or SQL Server.

a. In the Profile Fields section, set the following auxiliary values:

      • Aux ID 1 – userPrincipalName 
      • Aux ID 2 – otherLoginWorkstations
      • Aux ID 5 – otherIpPhone and make it writable. (This field is set from custom pre-authentication page – MSConditionalAccess.aspx.vb)

b. In the Global Aux Fields section, designate Global Aux ID 1 as Validated.

Workflow tab settings

Select the Workflow tab.

1. In the Login Screen Options section, set the following values:

      • Set Default Workflow to Username | Second Factor.
      • Set Public/Private Mode to Public Mode Only.

2. In the Customer Identity Consumer section, set the following values:

      • Set Receive Token to Token.
      • Leave other fields set to the default.

Multi-Factor Methods tab settings

Select the Multi-Factor Methods tab.

1. In the Phone Settings 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 to One-Time Passcode via Phone Call and SMS.

2. In the Email Settings section, set Email Field 1 to One-Time Passcode via HTML Email.

Post Authentication tab settings

Select the Post Authentication tab.

1. In the Post Authentication section, set the Authenticated User Redirect dropdown to OpenID Connect/OAuth2.

2. In the User ID Mapping section, set the following values:

      • Set User ID Mapping to Authenticated User ID. Map other parameters, if needed.
      • Set Name ID Format to urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.

      • Set Encode to Base64 to False.

3. In the OpenID Connect/OAuth 2.0 – Settings section, set the following values:

      • Set Enabled to True.
      • Set Issuer to the fully qualified domain name (FQDN)/Hostname of the IdP appliance, for example, This must be publicly facing and have a valid SSL certificate.
      • Set Signing Algorithm to either RSA SHA256 (RS256) 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 to True to provide a clean user experience.
      • Set Enable User Consent Storage to True to provide a clean user experience and to enable check session endpoints.
      • Set Consent Storage Attribute to the AUX ID 2 value that was mapped to a string attribute, for example, otherLoginWorkstations.

Leave the following fields set to the default:

        • Authorization Code Lifetime
        • Access Token Lifetime
        • Refresh Token Lifetime

4. In the OpenID Connect/OAuth 2.0 – Scopes section, set the Discoverable check box for the openid scope.

5. In the OpenID Connect/OAuth 2.0 – Clients section, click the Add Client button and set the following values: 

      • Set Name to ConditionalAccess or another appropriate name.
      • Set Client ID to the appropriate client ID for this client.
      • Set the Enabled/Disabled check box.

6. In the OpenID Connect/OAuth 2.0 - Client Details section, set the following values:

      • Set Enabled to True.
      • Set Name to ConditionalAccess or another appropriate name.
      • Set JSON Web Encryption to Disabled.
      • Set JSON Web Key URI to Blank.

7. 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.

8. In the OpenID Connect/OAuth 2.0 - Client Redirect URIs section, click the Add Redirect URI button and set the Client Redirect URI to

9. In the OpenID Connect/OAuth 2.0 – Claims section, set the following values:

      • Set Sub to AUX ID 5, which was mapped to the otherIpPhone value on the Data tab.
      • Select the Discoverable check box.

10. In the OpenID Connect/OAuth 2.0 – Custom Claims section, click the Add Custom Claim button and set the following values:

      • Set Claim to SecureAuthMFA.
      • Set Profile Property to Global Aux ID 1.
      • Set the Discoverable check box.

System Info tab settings

Select the System Info tab.

1. In the Links section at the bottom of the screen, click Click to edit Web Config file to e dit the web.config file .

2. Add the following key under the  <appSettings>  section:

<add key="MSConditionalAccess-ProfileField" value="AuxID5" />

Note: The following keys are required only if user profile data is using samAccountName as uniqueidentifier. The keys are required to create a separate API realm. (Do not use an OpenID Connect realm as an API realm because you cannot have two different settings for an OpenID Connect realm.) After adding the following keys, see Optional API realm configuration.

<add key="MSConditionalAccess-EnableUPNsamAccountNameConversion" value="True" />
<add key="MSConditionalAccess-UPNsamAccountNameConversionUsingAPI" value="True" />
<add key="MSConditionalAccess-API-SecureAuthRealmUrl" value="https://<domain or localhost>/SecureAuthXX" />
<add key="MSConditionalAccess-API-AppId" value="XXXXXXXXXXXX" />
<add key="MSConditionalAccess-API-AppKey" value="XXXXXXXXXXXXXXXXXXXXX" />
<add key="MSConditionalAccess-API-samAccountNameField" value="AuxID6" />

For information about editing the web.config file, see the System Info Tab Configuration document.

Save all changes made to this configuration and exit.

Optional API realm configuration 

The following steps are required if user profile data is using samAccountName as uniqueidentifier and you set the extra keys in "System Info tab settings," step 2.

  1. In the Data tab, create a connection based on the data store type, such as Active Directory or SQL Server.
  2. In the Search Filter section, set Search Attribute to userPrincipalName, and set searchFilter to (&(userPrincipalName=%v)(objectclass=*)) as shown in the following image.

  3. In the Profile Fields section, set Aux ID 6 to sAMAccountName, as shown in the following image. (This field is set to match the MSConditionalAccess key you set in "System Info tab settings," step 2.
  4. Save your changes.
  5. In the API tab, enable the API for the realm by setting the following:
    1. In the API Key section, set Enable API for this realm.
    2. In the API Permissions section, under Authentication, set Enable Authentication API.
    3. Under Identity Management, set User Management - add / update / retrieve users and their properties.
    4. Save your changes.

Configure Microsoft Custom Control 

Create and configure a new custom control for Microsoft Conditional Access.

  1. Log in to Microsoft Azure.
  2. Click Azure Active Directory in the left pane.
  3. In the Security section, click Conditional access.
  4. In the Manage section, click Custom controls.
  5. Click New custom control
  6. Enter the JSON for customized controls in the fill-in field.

7.  Enter the JSON provided by SecureAuth Support, then click Save . (Contact SecureAuth Support per the Prerequisites steps, if you did not already request this information.)

Configure the JSON file as follows, using the above image as a guide:

    1. Set AppId to the data application referenced by Microsoft.
    2. Set ClientId by retrieving the designated realm located under the Post Authentication tab, in the OpenID Connect/OAuth 2.0 - Clients section.
    3. Set DiscoveryUrl to the OpenID configuration for the designated realm.

For your convenience, copy the following code snippet into the JSON file and change values appropriately:

   "Name": "Name for SecureAuth MFA",
   "AppId": "Microsoft data App ID",
   "ClientId": "SecureAuth ClientID",
   "DiscoveryUrl": " https://SecureAuthURL/secureauthXX/.well-known/openid-configuration ",
           "Id": "SecureAuthIdP",
           "Name": "SecureAuthIdP",
                "Type": "SecureAuthMFA",
                "Value": "Validated",
                "Values": null

Create a Policy

Create a Microsoft Conditional Access policy.

  1. Log into Microsoft Azure.
  2. Click Azure Active Directory in left pane.
  3. Click Security > Conditional Access - Policies > New Policy.

4. Specify the users, apps, and controls that you want to assign the policy to.

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.

  1. Log in to Microsoft Teams:
  2. Enter your email address in the following screen:
  3. Enter your password in the following screen:
  4. Select the kind of two-factor authentication method to use to log into Microsoft Teams. The following example shows the text message (SMS) method.
  5. In the following screen, enter the one-time passcode that was sent to you:
  6. 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.