Microsoft Defender for Cloud Apps
Architecture and deployment

Onboard non-Microsoft IdP catalog apps for Conditional Access app control | Microsoft Defender for Cloud Apps

In brief

The procedure now more clearly explains that administrators should copy the SSO URL and attributes, then enter them in the IdP’s custom app configuration steps.

What Defender admins need to know

Administrators following this procedure have clearer guidance; no configuration change is required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Onboard non-Microsoft IdP catalog apps for Conditional Access app control

Prerequisites

Before you begin, make sure your environment meets the following requirements:

  • Your organization must have the following licenses to use conditional access app control:

    • The license required by your identity provider (IdP) solution

Configure your IdP to work with Defender for Cloud Apps

ThisThe following procedure describes how to route app sessions from other IdP solutions to Defender for Cloud Apps.

Copy your app's single sign-on configuration information because you will enter it in the IdP configuration steps that follow. When you're finished, select **Next** to continue.
  1. Continuing on the IDENTITY PROVIDER page of the wizard, either upload a metadata file from your IdP or enter app data manually.

    • The Single sign-on service URL. This is the URL that your IdP uses to receive single sign-on requests.
    • A SAML certificate, if your IdP provides one. In such cases, select the Use identity provider's SAML certificate option, and then upload the certificate file.
  2. Continuing on the IDENTITY PROVIDER page of the wizard, copy both the single sign-on URL and all attributes and values so that you can enter them in your IdP's custom app configuration in the next steps.

    When you're done, select Next to continue.