You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-how-to-index-markdown-blobs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.service: azure-ai-search
10
10
ms.custom:
11
11
- ignite-2024
12
12
ms.topic: how-to
13
-
ms.date: 11/20/2024
13
+
ms.date: 05/29/2025
14
14
---
15
15
16
16
# Index Markdown blobs and files in Azure AI Search
@@ -38,7 +38,7 @@ In Azure AI Search, indexers for Azure Blob Storage, Azure Files, and OneLake su
38
38
Parsing mode parameters are specified in an indexer definition when you create or update an indexer.
39
39
40
40
```http
41
-
POST https://[service name].search.windows.net/indexers?api-version=2024-11-01-preview
41
+
POST https://[service name].search.windows.net/indexers?api-version=2025-05-01-preview
42
42
Content-Type: application/json
43
43
api-key: [admin key]
44
44
@@ -155,7 +155,7 @@ An example index configuration might look something like this:
155
155
If field names and data types align, the blob indexer can infer the mapping without an explicit field mapping present in the request, so an indexer configuration corresponding to the provided index configuration might look like this:
156
156
157
157
```http
158
-
POST https://[service name].search.windows.net/indexers?api-version=2024-11-01-preview
158
+
POST https://[service name].search.windows.net/indexers?api-version=2025-05-01-preview
159
159
Content-Type: application/json
160
160
api-key: [admin key]
161
161
@@ -337,7 +337,7 @@ If you aren't utilizing field mappings, the shape of the index should reflect th
337
337
### Indexer definition for one-to-one parsing
338
338
339
339
```http
340
-
POST https://[service name].search.windows.net/indexers?api-version=2024-11-01-preview
340
+
POST https://[service name].search.windows.net/indexers?api-version=2025-05-01-preview
Copy file name to clipboardExpand all lines: articles/search/search-howto-managed-identities-sql.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.custom:
10
10
- ignite-2023
11
11
ms.service: azure-ai-search
12
12
ms.topic: how-to
13
-
ms.date: 12/10/2024
13
+
ms.date: 05/29/2025
14
14
---
15
15
16
16
# Set up an indexer connection to Azure SQL using a managed identity
@@ -90,7 +90,7 @@ Create the data source and provide either a system-assigned managed identity or
90
90
91
91
### System-assigned managed identity
92
92
93
-
The [REST API](/rest/api/searchservice/data-sources/create), Azure portal, and the [.NET SDK](/dotnet/api/azure.search.documents.indexes.models.searchindexerdatasourceconnection) support system-assigned managed identity.
93
+
The [REST API](/rest/api/searchservice/data-sources/create), Azure portal, and the Azure SDKs support system-assigned managed identity.
94
94
95
95
When you're connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide an Initial Catalog or Database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Azure SQL Database, the resource group of SQL Database, and the name of the SQL database.
96
96
@@ -115,16 +115,16 @@ api-key: [admin key]
115
115
116
116
### User-assigned managed identity (preview)
117
117
118
-
The 2021-04-30-preview and later preview REST APIs support connections based on a user-assigned managed identity. When you're connecting with a user-assigned managed identity, there are two changes to the data source definition:
118
+
Preview REST APIs support connections based on a user-assigned managed identity. When you're connecting with a user-assigned managed identity, there are two changes to the data source definition:
119
119
120
120
* First, the format of the "credentials" property is an Initial Catalog or Database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Azure SQL Database, the resource group of SQL Database, and the name of the SQL database. This is the same format as the system-assigned managed identity.
121
121
122
122
* Second, add an "identity" property that contains the collection of user-assigned managed identities. Only one user-assigned managed identity should be provided when creating the data source. Set it to type "userAssignedIdentities".
123
123
124
-
Here's an example of how to create an indexer data source object using the most recent preview API version for [Create orUpdate Data Source](/rest/api/searchservice/data-sources/create-or-update?view=rest-searchservice-2024-05-01-preview&preserve-view=true):
124
+
Here's an example of how to create an indexer data source object using the most recent preview API version for [Create orUpdate Data Source](/rest/api/searchservice/data-sources/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true):
125
125
126
126
```http
127
-
POST https://[service name].search.windows.net/datasources?api-version=2024-05-01-preview
127
+
POST https://[service name].search.windows.net/datasources?api-version=2025-05-01-preview
Copy file name to clipboardExpand all lines: articles/search/search-index-azure-sql-managed-instance-with-managed-identity.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: azure-ai-search
9
9
ms.custom:
10
10
- ignite-2023
11
11
ms.topic: conceptual
12
-
ms.date: 12/10/2024
12
+
ms.date: 05/29/2025
13
13
---
14
14
15
15
# Set up an indexer connection to Azure SQL Managed Instance using a managed identity
@@ -46,12 +46,11 @@ Follow these steps to assign the search service system managed identity permissi
46
46
47
47
:::image type="content" source="./media/search-index-azure-sql-managed-instance-with-managed-identity/sql-login.png" alt-text="Showing screenshot of the Connect to Server dialog.":::
48
48
49
-
3. From the left pane, locate the SQL database you are using as data source for indexing and right-click it. Select **New Query**.
49
+
1. From the left pane, locate the SQL database you are using as data source for indexing and right-click it. Select **New Query**.
50
50
51
51
:::image type="content" source="./media/search-index-azure-sql-managed-instance-with-managed-identity/new-sql-query.png" alt-text="Showing screenshot of new SQL query.":::
52
52
53
-
54
-
4. In the T-SQL window, copy the following commands and include the brackets around your search service name. Click on **Execute**.
53
+
1. In the T-SQL window, copy the following commands and include the brackets around your search service name. Click on **Execute**.
55
54
56
55
57
56
```sql
@@ -79,8 +78,7 @@ In this step, you'll give your Azure AI Search service permission to read data f
79
78
80
79
:::image type="content" source="./media/search-index-azure-sql-managed-instance-with-managed-identity/access-control-add-role-assignment.png" alt-text="Showing screenshot of the Access Control page." lightbox="media/search-index-azure-sql-managed-instance-with-managed-identity/access-control-add-role-assignment.png":::
81
80
82
-
83
-
4. Select **Reader** role.
81
+
1. Select **Reader** role.
84
82
1. Leave **Assign access to** as **Microsoft Entra user, group, or service principal**.
85
83
1. If you're using a system-assigned managed identity, search for your search service, then select it. If you're using a user-assigned managed identity, search for the name of the user-assigned managed identity, then select it. Select **Save**.
86
84
@@ -101,7 +99,7 @@ When you're connecting with a system-assigned managed identity, the only change
101
99
Here's an example of how to create a data source to index data from a storage account using the [Create Data Source](/rest/api/searchservice/data-sources/create) REST API and a managed identity connection string. The managed identity connection string format is the same for the REST API, .NET SDK, and the Azure portal.
102
100
103
101
```http
104
-
POST https://[service name].search.windows.net/datasources?api-version=2020-06-30
102
+
POST https://[service name].search.windows.net/datasources?api-version=2024-07-01
105
103
Content-Type: application/json
106
104
api-key: [admin key]
107
105
@@ -124,7 +122,7 @@ The index specifies the fields in a document, attributes, and other constructs t
124
122
Here's a [Create Index](/rest/api/searchservice/indexes/create) REST API call with a searchable `booktitle` field:
125
123
126
124
```http
127
-
POST https://[service name].search.windows.net/indexes?api-version=2020-06-30
125
+
POST https://[service name].search.windows.net/indexes?api-version=2024-07-01
128
126
Content-Type: application/json
129
127
api-key: [admin key]
130
128
@@ -144,7 +142,7 @@ An indexer connects a data source with a target search index, and provides a sch
144
142
Here's a [Create Indexer](/rest/api/searchservice/indexers/create) REST API call with an Azure SQL indexer definition. The indexer runs when you submit the request.
145
143
146
144
```http
147
-
POST https://[service name].search.windows.net/indexers?api-version=2020-06-30
145
+
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
0 commit comments