@@ -1,7 +1,7 @@
 ---
 ms.service: azure-ai-search
 ms.topic: include
-ms.date: 03/25/2026
+ms.date: 04/10/2026
 ---
 
 [!INCLUDE [Feature preview](../previews/preview-generic.md)]
@@ -66,9 +66,6 @@ Content-Type: application/json
         "sourceDataFields": [
           { "name": "description" },
           { "name": "category" }
-        ],
-        "searchFields": [
-          { "name": "*" }
         ]
     }
 }

@@ -22,7 +22,7 @@ For more information about the deprecation path, see the [Azure SDK lifecycle an
 
 ## Deprecated versions
 
-**2023-07-01-preview** was deprecated on April 8, 2024 and won't be supported after July 8, 2024.
+**2023-07-01-preview** was deprecated on April 8, 2024 and is no longer supported as of July 8, 2024.
 
 This was the first REST API that offered vector search support. Newer API versions have a different vector configuration. You should [migrate to a newer version](search-api-migration.md) as soon as possible.
 

@@ -103,7 +103,7 @@ To increase or decrease the capacity of your service, you have two options:
 
    This operation can take several hours to complete. It occurs in the background, so your search service remains fully operational and available for read and write operations.
 
-   You can't cancel the operation or monitor its progress. However, the following message displays while changes are underway:
+   You can't cancel the operation or monitor its progress. However, the following message displays while changes are underway.
 
    :::image type="content" source="media/search-capacity-planning/updating-message.png" alt-text="Screenshot of the Updating message in the Azure portal." border="true" lightbox="media/search-capacity-planning/updating-message.png":::
 
@@ -112,7 +112,7 @@ To increase or decrease the capacity of your service, you have two options:
 > [!NOTE]
 > The Azure portal and [Services - Update (REST API)](/rest/api/searchmanagement/services/update) support changes between Basic and Standard (S1, S2, and S3) tiers. You can upgrade or downgrade tiers, provided your current service configuration doesn't exceed the [limits of the target tier](search-limits-quotas-capacity.md). Your region also can't have [capacity constraints on the target tier](search-region-support.md).
 
-Your [pricing tier](search-sku-tier.md) determines the maximum storage of your search service. If you need more or less capacity, you can switch to a different pricing tier that accommodates your storage needs.
+Your pricing tier determines the maximum storage of your search service. If you need more or less capacity, you can switch to a different pricing tier that accommodates your storage needs.
 
 In addition to capacity, pricing tiers determine limits on indexes, indexers, and other search objects. Compare the [service limits](search-limits-quotas-capacity.md) of your current tier and your desired tier before you proceed. Generally, switching to a higher tier increases your [storage limit](search-limits-quotas-capacity.md#service-limits) and [vector limit](search-limits-quotas-capacity.md#vector-index-size-limits), increases request throughput, and decreases latency, while switching to a lower tier has the opposite effect.
 
@@ -140,7 +140,7 @@ To change your pricing tier:
 
    This operation can take several hours to complete. It occurs in the background, so your search service remains fully operational and available for read and write operations.
 
-   You can't cancel the operation or monitor its progress. However, the following message displays while changes are underway:
+   You can't cancel the operation or monitor its progress. However, the following message displays while changes are underway.
 
    :::image type="content" source="media/search-capacity-planning/updating-message.png" alt-text="Screenshot of the Updating message in the Azure portal." border="true" lightbox="media/search-capacity-planning/updating-message.png":::
 

@@ -4,7 +4,7 @@ description: Configure indexer connections to access content from other Azure re
 ms.reviewer: mcarter
 ms.service: azure-ai-search
 ms.topic: how-to
-ms.date: 03/17/2026
+ms.date: 04/10/2026
 ms.update-cycle: 180-days
 ms.custom:
   - ignite-2024
@@ -24,7 +24,7 @@ Shared private link is a premium feature billed by usage. For details, see [Azur
 
 ## Prerequisites
 
-+ [A supported Azure resource](#supported-resource-types), configured to run in a virtual network.
++ A [supported Azure resource](#supported-resource-types) configured to run in a virtual network.
 
 + An Azure AI Search service. Requirements vary by workload:
 
@@ -308,7 +308,7 @@ This would return a JSON, where the connection state shows up as "status" under
 }
 ```
 
-If the provisioning state (`properties.provisioningState`) of the resource is "Succeeded" and connection state(`properties.status`) is "Approved", it means that the shared private link resource is functional and the indexer can be configured to communicate over the private endpoint.
+If the provisioning state (`properties.provisioningState`) of the resource is "Succeeded" and connection state (`properties.status`) is "Approved", it means that the shared private link resource is functional and the indexer can be configured to communicate over the private endpoint.
 
 ## 4 - Configure the indexer to run in the private environment
 
@@ -423,9 +423,9 @@ When evaluating shared private links for your scenario, remember these constrain
 
 + Indexer execution must use the [private execution environment](search-howto-run-reset-indexers.md#indexer-execution-environment) that's specific to your search service. Private endpoint connections aren't supported from the multitenant content processing environment. The configuration setting for this requirement is covered in this article.
 
-+ Review shared private link [resource limits for each tier](search-limits-quotas-capacity.md#shared-private-link-resource-limits).
++ Shared private link [resource limits](search-limits-quotas-capacity.md#shared-private-link-resource-limits) vary by pricing tier.
 
-+ The resource type `Microsoft.CognitiveServices/accounts` for kind `AIServices` isn't currently supported. This means that shared private link for Foundry resources with this kind can't be created at this time. If you require to use an Azure OpenAI embedding model for your skill or vectorizer, and need private communication, create an Azure OpenAI resource and a shared private link with the `Microsoft.CognitiveServices/accounts` with subtype `openai_account` as a workaround.
++ When you [change your pricing tier](search-capacity-planning.md#change-your-pricing-tier), shared private link resources are evaluated against the target tier's limits. If your shared private link count exceeds the target tier's maximum, the tier change is blocked. If the tier change succeeds, existing shared private link resources aren't recreated and don't require reapproval. Private indexer connectivity continues to work after the search service returns to a "Succeeded" provisioning state and "Running" status, provided the shared private link provisioning state remains "Succeeded" and the connection status remains "Approved."
 
 ## Troubleshooting