Documentation

Technical Prerequisites

For indexing, you need to register an Entra Id application 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. Please search for the following permissions and check the respective boxes:

    1. Search for ExternalConnection.ReadWrite.All and check the Box

    2. Search for ExternalItem.ReadWrite.All and check the box

12. Click on Add permissions

13. Grant the consent

14. Got to certificates and secrets

15. Generate a new Client Secret

    

16. Give it a name and an expiration date

17. Create the secret

18. Then make a note of the value

    

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

    

Configuration

You can access this dialog as part of the connector configuration, if the connector has Microsoft Search as target.

1. Tenant Id: is the tenant id from the app registration above.

2. Client Id: is the client id from the app registration above

3. Client secret: is the secret from the app registration above

4. Connection Id: Is the name of the external connection where the connector should index the documents into.

5. Connection description: this is the description which the connector uses during index creation. For normal operations, this field is not needed.

6. Response timeout: determines the timeout when waiting for responses in milliseconds.

7. Connection timeout: determines the timeout when waiting for connections to the instance in milliseconds.

8. Socket timeout: determines the timeout when waiting for connections to the instance in milliseconds.

9. Vector field for title. If you use vector search for the vectorization stages), then this field is used to push the vectorized title into.
   If you configure the search engine for querying data (cf. Search Experience and Query Pipelines ), then this field is used for issuing vector queries.

10. Vector field for body. If you use vector search, then this field is used to push the vectorized body into.
    If you configure the search engine for querying data, then this field is used for issuing vector queries.

11. Filters (aka refiners aka aggregations)

    1. Within this dialog you can add and remove filters. This does not mean that filters will be shown in the search interface right away but it is needed to tell the search engine to return calculated filters.

    2. Filter type: defines if this is a term filter (such as for file types), range filters (such as for prices) or date filters.

    3. Fieldname: is the name of the field which the filter should be computed for.

    4. Number of values to show: for term filters this defines how many values should be returned.

    5. Sorting: defines if the filter buckets should be sorted based on the document frequency (number of results) or lexicographically

    6. Sort direction: if sorting should be descending or ascending (based on the ordering type in e.)

When finished with setting these fields, click on validate and save. If you observe any issues, then the validator will let you know or you can find more insights in the log files.

Managing the Search Schema

The Search schema field and also the controls are described at Index Creation and Management .

The connector comes with a standard schema, which you can manage from the configuration dialog.

There is no need for a principal index, as Microsoft Search comes with its own principal store.