@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
   - build-2024
-ms.topic: concept-article
+ms.topic: article
 ms.date: 10/23/2025
 ms.update-cycle: 180-days
 ---

@@ -8,7 +8,7 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
+ms.topic: article
 ms.date: 10/14/2025
 ms.update-cycle: 180-days
 ---

@@ -7,7 +7,7 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
+ms.topic: article
 ms.date: 05/27/2025
 ms.update-cycle: 365-days
 ---

@@ -7,7 +7,7 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: conceptual
+ms.topic: article
 ms.date: 05/08/2025
 ms.update-cycle: 365-days
 ---

@@ -5,7 +5,7 @@ description: Demonstrates using the Bing Entity Search service in a custom skill
 author: gmndrg
 ms.author: gimondra
 ms.service: azure-ai-search
-ms.topic: conceptual
+ms.topic: article
 ms.date: 01/18/2025
 ms.update-cycle: 365-days
 ms.custom:

@@ -7,7 +7,7 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
+ms.topic: article
 ms.date: 04/14/2025
 ms.update-cycle: 365-days
 ---

@@ -5,7 +5,7 @@ description: Learn about skillsets and create a skillset in Azure AI Search usin
 author: HeidiSteen
 ms.author: heidist
 ms.service: azure-ai-search
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 10/02/2025
 ms.update-cycle: 365-days
 ms.custom:

@@ -9,7 +9,7 @@ ms.custom:
   - ignite-2023
   - build-2024
   - ignite-2024
-ms.topic: concept-article
+ms.topic: article
 ms.date: 11/04/2025
 ms.update-cycle: 365-days
 ---

@@ -8,8 +8,8 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
   - build-2024
-ms.topic: concept-article
-ms.date: 07/14/2025
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 # Skill context and input annotation language
@@ -21,14 +21,14 @@ The data working set that represents the current state of the indexer work for t
 progressively enriched with each skill iteration's output data.
 That data is internally organized in a tree-like structure that can be queried to be used as skill inputs or to be added to the index.
 The nodes in the tree can be simple values such as strings and numbers, arrays, or complex objects and even binary files.
-Even simple values can be enriched with additional structured information.
+Even simple values can be enriched with more structured information.
 For example, a string can be annotated with additional information that is stored beneath it in the enrichment tree.
 The expressions used to query that internal structure use a rich syntax that is detailed in this article.
 The enriched data structure can be [inspected from debug sessions](cognitive-search-debug-session.md).
 Expressions querying the structure can also be tested from debug sessions.
 
-Throughout the article, we'll use the following enriched data as an example.
-This data is typical of the kind of structure you would get when enriching a document using a skillset with [OCR](cognitive-search-skill-ocr.md), [key phrase extraction](cognitive-search-skill-keyphrases.md), [text translation](cognitive-search-skill-text-translation.md), [language detection](cognitive-search-skill-language-detection.md), and [entity recognition](cognitive-search-skill-entity-recognition-v3.md) skills, as well as a custom tokenizer skill.
+Throughout the article, we use the following enriched data as an example.
+This data is typical of the kind of structure you would get when enriching a document using a skillset with [OCR](cognitive-search-skill-ocr.md), [key phrase extraction](cognitive-search-skill-keyphrases.md), [text translation](cognitive-search-skill-text-translation.md), [language detection](cognitive-search-skill-language-detection.md), and [entity recognition](cognitive-search-skill-entity-recognition-v3.md) skills, plus a custom tokenizer skill.
 
 |Path|Value|
 |---|---|
@@ -77,7 +77,7 @@ This data is typical of the kind of structure you would get when enriching a doc
 
 ## Document root
 
-All the data is under one root element, for which the path is `"/document"`. The root element is the default context for skills.
+Data is under one root element and the path is `"/document"`. The root element is the default context for skills.
 
 ## Simple paths
 
@@ -106,7 +106,7 @@ Specific elements of an array can be referenced by using their numeric index lik
 
 ### Escape sequences
 
-There are several characters that have a special meaning and need to be escaped if they are to be interpreted as-is instead of a syntax element. These characters include `#`, `/`, and `~` among others.
+There are several characters that have a special meaning and need to be escaped if they're to be interpreted as-is instead of a syntax element. These characters include `#`, `/`, and `~` among others.
 
 | Escape sequence | Special meaning (usage in path syntax)  | Example |
 |---|---|
@@ -142,7 +142,7 @@ The `'#'` token expresses that the array should be treated as a single value ins
 ### Enumerating arrays in context
 
 It's often useful to process each element of an array in isolation and have a different set of skill inputs and outputs for each.
