Documentation

Microsoft Entra ID Connector

For a general introduction to the connector, please refer to RheinInsights Atlassian Entra ID Connector.

Entra Id Configuration

Application Registration

The connector acts as an Entra Id application. This application must be registered as follows

  1. Navigate to https://portal.azure.com

  2. Open Entra Id

  3. Open App registrations

  4. Click on New registration

  5. Give it a name

  6. Click on Register

  7. Click on API permissions

  8. Add a Permission

  9. Click on Microsoft Graph

  10. Choose Application Permissions

  11. Search for User.Read.All and check the Box

  12. Optionally search for Group.Read.All and check the box, if you want to use the connector for indexing user-group relationships for secure search.

  13. Click on Add permissions

  14. Grant the consent

  15. Got to certificates and secrets

  16. Generate a new Client Secret

  17. Give it a name and an expiration date

  18. Create the secret

  19. Then make a note of the value

  20. Click on Overview and make a note of client Id and tenant Id

Content Source Configuration

The content source configuration of the connector comprises the following mandatory configuration fields.

Within the connector’s configuration please add the following information:

  1. Tenant Id. Is the tenant Id information from Step 20 above.

  2. Client Id. Is the client Id information from Step 20 above.

  3. Client secret is the client secret from Step 19 above.

  4. Rate limit: You can furthermore reduce the number of API calls per second.

  5. Excluded profiles: here you can exclude certain profiles from crawling. Please use either the user’s GUIDs or user principal names.

After entering the configuration parameters, click on validate. This validates the content crawl configuration directly against the content source. If there are issues when connecting, the validator will indicate these on the page. Otherwise, you can save the configuration and continue with Content Transformation configuration.

Recommended Crawl Schedules

Content Crawls

Depending on your requirements, we recommend to run a Full Scan every day or even more often. Principal crawls should run twice a day. For more information see Crawl Scheduling .

Principal Crawls

Depending on your requirements, we recommend to run a Full Principal Scan every day or even more often. Principal crawls should run twice a day. For more information see Crawl Scheduling .