Microsoft Intune and Microsoft Defender

Identity and Trust can query Microsoft Entra ID to get identity information based on sign-in events from Microsoft Intune or Microsoft Defender on endpoint computers. When you export sign-in events to Azure Event Hubs, Identity and Trust retrieves identities in a way that minimizes resource usage, reduces time delays, and ensures reliable access to the necessary data.

Prerequisites:

Workflow

  1. An Azure administrator adds Azure API permissions to the Entra ID application that is integrated with Identity and Trust.

  2. An Azure administrator configures Intune or Defender to export logs to the dedicate EventHub in Entra ID.

  3. An administrator of a Security Gateway that is integrated with Identity and Trust makes access control rules based on information from Intune and Defender. Data flow:

    Intune/Defender on the user endpoint computer => Entra ID sign-in logs (from Intune) and/or Entra ID advanced hunting (from Defender) => Azure EventHub => Identity and Trust => Security Gateway.

Comparison of Automatic and Manual Configuration of Intune and Defender

You can integrate Identity and Trust with Intune/Defender manually or automatically. The functionality of an automatic integration and a manual integration is the same.

In an Automatic Integration, an Azure administrator temporarily grants Azure privileges to Check Point. Check Point then makes the necessary configurations on the Azure side (the first two steps in the Workflow above).

In a Manual Integration, an Azure administrator makes the necessary configurations on the Azure side (the first two steps in the Workflow above). In a Manual Integration, you do not need to grant Azure privileges to Check Point.

Note - In an automatic integration, the Azure Event Hub Namespace and the associated Azure Storage Account are created with public network access enabled for all networks by default. To limit access to specific IPs, contact Check Point Support and reference sk185014.

Automatic Integration of Identity and Trust with Microsoft Intune and Microsoft Defender

  1. In Identity and Trust, from the left toolbar, click Integrations.

  2. In the Integrations section, click the + (plus sign) button.

  3. Select Identity Integrations.

  4. Select Microsoft Intune or Microsoft Defender. If you want to integrate both of them, it does not matter which one you select.

    The Microsoft Intune or Microsoft Defender integration window opens.

  5. Select Automatic.

  6. In Identity and Trust, click the link "First login to your Microsoft Entra ID Account".

    An Entra ID login window opens. The window contains a list of permissions that Check Point requires to perform automatic integration.

  7. Click Accept.

    The Entra ID login window closes. If Entra ID successfully granted permissions to Check Point, a confirmation message appears in the Check Point Portal.

  8. For the Integration Title, enter a title. After you create the integration, this title appears in the Identity and Trust Integrations section.

  9. Select an Entra ID Integration.

  10. Select a Subscription Name.

  11. Select a Resource Group Name.

  12. Optional - If you want to integrate both Intune and Defender, select the relevant checkbox:.

    • In a Microsoft Intune window, select Use this configuration to create Microsoft Defender integration as well.

    • In a Microsoft Defender window, select Use this configuration to create Microsoft Intune integration as well.

  13. Click Test permissions. If the test fails, follow the instructions in the failure message.

  14. Click Save.

    The Microsoft Intune and/or Microsoft Defender integration appears in the gallery.

Manual Integration of Identity and Trust with Microsoft Intune and Microsoft Defender

Keep Identity and Trust and Microsoft Entra ID open throughout this procedure.

Replacing an Invalid or Expired Client Secret

Note - This procedure applies only to Microsoft Intune and Microsoft Defender integrations that use SCIM Automatic Sync.

When you integrate Microsoft Intune or Microsoft Defender with a directory that uses SCIM (Automatic Sync), Identity and Trust creates a dedicated application in Microsoft Entra ID for the integration. This application uses a client secret to authenticate.

If the client secret becomes invalid or expires, the integration stops working and Identity and Trust cannot collect sign-in data from Intune or Defender. When this occurs, the integration card on the Integrations page shows the warning:

“Your client secret is invalid or expired.”

To restore the integration, generate a new client secret in Microsoft Entra ID and update the integration with the new value.

To replace an invalid or expired client secret:

  1. In Identity and Trust, from the left toolbar, click Integrations.

  2. On the Microsoft Intune or Microsoft Defender integration card that shows the error, click Update Credentials. Alternatively, click the three dots and then click Edit.

    The Edit Microsoft Intune or Edit Microsoft Defender window opens.

  3. Copy the value from the Application (client) ID field.

  4. Keep the Edit window open.

  5. In a web browser, go to entra.microsoft.com.

  6. Paste the Application (client) ID into the Search field and select the application under App registrations.

  7. On the application's page, select Manage > Certificates & secrets.

  8. On the Client secrets tab, click New client secret.

  9. In the Add a client secret pane:

    1. Enter a description.

    2. Select an expiration period.

    3. Click Add.

    The new secret appears on the Client secrets tab.

  10. Copy the secret from the Value column.

    Important - You cannot retrieve this secret value after you leave the page or close the pane.

  11. In the Identity and Trust portal, return to the open Edit Microsoft Intune or Edit Microsoft Defender window.

  12. Paste the secret value into the Client Secret field.

  13. Click Test connectivity.

  14. When the success message appears, click Save.

    Identity and Trust updates the integration card with the new client secret, removes the error message, and changes the integration status to Active.