Microsoft Entra ID

Set up an integration with Microsoft Entra ID to streamline the discovery of your SaaS applications.

Overview

Microsoft Entra ID is Microsoft’s cloud-based identity and access management service, which helps your employees sign in and access resources in:

  • External resources, such as Microsoft 365, the Azure portal, and thousands of other SaaS applications.
  • Internal resources, such as apps on your corporate network and intranet, and any cloud apps your organization developed.

Integration Details

  • Integration categories:
    • Single Sign-On Systems (SSO)
  • Supported regions
    • Global
    • China
  • Authentication mechanism:

Implementation Details

The process involves querying the Microsoft Graph API's servicePrincipal endpoint with specific filters applied:

  • servicePrincipalType eq 'Application' (servicePrincipalType must be 'Application')
  • accountEnabled eq true (accountEnabled must be true)

LeanIX excludes applications that lack defined oauth2PermissionScopes. This approach, using servicePrincipals instead of the application endpoint, allows us to manage access to applications across different tenants, extending beyond those solely within our current tenant. For a detailed guide on discovering and managing service principals and applications, see Microsoft's documentation Application and Service Principal Objects.

LeanIX integration supports two regions - Global and China, with API calls directed to different URLs depending on the region.

Authorization and permissions are managed using OAuth 2.0 client credentials grant flow, as outlined in OAuth 2.0 Client Credentials Grant Flow. The required scope for API access is specified by .default within the https://graph.microsoft.com/resource.

For information on managing permissions and consent for the applications, see Permissions and Consent Overview. Additionally, for details on handling national cloud deployments, including URIs specific to national clouds, see Authentication for National Clouds. This comprehensive approach ensures secure and scalable management of SaaS applications across different environments and regions.

SaaS Discovery with Entra ID

With Entra ID integration, LeanIX identifies services for SaaS discovery by reading servicePrincipal, which are visible under the Enterprise Registration blade in Azure Active Directory (AAD). For SaaS identification, LeanIX relies on the Gallery Template used, specifically the ID of the underlying application (Application IDs). Additionally, LeanIX collects the unique identifiers (External IDs) and names (External names) of the applications, although detection is not based on these collected attributes. External IDs and external names are used to detect multiple instances of SaaS. For more information, see Detecting Multiple Instances of SaaS.

👍

Note

LeanIX does not collect any login or user data, ensuring compliance with data privacy regulations.

Set up Microsoft Entra ID

Register a new application in Microsoft Entra ID

  1. Based on the region which you want to connect, sign in to the Global Azure portal or China Azure portal. Use the Azure administrator account that is also a member of the Global Administrator directory role in your Microsoft Entra ID tenant.
  1. On the left navigation pane, click Microsoft Entra ID.

  1. On the Microsoft Entra ID page, click App registrations.

  2. On the App registrations page, in the toolbar on the top, click New registration.

  3. Register an application page opens, perform the following steps:

    1. In the Name textbox, type LeanIX SaaS Discovery Integration (it is just a label so it can be anything that will make you identify it relates to LeanIX integration).
    2. Under Supported account types select Accounts in this organizational directory only (Default Directory only - Single tenant).
    3. Click Register at the bottom of the screen.

Grant permissions to the application

  1. Now that we have the application we need to grant permissions, in the left menu click API permissions.

  2. Click the Add a permission button.

  3. The new configuration panel Request API permissions will display on the right, select the Microsoft Graph API, pick Application permissions, and search for Application.Read.All.

  4. Click on the Add permissions button at the bottom to assign permission to the LeanIX application.

  5. Click on the Grant admin consent for Default Directory button to enable configured permissions for the application

  1. Next, click Yes to grant consent for the requested permissions.
  2. The permission status indicator in the API permissions page will change to approved.

Gather configuration settings

  1. Return to the application overview section (App Registrations > click on created app) from where you will need to grab the following identifiers: Application (client) ID and Directory (tenant) ID.

  2. In the left menu, navigate to Certificates & secrets to generate a client secret, also called the application password.

  3. Click on the New client secret button to create a new password.

    1. Please choose the description for the secret (e.g. LeanIX SaaS Discovery Integration secret) or leave it empty

    2. Select the expiration length of the secret. Once the expiration date of the created client secret is reached, you will have to create a new one and reconfigure the integration in the LeanIX application.

    3. Click Add

  4. Copy the Secret Value to your clipboard.

🚧

Store the secret value

Please make a note of the client secret value as soon as it is revealed. It will be masked when you navigate away from the Certificates & secrets panel.
This value needs to be added to LeanIX under Client Secret.

Pass configuration values to the LeanIX app

  1. Proceed to LeanIX and input the credentials you have generated on the Azure Admin Portal.

    Entering the Azure Admin Portal Credentials in LeanIX

    Entering the Azure Admin Portal Credentials in LeanIX

  2. Click Finish and wait for the connection to be established.