Obtain
the Microsoft Entra ID customer Tenant ID.You can configure Microsoft Azure AD Conditional Access to use Identity as a Service for multi-factor authentication. To do this, you must add a Microsoft Azure AD Conditional Access application to Identity as a Service. This integration guide describes how to integrate Microsoft Azure AD Conditional Access with Identity as a Service. o integrate Microsoft Entra ID Active Directory with Identity as a Service, see Integrate Microsoft Entra ID active directory with Identity as a Service.
Notes: You can configure one
or more Microsoft Azure AD Conditional Access OIDC applications for your
Microsoft Entra ID custom tenant that can be used across all application
within that tenant. For example, you can create multiple Identity as a
Service Microsoft Azure AD Conditional Access OIDC applications and set
each application to require a different authenticator.
Microsoft Azure AD Conditional Access is being replaced with Microsoft
Entra ID. See Integrate
Microsoft Entra ID External Authentication
To integrate Microsoft Azure AD Conditional Access OIDC with Identity as a Service, complete the following steps:
a. Synchronize your Microsoft Azure AD Conditional Access users with Identity as a Service. See Synchronize Microsoft Entra ID External users with Identity as a Service and Sync an on-premises AD with Microsoft Entra ID External.
b. If you have not done so already, Create a gateway
c. 
Obtain
the Microsoft Entra ID customer Tenant ID.
Obtain the Tenant ID
1. Log in to the Microsoft Entra ID portal.
2. In the Microsoft Entra ID icon.
3. Copy the Tenant ID.
Step
2: Add Microsoft Azure AD Conditional Access OIDC to Identity as a Service1. Log in to an Identity as a Service account with a role that allows you to configure applications.
2. Click
> Security > Applications. The Applications
List page appears.
3. Click Add. The Select an Application template page appears.
4. Under OpenID Connect and OAuth Cloud Integrations, click Microsoft Azure AD Conditional Access. The Add Microsoft Azure AD Conditional Access page appears.
5. Modify the Application Name and Application Description, if required.
6. Optional. Add a custom application logo, as follows:
a. Click 
next
to Application Logo. The Upload
Logo dialog box appears.
b. Click 
to select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
d. If required, resize your image.
e. Click OK.
7. Select the Authentication Flow that appears to users during login.
8. Click Next. The General Settings and Authentication Settings page appears.
9. In the General Settings, do the following:
a. From the User ID Mapping Attribute drop-down list, select User ID to map the Azure AD incoming claim to the attribute used to find the user.
Note: The Login Redirect URI and the Supported Scope are selected by default.
10. Select the OIDC Signing Certificate used to connect to the Microsoft Azure AD.
11. Optional: Select Respond Immediately for Unsuccessful Responses to return to the application immediately after a login failure, rather than allow user to try again with a different userID.
12. Deselect Enable Go Back Button if you do not want users to be able to go back to the Microsoft Azure AD login page to log in.
13. In the Authentication Settings, accept the defaults or, optionally, do the following:
a. Select Require Consent if you want the user to be prompted for consent for each request.
b. Optional. Enter a Consent Message to include a message to users when consent is requested.
c. Set the Max Authentication Age (seconds) to the maximum amount of time that can elapse before a user must re-authenticate to log in. This feature is disabled if the field is left blank.
14. In the Azure AD Conditional Access Custom Control Settings, do the following:
a. Select the Incoming Userid Claim from the drop-down list. The default is User Principal Name. This value is the incoming claim used by Microsoft Entra ID Directory to identify the user.
Note: An Identity as a
Service account that is synchronized with a corporate directory containing
User Principal Name values, auto-populates the User Principal
Name in the user profile information when directory synchronization
occurs. This value is stored in the user’s User Principal Name system
attribute. See Trigger
on-demand synchronization to trigger an immediate directory synchronization.
If the User Principal Name is not populated by directory synchronization,
you must populate the user’s User Principal Name system attribute
manually for every user integrated with Microsoft Azure AD Conditional
Access OIDC.
b. In the Customer Tenant/Directory ID text box, enter the Microsoft Azure AD Conditional Access customer tenant ID, for example, a5a69e76-58be-4303-9339-9fe8f582523d. See Step 1: Obtain the Microsoft Azure AD Conditional Access customer Tenant ID.
15. Copy and save the auto-generated Azure AD Access Custom Control JSON Text. You need this text to configure the Azure AD conditional access custom control at the Microsoft Entra ID Customer Tenant site.
16. Click Submit. A success message appears.
Step 3: Add a resource rule
to protect access to Microsoft Azure AD Conditional Access OIDC
Note: Set Skip Password as the first-factor authentication type and then set the second-factor authenticators that you want to use with Microsoft Azure AD Conditional Access.
Create a resource rule to protect access to OIDC applications
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Resource Rules. The Resource Rules List
page appears.
3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.
4. Enter a Rule Name and Rule Description for the resource rule.
5. In the Groups list, select the group or groups of users restricted by the resource rule.
These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.
6. Click Next. The Authentication Conditions Settings page appears.
7. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate whenever they attempt a new login.
8. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
9. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.
10. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
11. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
12. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
13. Click Date/Time to set the conditions as follows:
a. Select one of the following:
– Allow Date/Time to set when a user can access the application.
– Deny Date/Time to set when the user cannot access the application.
The Date/Time Context Condition Settings appear.
b. Select the Condition Type:
– Specific Date Range Condition—Allows or denies access to the application during a select period of days.
– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.
– Clear Selection—Clears existing Date and Time conditions.
c. Set the Condition Type settings, as follows:
i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.
ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.
iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.
d. Click Save to return to the Authentication Conditions Settings page.
14. Click Geolocation to set the Location Condition Settings, as follows:
a. Select Allow or Deny to create an allowed or denied country list.
b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.
c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.
d. Click Save to save to return to the Authentication Conditions Settings page.
15. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
16. Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:
a. Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.
The risk score is based on the attribute differences
between a user's Machine Authentication information and that recorded
on Identity as a Service before the condition fails. If an attribute does
not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The
Non-Matching Risk Points values of each non-matching
attribute are added together, resulting in a total risk score. This score
is normalized to be out of 100 as follows:
Total Risk Score = (Total Risk Points
of Failing Attributes / Maximum Risk Points of All Enabled Attributes)
* 100
The resource rule condition fails when the number of non-matching risk
points exceeds the Machine Authentication Risk value defined in this step.
A value of 0 means that a single attribute
difference causes the Device Fingerprint
condition to fail. The default value is 3.
The value between 0-50 can be entered.
The default value is defined by the Machine Risk Limit.
See Modify machine authenticator settings.
b. Click Save.
17. Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.
18. Set the Device Certificates risk factor to require the client to perform client-authenticated SSL with a certificate issued from a trusted CA to pass.
19. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
20. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:
a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.
b. Enter the risk percentage.
c. Click OK.
21. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
22. Click Submit to create the resource rule.
Step 4: Configure
the Microsoft Entra ID TenantYou must configure the Microsoft Azure AD Conditional Access Tenant for each Customer Tenant application that requires a custom control for multi-factor authentication. You must first configure a custom control and then configure the policies to prevent access to specific (or all) applications.
The Microsoft Azure AD Conditional Access policy is similar to an Identity as a Service resource rule. The policy may apply to a specific user or the interface being used, for example. The policy can also enforce custom controls.
Step A: Configure custom controls
1. Ensure that you have synchronized your Azure AD users with Identity as a Service. See Synchronize Microsoft Entra ID External users with Identity as a Service and Sync an on-premises AD with Microsoft Entra ID External.
2. Go to the Microsoft Entra ID portal and log in to the Customer Tenant as an administrator.
3. In the Home page, select Microsoft Entra Conditional Access.
4. Under Manage, click Custom controls.
5. Click New custom control.
6. In the text box, enter the auto-generated Azure AD Access Custom Control JSON Text that you copied in Step 2: Add Microsoft Azure AD Conditional Access OIDC to Identity as a Service.
You can change the Id value, if required, for example if you plan to define multiple custom controls. For example, "Id": "Identity as a Service MFA",
7. Click Create.
Step B: Configure policies
1. In the Microsoft Entra ID Conditional Access page, select Policies.
2. Click New Policy. The New Policy dialog box appears.
3. Under Assignments, select Users and groups.
4. In the Include pane, select Select users and groups and select the specific set of users you want to associate with the policy.
5. Click Done.
Attention: Ensure that you do not select your initial admin user as a user of this policy as doing so can potentially lock you out of the Microsoft Entra ID portal.
6. Under Assignments, click Cloud apps.
7. Select to Include specific apps or ALL applications. The options are
● None
● All cloud apps
● Select apps
If you choose Select apps, click Select and then from the Applications list, select the specific apps you want to include.
8. Click Select.
9. Click Done.
10. Under Access controls, click Grant.
11. Under Select the controls to be enforced, select Grant access.
12. Select Identity as a Service MFA (or select the required Id value of the custom control if you created several custom controls).
13. Click Select.
14. Toggle Enable policy to On.
15. Click Create.
Step 5: Test
the Conditional Access Control in Conditional Access Control in Microsoft
Entra ID1. Go to the Microsoft Entra ID portal.
2. Log into Microsoft Entra ID with a user that you selected as part of the policy definition for conditional access.
3. Enter the password. You are redirected to Identity as a Service for second-factor authentication.
4. Respond to the second-factor challenge.
5. Confirm that the user has logged in to the Azure AD portal successfully.