Create or Update Data Source (Preview REST API)
Important
This API reference is for a legacy version. See Data plane REST operations for updated reference documentation. Use the filter on the top left to select a version.
Applies to: 2023-07-01-Preview. This version is no longer supported. Upgrade immediately to a newer version.
Important
2023-07-01-Preview (no changes).
2021-04-30-Preview adds managed identity support for indexer connections to other Azure resources:
- "credentials" accepts an Azure resource ID as a value, provided that the search service runs under a managed identity and Azure role assignments grant read access to data.
- "identity" accepts a user-assigned managed identity. This property is first-level for data connections. It's also under "encryptionKey" for retrieving a customer-managed key in Azure Key Vault.
- Azure Files support is in preview. Use a preview API to index from this data source.
2020-06-30-Preview adds:
- "dataDeletionDetectionPolicy" accepts "NativeBlobSoftDeleteDeletionDetectionPolicy" for blob indexers.
- Azure Database for MySQL support is in preview. Use a preview API to index from this data source.
- Cosmos DB MongoDB API and Gremlin API support is in preview. Use a preview API to index from this data source.
In Azure AI Search, a data source is used with indexers, providing the connection information for on demand or scheduled data refresh of a target index, pulling data from supported data sources.
You can use either POST or PUT on a create request. For either one, the request body provides the object definition.
POST https://[service name].search.windows.net/datasources?api-version=[api-version]
Content-Type: application/json
api-key: [admin key]
For update requests, use PUT and specify the indexer name on the URI.
PUT https://[service name].search.windows.net/datasources/[data source name]?api-version=[api-version]
Content-Type: application/json
api-key: [admin key]
HTTPS is required for all service requests. If the object doesn't exist, it's created. If it already exists, it's overwritten using the new definition.
Note
Once a data source exists, you cannot change the type property on an update request. Instead, you should create a new data source using the type you want.
URI Parameters
| Parameter | Description |
|---|---|
| service name | Required. Set this to the unique, user-defined name of your search service. |
| data source name | Required on the URI if using PUT. The name must be lower case, start with a letter or number, have no slashes or dots, and be fewer than 128 characters. After you start the name with a letter or number, the rest of the name can include any letter, number and dashes, as long as the dashes aren't consecutive. |
| api-version | Required. See API versions for more versions. |
Request Headers
The following table describes the required and optional request headers.
| Fields | Description |
|---|---|
| Content-Type | Required. Set this to application/json |
| api-key | Optional if you're using Azure roles and a bearer token is provided on the request, otherwise a key is required. An api-key is a unique, system-generated string that authenticates the request to your search service. Create requests must include an api-key header set to your admin key (as opposed to a query key). See Connect to Azure AI Search using key authentication for details. |
Request Body
The body of the request contains a data source definition, which includes type of the data source, credentials to read the data, as well as an optional data change detection and data deletion detection policies that are used to efficiently identify changed or deleted data in the data source when used with a periodically scheduled indexer
The following JSON is a high-level representation of the main parts of the definition.
{
"name" : (optional on PUT; required on POST) "Name of the data source",
"description" : (optional) "Anything you want, or nothing at all",
"type" : (required) "Must be a supported data source",
"credentials" : (required) { "connectionString" : "Connection string for your data source" },
"container" : (required) { "name" : "Name of the table, collection, or blob container you wish to index" },
"dataChangeDetectionPolicy" : (optional) {See below for details },
"dataDeletionDetectionPolicy" : (optional) {See below for details },
"identity": (optional) {Sets the Resource ID of a managed identity. See below for details },
"encryptionKey":(optional) {
"keyVaultKeyName": "Name of the Azure Key Vault key used for encryption",
"keyVaultKeyVersion": "Version of the Azure Key Vault key",
"keyVaultUri": "URI of Azure Key Vault, also referred to as DNS name, that provides the key.",
"identity": "(Resource ID of a user-assigned managed identity, used for connecting to key vault)",
"accessCredentials": (Credentials for connecting to key vault. Omit if using a managed identity) {
"applicationId": "Azure AD Application ID that has access permissions to the key vault",
"applicationSecret": "Authentication key of the specified Azure AD application)"}
}
}
Request contains the following properties:
| Property | Description |
|---|---|
| name | Required. The name of the data source. A data source name must only contain lowercase letters, digits or dashes, can't start or end with dashes and is limited to 128 characters. |
| description | An optional description. |
| type | Required. Must be one of the supported data source types: adlsgen2 for Azure Data Lake Storage Gen2 azureblob for Azure Blob Storage azurefiles for Azure File Storageazuresql for Azure SQL Database azuretable for Azure Table Storagecosmosdb for the Azure Cosmos DB SQL API, MongoDB API, Gremlin API mysql for Azure Database for MySQL |
| credentials | Required. Contains a connectionString property that specifies how to connect. |
| container | Required. Specifies the container, collection, table, or view containing the data to be indexed. |
| dataChangeDetectionPolicy | Optional. Specifies the mechanism provided by the data platform for identifying changed data items. |
| dataDeletionDetectionPolicy | Optional. Identifies how the data platform deletes data. |
| encryptionKey | Optional. Used for additional encryption of data source credentials, through customer-managed encryption keys (CMK) in Azure Key Vault. Available for billable search services created on or after 2019-01-01. |
| disabled | Optional. Boolean value indicating whether the indexer is created in a disabled state, which prevents it from running immediately. False by default. |
| identity | Optional. It contains a userAssignedIdentity of type #Microsoft.Azure.Search.DataUserAssignedIdentity and specifies the user-assigned managed identity of the external resource. This property depends on credentials having the connection string in the right format (a Resource ID) for managed identity connections for each data source type. If the identity property is null, the connection to a resource ID is made using the system-managed property. If this property is assigned to the type #Microsoft.Azure.Search.DataNoneIdentity, any explicit identity that was previously specified is cleared. |
Response
For a successful request: 201 Created if a new data source was created, and 204 No Content if an existing data source was updated.
Examples
Example: Azure roles and a system-assigned managed identity
If your search service has a system-assigned managed identity and a role assignment, the data source connection can be the unique resource ID of your storage account.
{
"name": "azure-blob-ds",
"description": "a description of the blob data",
"type": "azureblob",
"subtype": null,
"credentials": {
"connectionString": "ResourceId=/subscriptions/[subscription ID]/resourceGroups/[resource group name]/providers/Microsoft.Storage/storageAccounts/[storage account name]/;"
},
"container": {
"name": "mycontainer"
},
"dataChangeDetectionPolicy": null,
"dataDeletionDetectionPolicy": null,
}
Example: Azure roles and a user-assigned managed identity (preview)
This example demonstrates an Azure AD authenticated connection for a search service that has a user-assigned managed identity.
{
"name": "azure-blob-ds",
"description": "a description of the blob data",
"type": "azureblob",
"subtype": null,
"credentials": {
"connectionString": "ResourceId=/subscriptions/[subscription ID]/resourceGroups/[resource group name]/providers/Microsoft.Storage/storageAccounts/[storage account name]/;"
},
"container": {
"name": "mycontainer"
},
"dataChangeDetectionPolicy": null,
"dataDeletionDetectionPolicy": null,
"identity": {
"@odata.type": "#Microsoft.Azure.Search.DataUserAssignedIdentity",
"userAssignedIdentity": "/subscriptions/[subscription ID]/resourceGroups/[resource group name]/providers/Microsoft.ManagedIdentity/userAssignedIdentities/[user identity name]"
}
}
Example: Azure SQL with change detection (High Watermark Change Detection Policy)
{
"name" : "asqldatasource",
"description" : "a description",
"type" : "azuresql",
"credentials" : { "connectionString" : "Server=tcp:....database.windows.net,1433;Database=...;User ID=...;Password=...;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" },
"container" : { "name" : "sometable" },
"dataChangeDetectionPolicy" : { "@odata.type" : "#Microsoft.Azure.Search.HighWaterMarkChangeDetectionPolicy", "highWaterMarkColumnName" : "RowVersion" }
}
Example: Azure SQL with change detection (SQL Integrated Change Tracking Policy)
{
"name" : "asqldatasource",
"description" : "a description",
"type" : "azuresql",
"credentials" : { "connectionString" : "Server=tcp:....database.windows.net,1433;Database=...;User ID=...;Password=...;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" },
"container" : { "name" : "sometable" },
"dataChangeDetectionPolicy" : { "@odata.type" : "#Microsoft.Azure.Search.SqlIntegratedChangeTrackingPolicy" }
}
Example: Azure SQL with change detection with deletion detection
Recall that the properties for deletion detection are "softDeleteColumnName" and "softDeleteMarkerValue".
{
"name" : "asqldatasource",
"description" : "a description",
"type" : "azuresql",
"credentials" : { "connectionString" : "Server=tcp:....database.windows.net,1433;Database=...;User ID=...;Password=...;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" },
"container" : { "name" : "sometable" },
"dataDeletionDetectionPolicy" : { "@odata.type" : "#Microsoft.Azure.Search.SoftDeleteColumnDeletionDetectionPolicy", "softDeleteColumnName" : "IsDeleted", "softDeleteMarkerValue" : "true" }
}
Example: Data source with required properties only
Optional properties related to change and deletion detection can be omitted if you only intend to use the data source for one-time copy of the data:
{
"name" : "asqldatasource",
"description" : "anything you want, or nothing at all",
"type" : "azuresql",
"credentials" : { "connectionString" : "Server=tcp:....database.windows.net,1433;Database=...;User ID=...;Password=...;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" },
"container" : { "name" : "sometable" }
}
Example: Using the unchanged or redacted credential option
If you intend to update the data source, the credentials aren't required. The values <unchanged> or <redacted> can be used in place of the connection string.
{
"name" : "adatasource",
"description": "a description",
"type": "azuresql",
"credentials": { "connectionString": "<unchanged>" },
"container" : { "name": "sometable" }
}
Example: Encryption keys
Encryption keys are customer-managed keys used for additional encryption. For more information, see Encryption using customer-managed keys in Azure Key Vault.
{
"name" : "adatasource",
"description": "a description",
"type": "azuresql",
"credentials": { "connectionString": "<unchanged>" },
"container" : { "name": "sometable" },
"encryptionKey": (optional) {
"keyVaultKeyName": "Name of the Azure Key Vault key used for encryption",
"keyVaultKeyVersion": "Version of the Azure Key Vault key",
"keyVaultUri": "URI of Azure Key Vault, also referred to as DNS name, that provides the key. An example URI might be https://my-keyvault-name.vault.azure.net",
"accessCredentials": (optional, only if not using managed identity) {
"applicationId": "Azure Active Directory Application ID that was granted access permissions to your specified Azure Key Vault",
"applicationSecret": "Authentication key of the specified Azure AD application)"}
}
}
Example: Encryption key vault connections by search services having a user-assigned managed identity
This example omits accessCredentials. For a resource that has a user-assigned managed identity assigned to it, you can specify the identity in encryptionKey and retrieve the key using that identity and Azure role assignments.
{
"name" : "adatasource",
"description": "a description",
"type": "azuresql",
"credentials": { "connectionString": "<unchanged>" },
"container" : { "name": "sometable" },
"encryptionKey": (optional) {
"keyVaultKeyName": "Name of the Azure Key Vault key used for encryption",
"keyVaultKeyVersion": "Version of the Azure Key Vault key",
"keyVaultUri": "URI of Azure Key Vault, also referred to as DNS name, that provides the key. An example URI might be https://my-keyvault-name.vault.azure.net",
"identity": {
"@odata.type": "#Microsoft.Azure.Search.DataUserAssignedIdentity",
"userAssignedIdentity": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso-rg/providers/Microsoft.ManagedIdentity/userAssignedIdentities/contoso-identity"
}
}
}
Definitions
| Link | Description |
|---|---|
| container | Specifies the container, collection, table, or view containing the data to be indexed. |
| credentials | Contains a connectionString property that specifies how an indexer connects to an Azure resource. |
| dataChangeDetectionPolicy | Specifies the mechanism provided by the data platform for identifying changed data. |
| dataDeletionDetectionPolicy | Specifies the mechanism for detecting deleted data. |
| encryptionKey | Configures a connection to Azure Key Vault for customer-managed encryption. |
container
Specifies the container, collection, table, or view containing the data to be indexed.
| Attribute | Description |
|---|---|
| name | Required. For Azure Cosmos DB, specifies the SQL API collection. For Azure Blob Storage, specifies the storage container. For Azure SQL, specifies the table or view. You can use schema-qualified names, such as [dbo].[mytable]. For Azure Table Storage, specifies the name of the table. |
| query | Optional. For Azure Cosmos DB, allows you to specify a query that flattens an arbitrary JSON document layout into a flat schema that Azure AI Search can index. For Azure Blob Storage, allows you to specify a virtual folder within the blob container. For example, for blob path mycontainer/documents/blob.pdf, documents can be used as the virtual folder. For Azure Table Storage, allows you to specify a query that filters the set of rows to be imported. For Azure SQL, query isn't supported (use views instead). |
credentials
Contains a "connectionString" property that specifies how an indexer connects to an Azure resource.
| Attribute | Description |
|---|---|
| connectionString | Required. Specifies a connection to an indexer data source. If you're updating the data source definition, the connection string isn't required. The values <unchanged> or <redacted> can be used in place of the actual connection string. For connections that are authenticated using keys or sign-in credentials, those values are visible in the connection string. The format of the connection string depends on the data source type: For Azure SQL Database, this is the usual SQL Server connection string. If you're using Azure portal to retrieve the connection string, choose the ADO.NET connection string option. For Azure Cosmos DB, the connection string must be in the following format: "AccountEndpoint=https://[your account name].documents.azure.com;AccountKey=[your account key];Database=[your database id]". All of the values are required. You can find them in the Azure portal. If you're using a managed identity to authenticate, you can omit credentials on the connection. |
For connections that are authenticated using a managed identity, the connection string specifies the Azure resource ID (see these links for connection string format: Azure Storage, Cosmos DB,SQL Database).
Role assignments scoped to the external data source determine whether the indexer can connect, and the search service must be configured to run as a trusted service in Azure Active Directory.
If the "identity" property is also specified, the connection is made using the search service user-assigned managed identity provided by the "identity" property. Otherwise, if "identity" is unspecified or null, the connection is through the system-managed identity.
dataChangeDetectionPolicy
Specifies the mechanism provided by the data platform for identifying changed data. Supported policies vary based on the data source type.
| Attribute | Description |
|---|---|
| dataChangeDetectionPolicy | Optional. Valid policies include HighWatermarkChangeDetectionPolicy or SqlIntegratedChangeDetectionPolicy. HighWatermarkChangeDetectionPolicy depends on an existing column or property that is updated in tandem with other updates (all inserts result in an update to the watermark column), and the change in value is higher. SqlIntegratedChangeDetectionPolicy is used to reference the native change detection features in SQL Server. This policy can only be used with tables; it can't be used with views. You need to enable change tracking for the table you're using before you can use this policy. See Enable and disable change tracking for instructions. |
| highWaterMarkColumnName | Required for HighWatermarkChangeDetectionPolicy. For Cosmos DB, the column must be _ts property. For Azure SQL, an indexed rowversion column is recommended. For Azure Storage, change detection is built-in using lastModified values, eliminating any need to set the dataChangeDetectionPolicy. |
dataDeletionDetectionPolicy
Specifies the mechanism provided by the data platform for identifying deleted data. Supported policies vary based on the data source type.
| Attribute | Description |
|---|---|
| dataDeletionDetectionPolicy | Optional. Valid values are SoftDeleteColumnDeletionDetectionPolicy or NativeBlobSoftDeleteDeletionDetectionPolicy (see Native blob soft delete (preview)). Currently, the only generally available policy isSoftDeleteColumnDeletionDetectionPolicy, which identifies deleted items based on the value of a 'soft delete' column or property in the data source. |
| softDeleteColumnName" | Required. Name of a column in your data source providing a value that specifies a row's deletion status. For example, you could create a column named "IsDeleted". Only columns with string, integer, or boolean values are supported. |
| softDeleteMarkerValue | Required. The value of the soft delete column. The value used as softDeleteMarkerValue must be a string, even if the corresponding column holds integers or booleans. For example, if the value that appears in your data source is 1, use "1" as the softDeleteMarkerValue. If the indexer reads this value from the soft delete column, it deletes the corresponding search document from the search index. |
encryptionKey
Configures a connection to Azure Key Vault for supplemental customer-managed encryption keys (CMK). Encryption with customer-managed keys isn't available for free services. For billable services, it's only available for search services created on or after 2019-01-01.
A connection to the key vault must be authenticated. You can use either "accessCredentials" or a managed identity for this purpose.
Managed identities can be system or user-assigned (preview). If the search service has both a system-assigned managed identity and a role assignment that grants read access to the key vault, you can omit both "identity" and "accessCredentials", and the request will authenticate using the managed identity. If the search service has user-assigned identity and role assignment, set the "identity" property to the resource ID of that identity.
| Attribute | Description |
|---|---|
| keyVaultKeyName | Required. Name of the Azure Key Vault key used for encryption. |
| keyVaultKeyVersion | Required. Version of the Azure Key Vault key. |
| keyVaultUri | Required. URI of Azure Key Vault (also referred to as DNS name) that provides the key. An example URI might be https://my-keyvault-name.vault.azure.net. |
| accessCredentials | Omit if you're using a managed identity. Otherwise, the properties of accessCredentials include applicationId (an Azure Active Directory Application ID that has access permissions to your specified Azure Key Vault), and applicationSecret (the authentication key of the specified Azure AD application). |
| identity | Optional unless you're using a user-assigned managed identity for the search service connection to Azure Key Vault. The format is "/subscriptions/[subscription ID]/resourceGroups/[resource group name]/providers/Microsoft.ManagedIdentity/userAssignedIdentities/[managed identity name]". |