Merge pull request #5273 from HeidiSteen/heidist-freshness

Freshness pass, #2

Author: denrea

articles/search/search-dotnet-sdk-migration-version-11.md

@@ -9,7 +9,7 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.devlang: csharp
 ms.topic: conceptual
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ms.custom:
   - devx-track-csharp
   - devx-track-dotnet

articles/search/search-how-to-alias.md

@@ -8,36 +8,54 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # Create an index alias in Azure AI Search
 
 > [!IMPORTANT]
 > Index aliases are currently in public preview and available under [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-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.
+An index alias in Azure AI Search is 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.
 
-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.
+Before using an alias, your application sends requests directly to `hotel-samples-index`.
 
-Instead of dropping and rebuilding your index, you can use index aliases. A typical workflow would be to: 
+```http
+POST /indexes/hotel-samples-index/docs/search?api-version=2025-05-01-preview
+{
+    "search": "pool spa +airport",
+    "select": "HotelId, HotelName, Category, Description",
+    "count": true
+}
+```
 
-1. Create your search index
-1. Create an alias that maps to your search index
-1. Have your application send querying/indexing requests to the alias rather than the index name
-1. When you need to make a change to your index that requires a rebuild, create a new search index 
-1. When your new index is ready to go, update the alias to map to the new index and requests will automatically be routed to the new index
+After using an alias, your application sends requests to `my-alias`, which maps to `hotel-samples-index`.
+
+```http
+POST /indexes/my-alias/docs/search?api-version=2025-05-01-preview
+{
+    "search": "pool spa +airport",
+    "select": "HotelId, HotelName, Category, Description",
+    "count": true
+}
+```
+
+## Supported scenarios
+
+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](/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).
 
 ## Create an index alias
 
 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.
 
 ### [**REST API**](#tab/rest)
 
-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.
+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.
 
 ```http
-POST /aliases?api-version=2024-05-01-preview
+POST /aliases?api-version=2025-05-01-preview
 {
     "name": "my-alias",
     "indexes": ["hotel-samples-index"]
@@ -75,12 +93,12 @@ Index aliases are also supported in the latest preview SDKs for [Java](https://c
 
 ## Send requests to an index alias
 
-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.
+Aliases can be used for all document operations including querying, indexing, suggestions, and autocomplete.
 
-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. 
+This query sends the request to `my-alias`, which is mapped to an actual index on your search service. 
 
 ```http
-POST /indexes/my-alias/docs/search?api-version=2024-05-01-preview
+POST /indexes/my-alias/docs/search?api-version=2025-05-01-preview
 {
     "search": "pool spa +airport",
     "searchMode": any,
@@ -90,29 +108,19 @@ POST /indexes/my-alias/docs/search?api-version=2024-05-01-preview
 }
 ```
 
-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).
-
-> [!NOTE]
-> 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.
-> 
-> 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.
+## Update an alias
 
-## Swap indexes
-
-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).
+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).
 
 ```http
-PUT /aliases/my-alias?api-version=2024-05-01-preview
+PUT /aliases/my-alias?api-version=2025-05-01-preview
 {
     "name": "my-alias",
     "indexes": ["hotel-samples-index2"]
 }
 ```
 
-After you make the update to the alias, requests will automatically start to be routed to the new index.
-
-> [!NOTE]
-> 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.
+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.
 
 ## See also
 

articles/search/search-howto-index-cosmosdb-gremlin.md

@@ -11,7 +11,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # Index data from Azure Cosmos DB for Apache Gremlin for queries in Azure AI Search

articles/search/search-howto-index-cosmosdb-mongodb.md

@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # Index data from Azure Cosmos DB for MongoDB for queries in Azure AI Search

articles/search/search-howto-managed-identities-data-sources.md

@@ -11,7 +11,7 @@ ms.custom:
   - ignite-2023
   - build-2024
 ms.topic: how-to
-ms.date: 11/22/2024
+ms.date: 05/29/2025
 ---
 
 # Configure a search service to connect using a managed identity in Azure AI Search

articles/search/search-howto-move-across-regions.md

@@ -11,7 +11,7 @@ ms.topic: how-to
 ms.custom:
   - subject-moving-resources
   - ignite-2023
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # Move your Azure AI Search service to another Azure region

articles/search/search-language-support.md

@@ -10,12 +10,12 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # Create an index for multiple languages in Azure AI Search
 
-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.
+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.
 
 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.
 

articles/search/search-monitor-logs-powerbi.md

@@ -9,15 +9,15 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # Visualize Azure AI Search Logs and Metrics with Power BI
 
 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.
 
 > [!NOTE]
-> 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.
+> The Power BI template currently uses a former product name, Azure Cognitive Search. The product name will be updated on the next template refresh.
 
 ## Set up logging and install the template
 

articles/search/search-query-troubleshoot-collection-filters.md

@@ -8,8 +8,8 @@ ms.author: beloh
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: conceptual
-ms.date: 12/10/2024
+ms.topic: reference
+ms.date: 05/29/2025
 ---
 # Troubleshooting OData collection filters in Azure AI Search
 

articles/search/semantic-code-migration.md

@@ -9,7 +9,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 12/10/2024
+ms.date: 05/29/2025
 ---
 
 # 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
 | stable | [2024-07-01](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2024-07-01&preserve-view=true) | No change |
 | preview | [2024-09-01-preview](/rest/api/searchservice/operation-groups?view=rest-searchservice-2024-09-01-preview&preserve-view=true) | No change |
 | 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).  |
+| 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. |
+| 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). |
 
 ## Change logs for Azure SDKs