Partager via

Classic portal: Deploy Conditional Access App Control for custom apps with non-Microsoft identity providers

  • Article

Note

This docset refers to the Microsoft Defender for Cloud Apps classic portal. Microsoft Defender for Cloud Apps is now part of Microsoft Defender XDR, which correlates signals from across the Microsoft Defender suite and provides incident-level detection, investigation, and powerful response capabilities.

As of June 2024, all customers using the classic Defender for Cloud Apps portal are automatically redirected to Microsoft Defender XDR, with no option to revert back to the classic portal. For more information, see Microsoft Defender for Cloud Apps in Microsoft Defender XDR and the Microsoft Defender for Cloud Apps documentation.

Session controls in Microsoft Defender for Cloud Apps 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-premises apps hosted via the Microsoft Entra application proxy with session controls. It provides steps to route app sessions from other IdP solutions to Defender for Cloud Apps. For Microsoft Entra ID, see Deploy Conditional Access App Control for custom apps using Microsoft Entra ID.

Access and session controls in Microsoft Defender for Cloud Apps work with applications from the Cloud app catalog and with custom applications.

Defender for Cloud Apps preonboards the following apps to work out-of-the-box:

  • Box
  • Concur
  • CornerStone on Demand
  • DocuSign
  • Dropbox
  • Egnyte
  • GitHub
  • Google Workspace
  • HighQ
  • JIRA/Confluence
  • LinkedIn Learning
  • Microsoft Azure DevOps Services (Visual Studio Team Services)
  • Microsoft Azure portal
  • Microsoft Dynamics 365 CRM
  • Microsoft Exchange Online
  • Microsoft OneDrive
  • Microsoft Power BI
  • Microsoft SharePoint Online
  • Microsoft Teams
  • Microsoft Yammer
  • Salesforce
  • Slack
  • Tableau
  • Workday
  • Workiva
  • Workplace from Meta

If you're interested in a specific app being preonboarded, send us details about the app. Be sure to send the use case you're interested in for onboarding it.

Prerequisites

Add admins to the app onboarding/maintenance list

  1. In the menu bar of Defender for Cloud Apps, select the settings cog settings icon 4. 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 select Save.

    Screenshot of settings for App onboarding and maintenance.

Check for necessary licenses

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

    • The license required by your identity provider (IdP) solution
    • Microsoft Defender for Cloud Apps

  • Apps must be configured with single sign-on

  • Apps must use the following authentication protocols:

    IdP Protocols
    Other SAML 2.0

To deploy any app

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

  1. Configure your IdP to work with Defender for Cloud Apps

  2. Configure the app that you are deploying

  3. Verify that the app is working correctly

  4. Enable the app for use in your organization

Note

To deploy Conditional Access App Control for Microsoft Entra apps, you need a valid license for Microsoft Entra ID P1 or higher as well as a Defender for Cloud Apps license.

Step 1: Configure your IdP to work with Defender for Cloud Apps

Note

