Onboard and deploy Conditional Access App Control for any app

Applies to: Microsoft Cloud App Security

Session controls in Microsoft Cloud App Security can be configured to work with any web apps. This article describes how to onboard and deploy custom line-of-business apps, non-featured SaaS apps, and on-premise apps hosted via the Azure Active Directory (Azure AD) Application Proxy with Session controls.

For a list of apps that are featured by Cloud App Security to work out-of-the-box, see Protect apps with Microsoft Cloud App Security Conditional Access App Control.

Prerequisites

  • Your organization must have the following licenses to use Conditional Access App Control:

    • Azure Active Directory Premium P1 or higher
    • Microsoft Cloud App Security
  • Apps must be configured with single sign-on in Azure AD

  • Apps must use SAML or Open ID Connect 2.0 protocols

To deploy any app

Follow these steps to configure any app to be controlled by Cloud App Security Conditional Access App Control.

Step 1: Configure Azure AD Conditional Access policy to route relevant apps to Cloud App Security

Step 2: Configure the users that will deploy the app

Step 3: Configure the app that you are deploying

Step 4: Verify that the app is working correctly

Step 5: Enable the app for use in your organization

Step 6: Update the Azure AD policy

Note

To deploy Conditional Access App Control for Azure AD apps, you need a valid license for Azure Active Directory Premium P1 or higher as well as a Cloud App Security license.

Step 1: Configure Azure AD Conditional Access policy to route relevant apps to Cloud App Security

  1. In Azure AD, browser to Security > Conditional Access.

  2. On the Conditional Access blade, in the toolbar at the top, click New policy.

  3. On the New blade, in the Name textbox, enter the policy name.

  4. Under Assignments, click Users and groups, assign the users that will be onboarding (initial sign on and verification) the app, and then click Done.

  5. Under Assignments, click Cloud apps, assign the apps you want to control with Conditional Access App Control, and then click Done.

  6. Under Access controls, click Session, select Use Conditional Access App Control and choose a built-in policies (Monitor only or Block downloads) or Use custom policy to set an advanced policy in Cloud App Security, and then click Select.

    Azure AD conditional access

  7. Optional: Add conditions and grant controls as required.

  8. Set Enable policy to On and then click Create.

Step 2: Configure the users that will deploy the app

  1. In Cloud App Security, in the menu bar, click the settings cog settings icon and select Settings.

  2. Under Conditional Access App Control, select App onboarding/maintenance.

  3. Enter the user principal name or email for the users that will be onboarding the app, and then click Save.

    Screenshot of settings for App onboarding and maintenance.

Step 3: Configure the app that you are deploying

Go to the app that you are deploying. The page you see depends on whether the app is recognized. Do one of the following:

App status Description Steps
Not recognized You will see an app not recognized page prompting you to configure your app. 1. Add the app to Conditional Access App Control.
2. Add the domains for the app, and then return to the app and refresh the page.
3. Install the certificates for the app.
Recognized You will see an onboarding page prompting you to continue the app configuration process. - Install the certificates for the app.

Note: Make sure the app is configured with all domains required for the app to function correctly. To configure additional domains, proceed to Add the domains for the app, and then return to the app page.

To add a new app

  1. In the menu bar, click the settings cog settings icon, and then select Conditional Access App Control.

  2. Click View new apps.

    Conditional access app control view new apps

  3. In the screen that opens, you can see a list of new apps. For each app you are onboarding, click on the + sign, and then click Add.

    Note

    If an app does not appear in the Cloud App Security app catalog, it will appear in the dialog under unidentified apps along with the login URL. When you click the + sign for these apps, you can onboard the application as a custom app.

    Conditional access app control discovered Azure AD apps

To add domains for an app

Associating the correct domains to an app allows Cloud App Security to enforce policies and audit activities.

For example, if you have configured a policy that blocks downloading files for an associated domain, file downloads by the app from that domain will be blocked. However, file downloads by the app from domains not associated with the app will not be blocked and the action will not be audited in the activity log.

Note

Cloud App Security still adds a suffix to domains not associated with the app to ensure a seamless user experience.

  1. From within the app, on the Cloud App Security admin toolbar, click Discovered domains.

    Note

    The admin toolbar is only visible to users with permissions to onboard or maintenance apps.

  2. In the Discovered domains panel, make a note of domain names or export the list as a .csv file.

    Note

    The panel displays a list of discovered domains that are not associated in the app. The domain names are fully qualified.

  3. Go to Cloud App Security, in the menu bar, click the settings cog settings icon and select Conditional Access App Control.
  4. In the list of apps, on the row in which the app you are deploying appears, choose the three dots at the end of the row, and then under APP DETAILS, choose Edit.

    Tip

    To view the list of domains configured in the app, click View app domains.

  5. In User-defined domains, enter all the domains you want to associate with this app, and then click Save.

    Note

    You can use the * wildcard character as a placeholder for any character. When adding domains, decide whether you want to add specific domains (sub1.contoso.com,sub2.contoso.com) or multiple domains (*.contoso.com).

To install root certificates

  1. Repeat the following steps to install the Current CA and Next CA self-signed root certificates.

    1. Select the certificate.
    2. Click Open, and when prompted click Open again.
    3. Click Install certificate.
    4. Choose either Current User or Local Machine.
    5. Select Place all certificates in the following store and then click Browse.
    6. Select Trusted Root Certificate Authorities and then click OK.
    7. Click Finish.

    Note

    For the certificates to be recognized, once you have installed the certificate, you must restart the browser and go to the same page.

  2. Click Continue.

Step 4: Verify that the app is working correctly

  1. Verify that the sign in flow works correctly.
  2. Once you are in the app, perform the following checks:
    1. Visit all pages within the app that are part of a users’ work process and verify that the pages render correctly.
    2. Verify that the behavior and functionality of the app is not adversely affected by performing common actions such as downloading and uploading files.
    3. Review the list of domains associated with the app. For more information, see Add the domains for the app.

Step 5: Enable the app for use in your organization

Once you are ready to enable the app for use in your organization's production environment, do the following steps.

  1. In Cloud App Security, click the settings cog settings icon, and then select Conditional Access App Control.
  2. In the list of apps, on the row in which the app you are deploying appears, choose the three dots at the end of the row, and then choose Edit app.
  3. Select Use with Conditional Access App Control and then click Save.

Step 6: Update the Azure AD policy

  1. In Azure AD, under Security, click Conditional Access.
  2. Update the policy you created earlier to include the relevant users, groups, and controls you require.
  3. Under Session > Use Conditional Access App Control, if you selected Use Custom Policy, go to Cloud App Security and create a corresponding session policy. For more information, see Session policies.

Next steps

See also

If you run into any problems, we're here to help. To get assistance or support for your product issue, please open a support ticket.