-This can be done by setting the context of the skill to an enumeration instead of the default `"/document"`.
+This best practice can be done by setting the context of the skill to an enumeration instead of the default `"/document"`.
 
 In the following example, we use one of the input expressions we used before, but with a different context that changes the resulting value.
 
@@ -152,12 +152,12 @@ In the following example, we use one of the input expressions we used before, bu
 
 For this combination of context and input, the skill gets executed once for each normalized image: once for `"/document/normalized_images/0"` and once for `"/document/normalized_images/1"`. The two input values corresponding to each skill execution are detailed in the values column.
 
-When enumerating an array in context, any outputs the skill produces will also be added to the document as enrichments of the context.
-In the above example, an output named `"out"` has its values for each execution added to the document respectively under `"/document/normalized_images/0/out"` and `"/document/normalized_images/1/out"`.
+When you enumerate an array in context, any outputs the skill produces are added to the document as enrichments of the context.
+In the previous example, an output named `"out"` has its values for each execution added to the document respectively under `"/document/normalized_images/0/out"` and `"/document/normalized_images/1/out"`.
 
 ## Literal values
 
-Skill inputs can take literal values as their inputs instead of dynamic values queried from the existing document. This can be achieved by prefixing the value with an equal sign. Values can be numbers, strings or Boolean.
+Skill inputs can take literal values as their inputs instead of dynamic values queried from the existing document. This best practice can be achieved by prefixing the value with an equal sign. Values can be numbers, strings or Boolean.
 String values can be enclosed in single `'` or double `"` quotes.
 
 |Expression|Value|

@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
   - build-2024
-ms.topic: concept-article
+ms.topic: article
 ms.date: 10/23/2025
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/12/2021
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -9,7 +9,7 @@ ms.service: azure-ai-search
 ms.custom:
   - references_regions
   - ignite-2025
-ms.topic: concept-article
+ms.topic: article
 ms.date: 11/10/2025
 ms.update-cycle: 365-days
 ---

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 09/07/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,19 +7,19 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 
 # Deprecated Cognitive Skills in Azure AI Search
 
 This document describes cognitive skills that are considered deprecated (retired). Use the following guide for the contents:
 
-* Skill Name: The name of the skill that will be deprecated; it maps to the @odata.type attribute.
-* Last available api version: The last version of the Azure AI Search public API through which skillsets containing the corresponding deprecated skill can be created/updated. Indexers with attached skillsets with these skills will continue to run even in future API versions until the "End of support" date, at which point they start failing.
+* Skill Name: The name of the skill to be deprecated; it maps to the @odata.type attribute.
+* Last available API version: The last version of the Azure AI Search public API through which skillsets containing the corresponding deprecated skill can be created/updated. Indexers with attached skillsets with these skills will continue to run even in future API versions until the "End of support" date, at which point they start failing.
 * End of support: The day after which the corresponding skill is considered unsupported and stops working. Previously created skillsets should still continue to function, but users are recommended to migrate away from a deprecated skill.
-* Recommendations: Migration path forward to use a supported skill. Users are advised to follow the recommendations to continue to receive support.
+* Recommendations: Migration path to use a supported skill. Users are advised to follow the recommendations to continue to receive support.
 
 If you're using the [Microsoft.Skills.Text.EntityRecognitionSkill](#microsoftskillstextentityrecognitionskill) (Entity Recognition cognitive skill (v2)), this article helps you upgrade your skillset to use the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md) which is generally available and introduces new features. 
 
@@ -29,7 +29,7 @@ If you're using the [Microsoft.Skills.Text.NamedEntityRecognitionSkill](#microso
 
 ## Microsoft.Skills.Text.EntityRecognitionSkill
 
-### Last available api version
+### Last available API version
 
 2021-04-30-Preview
 
@@ -357,7 +357,7 @@ To migrate to the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-se
 
 ## Microsoft.Skills.Text.SentimentSkill
 
-### Last available api version
+### Last available API version
 
 2021-04-30-Preview
 