For examples of how to configure IdP solutions, see:

  1. In Defender for Cloud Apps, browse to Investigate > Connected apps > Conditional Access App Control apps.

  2. Select the plus sign (+), and in the pop-up, select the app you want to deploy, and then select Start Wizard.

  3. On the APP INFORMATION page, fill out the form using the information from your app's single sign-on configuration page, and then select Next.

    • If your IdP provides a single sign-on metadata file for the selected app, select Upload metadata file from the app and upload the metadata file.
    • Or, select Fill in data manually and provide the following information:
      • Assertion consumer service URL
      • If your app provides a SAML certificate, select Use <app_name> SAML certificate and upload the certificate file.

    Screenshot showing app information page.

  4. On the IDENTITY PROVIDER page, use the provided steps to set up a new application in your IdP's portal, and then select Next.

    1. Go to your IdP's portal and create a new custom SAML app.
    2. Copy the single sign-on configuration of the existing <app_name> app to the new custom app.
    3. Assign users to the new custom app.
    4. Copy the apps single sign-on configuration information. You'll need it in the next step.

    Screenshot showing gather identity provider information page.

    Note

    These steps may differ slightly depending on your identity provider. This step is recommended for the following reasons:

    • Some identity providers do not allow you to change the SAML attributes or URL properties of a gallery app
    • Configuring a custom app enables you to test this application with access and session controls without changing the existing behavior for your organization.

  5. On the next page, fill out the form using the information from your app's single sign-on configuration page, and then select Next.

    • If your IdP provides a single sign-on metadata file for the selected app, select Upload metadata file from the app and upload the metadata file.
    • Or, select Fill in data manually and provide the following information:
      • Assertion consumer service URL
      • If your app provides a SAML certificate, select Use <app_name> SAML certificate and upload the certificate file.

    Screenshot showing enter identity provider information page.

  6. On the next page, copy the following information, and then select Next. You'll need the information in the next step.

    • Single sign-on URL
    • Attributes and values

    Screenshot showing gather identity providers SAML information page.

  7. In your IdP's portal, do the following:

    Note

    The settings are commonly found in IdP portal's custom app settings page.

    1. Recommended - Create a backup of your current settings.

    2. Replace the single sign-on URL field value with the Defender for Cloud Apps SAML single sign-on URL you noted earlier.

      Note

      Some providers may refer to the single sign-on URL as the Reply URL.

    3. Add the attributes and values you made a note of earlier to the app's properties.

      Note

      • Some providers may refer to them as User attributes or Claims.
      • When creating a new SAML app, the Okta Identity Provider limits attributes to 1024 characters. To mitigate this limitation, first create the app without the relevant attributes. After creating the app, edit it, and then add the relevant attributes.

    4. Verify that the name identifier is in the email address format.

    5. Save your settings.

  8. On the APP CHANGES page, do the following, and then select Next. You'll need the information in the next step.

    • Copy the Single sign-on URL
    • Download the Defender for Cloud Apps SAML certificate

    Screenshot showing gather Defender for Cloud Apps SAML information page.

  9. In your app's portal, on the single sign-on settings, do the following:

    1. Recommended - Create a backup of your current settings.
    2. In the single sign-on URL field, enter the Defender for Cloud Apps single sign-on URL you made a note of earlier.
    3. Upload the Defender for Cloud Apps SAML certificate you downloaded earlier.

    Note

    • After saving your settings, all associated login requests to this app will be routed through Conditional Access App Control.
    • The Defender for Cloud Apps SAML certificate is valid for one year. After it expires, a new certificate will need to be generated.

Step 2: Add the app manually and install certificates, if necessary

Applications in the app catalog are automatically populated into the table under Connected Apps. Check that the app you want to deploy is recognized by navigating there.

  1. In the menu bar of Defender for Cloud Apps, select the settings cog settings icon 1., and select the Conditional Access App Control tab to access a table of applications that can be configured with access and session policies.

    Conditional access app control apps.

  2. Select the App: Select apps… dropdown menu to filter and search for the app you want to deploy.

    Select App: Select apps to search for the app.

  3. If you don't see the app there, you'll have to manually add it.

How to manually add an unidentified app

  1. In the banner, select View new apps.

    Conditional access app control view new apps.

  2. In the list of new apps, for each app that you're onboarding, select the + sign, and then select Add.

    Note

    If an app does not appear in the Defender for Cloud Apps 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 Microsoft Entra apps.

To add domains for an app

Associating the correct domains to an app allows Defender for Cloud Apps to enforce policies and audit activities.

For example, if you've 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 won't be blocked and the action won't be audited in the activity log.

Note

Defender for Cloud Apps still adds a suffix to domains not associated with the app to ensure a seamless user experience.

  1. From within the app, on the Defender for Cloud Apps admin toolbar, select 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 Defender for Cloud Apps, in the menu bar, select the settings cog settings icon 2. and select Conditional Access App Control.
  4. In the list of apps, on the row in which the app you're 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, select View app domains.

  5. In User-defined domains, enter all the domains you want to associate with this app, and then select 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).

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. Select Open, and when prompted select Open again.
    3. Select Install certificate.
    4. Choose either Current User or Local Machine.
    5. Select Place all certificates in the following store and then select Browse.
    6. Select Trusted Root Certificate Authorities and then select OK.
    7. Select 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. Select Continue.

  3. Check that the application is available in the table.

    Check if app is available in table.

Step 3: Verify that the app is working correctly

To verify that the application is being proxied, first perform either a hard sign-out of browsers associated with the application or open a new browser with incognito mode.

Open the application and perform the following checks:

  • Check that the URL contains the .mcas suffix
  • Visit all pages within the app that are part of a user's work process and verify that the pages render correctly.
  • Verify that the behavior and functionality of the app isn't adversely affected by performing common actions such as downloading and uploading files.
  • Review the list of domains associated with the app. For more information, see Add the domains for the app.

If you encounter errors or issues, use the admin toolbar to gather resources such as .har files and recorded sessions for filing a support ticket.

Step 4: Enable the app for use in your organization

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

  1. In Defender for Cloud Apps, select the settings cog settings icon 3., and then select Conditional Access App Control.

  2. In the list of apps, on the row in which the app you're 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 select Save.

    Enable session controls pop-up.

Next steps

« PREVIOUS: Deploy Conditional Access App Control for catalog apps

NEXT: How to create a session policy »

See also

Introduction to Conditional Access App Control

Troubleshooting access and session controls

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.