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-alias.md
+36-28Lines changed: 36 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,36 +8,54 @@ ms.service: azure-ai-search
8
8
ms.custom:
9
9
- ignite-2023
10
10
ms.topic: how-to
11
-
ms.date: 12/10/2024
11
+
ms.date: 05/29/2025
12
12
---
13
13
14
14
# Create an index alias in Azure AI Search
15
15
16
16
> [!IMPORTANT]
17
17
> Index aliases are currently in public preview and available under [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
18
18
19
-
In Azure AI Search, an index alias is a secondary name that can be used to refer to an index for querying, indexing, and other operations. You can create an alias that maps to a search index and substitute the alias name in places where you would otherwise reference an index name. An alias adds flexibility if you need to change which index your application is pointing to. Instead of updating the references in your application, you can just update the mapping for your alias.
19
+
An index alias in Azure AI Searchis an alternate name for an index. You can use the alias instead of the index name in your application, which minimizes future updates to production code. If you need to switch to a newer index, you can update the alias mapping.
20
20
21
-
The main goal of index aliases is to make it easier to manage your production indexes. For example, if you need to make a change to your index definition, such as editing a field or adding a new analyzer, you'll have to create a new search index because all search indexes are immutable. This means you either need to [drop and rebuild your index](search-howto-reindex.md) or create a new index and then migrate your application over to that index.
21
+
Before using an alias, your application sends requests directly to `hotel-samples-index`.
22
22
23
-
Instead of dropping and rebuilding your index, you can use index aliases. A typical workflow would be to:
23
+
```http
24
+
POST /indexes/hotel-samples-index/docs/search?api-version=2025-05-01-preview
You can only use an alias with document operations or to get and update an index definition.
46
+
47
+
Aliases can't be used to [delete an index](/rest/api/searchservice/indexes/delete), or [test text tokenization](/rest/api/searchservice/indexes/analyze), or referenced as the `targetIndexName` on an [indexer](/rest/api/searchservice/indexers/create-or-update).
30
48
31
49
## Create an index alias
32
50
33
51
You can create an alias using the preview REST API, the preview SDKs, or through the [Azure portal](https://portal.azure.com). An alias consists of the `name` of the alias and the name of the search index that the alias is mapped to. Only one index name can be specified in the `indexes` array.
34
52
35
53
### [**REST API**](#tab/rest)
36
54
37
-
You can use the [Create or Update Alias (REST preview)](/rest/api/searchservice/aliases/create-or-update?view=rest-searchservice-2024-05-01-preview&preserve-view=true) to create an index alias.
55
+
You can use the [Create or Update Alias (REST preview)](/rest/api/searchservice/aliases/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true) to create an index alias.
38
56
39
57
```http
40
-
POST /aliases?api-version=2024-05-01-preview
58
+
POST /aliases?api-version=2025-05-01-preview
41
59
{
42
60
"name": "my-alias",
43
61
"indexes": ["hotel-samples-index"]
@@ -75,12 +93,12 @@ Index aliases are also supported in the latest preview SDKs for [Java](https://c
75
93
76
94
## Send requests to an index alias
77
95
78
-
Once you've created your alias, you're ready to start using it. Aliases can be used for all document operations including querying, indexing, suggestions, and autocomplete.
96
+
Aliases can be used for all document operations including querying, indexing, suggestions, and autocomplete.
79
97
80
-
In the query below, instead of sending the request to `hotel-samples-index`, you can instead send the request to `my-alias` and it will be routed accordingly.
98
+
This query sends the request to `my-alias`, which is mapped to an actual index on your search service.
81
99
82
100
```http
83
-
POST /indexes/my-alias/docs/search?api-version=2024-05-01-preview
101
+
POST /indexes/my-alias/docs/search?api-version=2025-05-01-preview
84
102
{
85
103
"search": "pool spa +airport",
86
104
"searchMode": any,
@@ -90,29 +108,19 @@ POST /indexes/my-alias/docs/search?api-version=2024-05-01-preview
90
108
}
91
109
```
92
110
93
-
If you expect to make updates to a production index, specify an alias rather than the index name in your client-side application. Scenarios that require an index rebuild are outlined in [Drop and rebuild an index](search-howto-reindex.md).
94
-
95
-
> [!NOTE]
96
-
> You can only use an alias with document operations or to get and update an index definition. Aliases can't be used to delete an index, can't be used with the Analyze Text API, and can't be used as the `targetIndexName` on an indexer.
97
-
>
98
-
> An update to an alias may take up to 10 seconds to propagate through the system so you should wait at least 10 seconds before performing any operation in the index that has been mapped or recently was mapped to the alias.
111
+
## Update an alias
99
112
100
-
## Swap indexes
101
-
102
-
Now, whenever you need to update your application to point to a new index, all you need to do is update the mapping in your alias. PUT is required for updates as described in [Create or Update Alias (REST preview)](/rest/api/searchservice/aliases/create-or-update?view=rest-searchservice-2024-05-01-preview&preserve-view=true).
113
+
PUT is required for alias updates as described in [Create or Update Alias (REST preview)](/rest/api/searchservice/aliases/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true).
103
114
104
115
```http
105
-
PUT /aliases/my-alias?api-version=2024-05-01-preview
116
+
PUT /aliases/my-alias?api-version=2025-05-01-preview
106
117
{
107
118
"name": "my-alias",
108
119
"indexes": ["hotel-samples-index2"]
109
120
}
110
121
```
111
122
112
-
After you make the update to the alias, requests will automatically start to be routed to the new index.
113
-
114
-
> [!NOTE]
115
-
> An update to an alias may take up to 10 seconds to propagate through the system so you should wait at least 10 seconds before deleting the index that the alias was previously mapped to.
123
+
An update to an alias may take up to 10 seconds to propagate through the system so you should wait at least 10 seconds before deleting the index that the alias was previously mapped to.
Copy file name to clipboardExpand all lines: articles/search/search-language-support.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,12 @@ ms.service: azure-ai-search
10
10
ms.custom:
11
11
- ignite-2023
12
12
ms.topic: how-to
13
-
ms.date: 12/10/2024
13
+
ms.date: 05/29/2025
14
14
---
15
15
16
16
# Create an index for multiple languages in Azure AI Search
17
17
18
-
If you have strings in multiple languages, you can attach [language analyzers](index-add-language-analyzers.md#supported-language-analyzers) that analyze strings using linguistic rules of a specific language during indexing and query execution. With a language analyzer, you get better handling of diacritics, character variants, punctuation, and word root forms.
18
+
If you have strings in multiple languages, you can use [vector search](vector-search-overview.md) to represent multilingual content mathematically, which is the more modern approach. Alternatively, if you aren't using vectors, you can attach [language analyzers](index-add-language-analyzers.md#supported-language-analyzers) that analyze strings using linguistic rules of a specific language during indexing and query execution. With a language analyzer, you get better handling of diacritics, character variants, punctuation, and word root forms.
19
19
20
20
Azure AI Search supports Microsoft and Lucene analyzers. By default, the search engine uses Standard Lucene, which is language agnostic. If testing indicates that the default analyzer is insufficient, replace it with a language analyzer.
Copy file name to clipboardExpand all lines: articles/search/search-monitor-logs-powerbi.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,15 +9,15 @@ 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
# Visualize Azure AI Search Logs and Metrics with Power BI
16
16
17
17
Azure AI Search can send operation logs and service metrics to an Azure Storage account, which can then be visualized in Power BI. This article explains the steps and how to use a Power BI template app to visualize the data. The template covers information about queries, indexing, operations, and service metrics.
18
18
19
19
> [!NOTE]
20
-
> The Power BI template is currently using the previous product name, Azure Cognitive Search. The name change will be updated on the next template refresh.
20
+
> The Power BI template currently uses a former product name, Azure Cognitive Search. The product name will be updated on the next template refresh.
Copy file name to clipboardExpand all lines: articles/search/semantic-code-migration.md
+3-1Lines changed: 3 additions & 1 deletion
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: how-to
12
-
ms.date: 12/10/2024
12
+
ms.date: 05/29/2025
13
13
---
14
14
15
15
# Migrate semantic ranking code from previous versions
@@ -42,6 +42,8 @@ Check your code for the REST API version or SDK package version to confirm which
42
42
| stable |[2024-07-01](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2024-07-01&preserve-view=true)| No change |
43
43
| preview |[2024-09-01-preview](/rest/api/searchservice/operation-groups?view=rest-searchservice-2024-09-01-preview&preserve-view=true)| No change |
44
44
| preview |[2024-11-01-preview](/rest/api/searchservice/operation-groups?view=rest-searchservice-2024-11-01-preview&preserve-view=true)| Adds query rewrite. The `queryLanguage` property is now required if you use [query rewrite (preview)](semantic-how-to-query-rewrite.md). |
45
+
| preview |[2025-03-01-preview](/rest/api/searchservice/operation-groups?view=rest-searchservice-2025-03-01-preview&preserve-view=true)| Adds opt-in to prerelease versions of semantic models. |
46
+
| preview |[2025-05-01-preview](/rest/api/searchservice/operation-groups?view=rest-searchservice-2025-05-01-preview&preserve-view=true)| No API updates in this preview, but semantic ranking now has [better integration with scoring profiles](semantic-how-to-enable-scoring-profiles.md). |
0 commit comments