@@ -372,20 +372,20 @@ Use [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v
 To migrate to the [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v3.md), make one or more of the following changes to your skill definition. You can update the skill definition using the [Update Skillset API](/rest/api/searchservice/skillsets/create-or-update).
 
 > [!NOTE]
-> The skill outputs for the Sentiment Skill V3 are not compatible with the index definition based on the SentimentSkill. You will have to make changes to the index definition, skillset (later skill inputs and/or knowledge store projections) and indexer output field mappings to replace the sentiment skill with the new version.
+> The skill outputs for the Sentiment Skill V3 aren't compatible with the index definition based on the SentimentSkill. You must make changes to the index definition, skillset (later skill inputs and/or knowledge store projections) and indexer output field mappings to replace the sentiment skill with the new version.
 
 1. *(Required)* Change the `@odata.type` from `"#Microsoft.Skills.Text.SentimentSkill"` to `"#Microsoft.Skills.Text.V3.SentimentSkill"`.
 
-2. *(Required)* The Sentiment Skill V3 provides a `positive`, `neutral`, and `negative` score for the overall text and the same scores for each sentence in the overall text, whereas the previous SentimentSkill only provided a single double that ranged from 0.0 (negative) to 1.0 (positive) for the overall text. You will need to update your index definition to accept the three double values in place of a single score, and make sure all of your downstream skill inputs, knowledge store projections, and output field mappings are consistent with the naming changes.
+2. *(Required)* The Sentiment Skill V3 provides a `positive`, `neutral`, and `negative` score for the overall text and the same scores for each sentence in the overall text, whereas the previous SentimentSkill only provided a single double that ranged from 0.0 (negative) to 1.0 (positive) for the overall text. You must update your index definition to accept the three double values in place of a single score, and make sure all of your downstream skill inputs, knowledge store projections, and output field mappings are consistent with the naming changes.
 
 It's recommended to replace the old SentimentSkill with the SentimentSkill V3 entirely, update your downstream skill inputs, knowledge store projections, indexer output field mappings, and index definition to match the new output format, and reset your indexer so that all of your documents have consistent sentiment results going forward.
 
 > [!NOTE]
-> If you need any additional help updating your enrichment pipeline to use the latest version of the sentiment skill or if resetting your indexer is not an option for you, please open a [new support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) where we can work with you directly.
+> If you need any more help updating your enrichment pipeline to use the latest version of the sentiment skill or if resetting your indexer isn't an option for you, open a [new support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) where we can work with you directly.
 
 ## Microsoft.Skills.Text.NamedEntityRecognitionSkill
 
-### Last available api version
+### Last available API version
 
 2017-11-11-Preview
 
@@ -446,7 +446,7 @@ To migrate to the [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-se
     }
     ```
 
-3. *(Optional)* If you don't explicitly specify the `categories`, the `EntityRecognitionSkill V3` can return different type of categories besides those that were supported by the `NamedEntityRecognitionSkill`. If this behavior is undesirable, make sure to explicitly set the `categories` parameter to `["Person", "Location", "Organization"]`.
+3. *(Optional)* If you don't explicitly specify the `categories`, the `EntityRecognitionSkill V3` can return a different type of category besides those supported by the `NamedEntityRecognitionSkill`. If this behavior is undesirable, make sure to explicitly set the `categories` parameter to `["Person", "Location", "Organization"]`.
 
     _Sample Migration Definitions_
 

@@ -7,14 +7,14 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 05/27/2025
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 
 # Document Extraction cognitive skill
 
-The **Document Extraction** skill extracts content from a file within the enrichment pipeline. By default, content extraction or retrieval is built into the indexer pipeline. However, by using the Document Extraction skill, you can control how parameters are set, and how extracted content is named in the enrichment tree.
+The **Document Extraction** skill extracts content from a file in the [enrichment pipeline](cognitive-search-concept-intro.md). By default, content extraction or retrieval is built into the enrichment pipeline. However, by using the Document Extraction skill, you can control how parameters are set, and how extracted content is named in the enrichment tree.
 
 For [vector](vector-search-overview.md) and [multimodal search](multimodal-search-overview.md), Document Extraction combined with the [Text Split skill](cognitive-search-skill-textsplit.md) is more affordable than other [data chunking approaches](vector-search-how-to-chunk-documents.md). The following tutorials demonstrate skill usage for different scenarios:
 

@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - references_regions
   - ignite-2024
-ms.topic: concept-article
+ms.topic: article
 ms.date: 11/19/2025
 ms.update-cycle: 365-days
 ---

@@ -7,8 +7,8 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 
@@ -17,7 +17,7 @@ ms.update-cycle: 365-days
 The **Entity Recognition** skill (v2) extracts entities of different types from text. This skill uses the machine learning models provided by [Text Analytics](/azure/ai-services/language-service/overview) in Foundry Tools.
 
 > [!IMPORTANT]
-> The Entity Recognition skill (v2) (**Microsoft.Skills.Text.EntityRecognitionSkill**) is now discontinued replaced by [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md). Follow the recommendations in [Deprecated skills](cognitive-search-skill-deprecated.md) to migrate to a supported skill.
+> The Entity Recognition skill (v2) (**Microsoft.Skills.Text.EntityRecognitionSkill**) is now discontinued and replaced by [Microsoft.Skills.Text.V3.EntityRecognitionSkill](cognitive-search-skill-entity-recognition-v3.md). Follow the recommendations in [Deprecated skills](cognitive-search-skill-deprecated.md) to migrate to a supported skill.
 
 > [!NOTE]
 > As you expand scope by increasing the frequency of processing, adding more documents, or adding more AI algorithms, you will need to [attach a billable Microsoft Foundry resource](cognitive-search-attach-cognitive-services.md). Charges accrue when calling APIs in Foundry Tools, and for image extraction as part of the document-cracking stage in Azure AI Search. There are no charges for text extraction from documents.

@@ -7,7 +7,7 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - build-2025
-ms.topic: concept-article
+ms.topic: article
 ms.date: 10/23/2025
 ---
 

@@ -7,7 +7,7 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
+ms.topic: article
 ms.date: 09/17/2025
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 12/09/2021
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 #	Key Phrase Extraction cognitive skill

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 12/09/2021
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 09/17/2025
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 # OCR cognitive skill

@@ -8,8 +8,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 02/22/2024
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 08/17/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 
@@ -17,7 +17,7 @@ ms.update-cycle: 365-days
 The **Sentiment** skill (v2) evaluates unstructured text along a positive-negative continuum, and for each record, returns a numeric score between 0 and 1. Scores close to 1 indicate positive sentiment, and scores close to 0 indicate negative sentiment. This skill uses the machine learning models provided by [Text Analytics](/azure/ai-services/language-service/overview) in Foundry Tools.
 
 > [!IMPORTANT]
-> The Sentiment skill (v2) (**Microsoft.Skills.Text.SentimentSkill**) is now discontinued replaced by [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v3.md). Follow the recommendations in [Deprecated Azure AI Search skills](cognitive-search-skill-deprecated.md) to migrate to a supported skill.
+> The Sentiment skill (v2) (**Microsoft.Skills.Text.SentimentSkill**) is now discontinued, replaced by [Microsoft.Skills.Text.V3.SentimentSkill](cognitive-search-skill-sentiment-v3.md). Follow the recommendations in [Deprecated Azure AI Search skills](cognitive-search-skill-deprecated.md) to migrate to a supported skill.
 
 > [!NOTE]
 > As you expand scope by increasing the frequency of processing, adding more documents, or adding more AI algorithms, you will need to [attach a billable Microsoft Foundry resource](cognitive-search-attach-cognitive-services.md). Charges accrue when calling APIs in Foundry Tools, and for image extraction as part of the document-cracking stage in Azure AI Search. There are no charges for text extraction from documents.

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 02/22/2024
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -8,8 +8,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 09/19/2022
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -7,8 +7,8 @@ ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 04/20/2023
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 

@@ -1,18 +1,18 @@
 ---
-title: Text split skill
+title: Text Split skill
 titleSuffix: Azure AI Search
 description: Break text into chunks or pages of text based on length in an AI enrichment pipeline in Azure AI Search.
 author: gmndrg
 ms.author: gimondra
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: concept-article
-ms.date: 09/19/2025
+ms.topic: article
+ms.date: 01/07/2026
 ms.update-cycle: 365-days
 ---
 
-# Text split cognitive skill
+# Text Split cognitive skill
 
 > [!IMPORTANT] 
 > Some parameters are in public preview under [Supplemental Terms of Use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). The [preview REST API](/rest/api/searchservice/index-preview) supports these parameters.

@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - build-2024
   - references_regions
-ms.topic: concept-article
+ms.topic: article
 ms.date: 10/23/2025
 ---
 

@@ -159,7 +159,7 @@ If you're using Newtonsoft.Json for JSON serialization, you can pass in global n
 
 ## Inside v11
 
-Each version of an Azure AI Search client library targets a corresponding version of the REST API. The REST API is considered foundational to the service, with individual SDKs wrapping a version of the REST API. As a .NET developer, it can be helpful to review the more verbose [REST API documentation](/rest/api/searchservice/) for more in depth coverage of specific objects or operations. Version 11 targets the [2020-06-30 search service specification](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/search/data-plane/Azure.Search/stable/2020-06-30). 
+Each version of an Azure AI Search client library targets a corresponding version of the REST API. The REST API is considered foundational to the service, with individual SDKs wrapping a version of the REST API. As a .NET developer, it can be helpful to review the more verbose [REST API documentation](/rest/api/searchservice/) for more in depth coverage of specific objects or operations. Version 11 targets the [2020-06-30 search service specification](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/search/data-plane/Search/stable/2020-06-30). 
 
 Version 11.0 fully supports the following objects and operations: