First time creating a connector? Read this first.
Here are some more details about these requirements:
- The endpoint and API key for Azure AI Search. Create an endpoint and API key.
-
The name of the index in Azure AI Search. Create an index.
The Azure AI Search index that you use must have an index schema that is compatible with the schema of the documents that Unstructured produces for you. Unstructured cannot provide a schema that is guaranteed to work in all circumstances. This is because these schemas will vary based on your source files’ types; how you want Unstructured to partition, chunk, and generate embeddings; any custom post-processing code that you run; and other factors. You can adapt the following index schema example for your own needs. Be sure to replace
<number-of-dimensions>(in three locations in the following example) with the number of dimensions of the embedding model you are using:See also:Therecord_id,element_id, andidfields are closely related, but each has a distinct purpose. For more information, see How connectors use record IDs, element IDs, and IDs.
Set up Enterprise Connect authentication
Enterprise Connect is available for dedicated instance customers only, and must be enabled on your instance before use. Contact your Unstructured account team or Unstructured Support to request access and have it enabled.
- Enable role-based access on your Azure AI Search service. Follow the instructions in Enable role-based access control for Azure AI Search in the Azure AI Search documentation. In the Azure portal, navigate to your search service, select Settings > Keys, and select Both to allow both API key and role-based authentication. If you want to use role-based authentication exclusively, select Role-based access control instead.
-
Create an App Registration for Unstructured in Microsoft Entra ID.
In your Azure subscription, follow the instructions in How to register an app in Microsoft Entra ID in the Microsoft Entra documentation. Enter a meaningful name for your App Registration (for example,
unstructured-connector). For Supported account types, select Single tenant only. You are registering this app for a third-party service (Unstructured) accessing resources in your own tenant. This is the single-tenant scenario as defined by Microsoft. -
Add a federated identity credential to the App Registration.
Follow the instructions in Configure an app to trust an external identity provider in the Microsoft Entra documentation. Navigate to your App Registration, select Certificates & secrets in the left navigation pane, select the Federated credentials tab, and select Add credential.
For Federated credential scenario, select Other issuer.
Set the following values:
Your Unstructured instance may require more than one federated identity credential. The platform uses separate identities for different operations, such as connection testing and running workflows. If your account team provides more than one Subject value, repeat these steps for each one.
Field Value Name A unique name for this credential (for example, unstructured-federated-credential). This cannot be changed after creation.Issuer The OIDC issuer URL for your Unstructured instance. Get this value from your Unstructured account team. (Example: https://oidc.prod-aks.example.com/...)Subject The service account identity for your Unstructured instance. Get this value from your Unstructured account team. (Example: system:serviceaccount:etl:etl-job-runner) This value must exactly match what Unstructured provides. If it does not match, the token exchange will fail without displaying an error.Audience Set this to api://AzureADTokenExchange. -
Add a role assignment to grant your App Registration access to your Azure AI Search service.
See Assign Azure roles using the Azure portal in the Azure documentation. Use the following values:
- Scope: the Azure AI Search service that contains the index you want the connector to access.
- Role: assign both Search Index Data Contributor (required for document indexing) and Search Service Contributor (required for connection testing). Repeat the role assignment steps for each role.
- Members: select User, group, or service principal, then search for and select the App Registration you created in Step 2.
-
Note the following values from your App Registration. You will need them when configuring the connector in Unstructured. Both values are available on the Overview page of your App Registration in the Microsoft Entra admin center.
- The Tenant ID (also called Directory ID) for your Azure subscription.
- The Client ID of your App Registration.
Create the destination connector
To create the destination connector:- On the sidebar, click Connectors.
- Click Destinations.
- Click New or Create Connector.
- Give the connector some unique Name.
- In the Provider area, click Azure AI Search.
- Click Continue.
- Follow the on-screen instructions to fill in the fields as described later on this page.
- Click Save and Test.
- Name (required): A unique name for this connector.
-
Endpoint (required): The endpoint URL for your Azure AI Search service, in the format
https://<service-name>.search.windows.net. - Index Name (required): The name of the index in your Azure AI Search service.
-
Authentication Method (required): The authentication method to use. Select API Key or Enterprise Connect (Workload Identity).
API Key only:
- API Key (required): The admin API key for your Azure AI Search service.
- Tenant ID (required): The Tenant ID (also called Directory ID) for your Azure subscription.
- Client ID (required): The Client ID of your App Registration.

