Merge pull request #108918 from HeidiSteen/heidist-bugfix

[Azure Cognitive Search] What's new, service region edits

Author: PRMerger6

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

@@ -9,27 +9,27 @@ ms.author: heidist
 ms.service: cognitive-search
 ms.topic: how-to
 ms.custom: subject-moving-resources
-ms.date: 03/06/2020
+ms.date: 03/24/2020
 ---
 
 # Move your Azure Cognitive Search service to another Azure region
 
-Occasionally, customers inquire about moving an existing search service to another region. Currently, there are no built-in mechanisms or tooling to help you with that task. It remains a manual process, outlined below in this article.
+Occasionally, customers ask about moving a search service to another region. Currently, there is no built-in mechanism or tooling to help with that task, but this article can help you understand the manual steps for achieving the same outcome.
 
 > [!NOTE]
 > In the Azure portal, all services have an **Export template** command. In the case of Azure Cognitive Search, this command produces a basic definition of a service (name, location, tier, replica, and partition count), but does not recognize the content of your service, nor does it carry over keys, roles, or logs. Although the command exists, we don't recommend using it for moving a search service.
 
-## Steps for moving a service
+## Guidance for moving a service
 
-If you need to move a search service to different region, your approach should look similar to the steps below:
+1. Identify dependencies and related services to understand the full impact of relocating a service, in case you need to move more than just Azure Cognitive Search.
 
-1. Identify related services to understand the full impact of relocating a service. You might be using Azure Storage for logging, knowledge store, or as an external data source. You might be using Cognitive Services for AI enrichment. Accessing services in other regions is common, but comes with additional bandwidth charges. Cognitive Services and Azure Cognitive Search are required to be in the same region if you are using AI enrichment.
+   Azure Storage is used for logging, creating a knowledge store, and is a commonly used external data source for AI enrichment and indexing. Cognitive Services is a dependency in AI enrichment. Both Cognitive Services and your search service are required to be in the same region if you are using AI enrichment.
 
-1. Inventory your existing service for a full list of objects on the service. If you enabled logging, create and archive any reports you might need for a historical record.
+1. Create an inventory of all objects on the service so that you know what to move: indexes, synonym maps, indexers, data sources, skillsets. If you enabled logging, create and archive any reports you might need for a historical record.
 
-1. Check pricing and availability in the new region to ensure availability of Azure Cognitive Search plus any related services that you might want to create in the same region. Check for feature parity. Some preview features have restricted availability.
+1. Check pricing and availability in the new region to ensure availability of Azure Cognitive Search plus any related services in the new region. The majority of features are available in all regions, but some preview features have restricted availability.
 
-1. Create a service in the new region and republish from source code any existing indexes, indexers, data sources, skillsets, knowledge stores, and synonym maps. Service names must be unique so you cannot reuse the existing name.
+1. Create a service in the new region and republish from source code any existing indexes, synonym maps, indexers, data sources, and skillsets. Remember that service names must be unique so you cannot reuse the existing name. Check each skillset to see if connections to Cognitive Services are still valid in terms of the same-region requirement. Also, if knowledge stores are created, check the connection strings for Azure Storage if you are using a different service.
 
 1. Reload indexes and knowledge stores, if applicable. You'll either use application code to push JSON data into an index, or rerun indexers to pull documents in from external sources. 
 
@@ -41,6 +41,9 @@ If you need to move a search service to different region, your approach should l
 
 ## Next steps
 
+The following links can help you locate more information when completing the steps outlined above.
+
++ [Azure Cognitive Search pricing and regions](https://azure.microsoft.com/pricing/details/search/)
 + [Choose a tier](search-sku-tier.md)
 + [Create a search service](search-create-service-portal.md)
 + [Load search documents](search-what-is-data-import.md)

articles/search/whats-new.md

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: overview
-ms.date: 03/10/2020
+ms.date: 03/24/2020
 ---
 # What's new in Azure Cognitive Search
 
@@ -24,6 +24,8 @@ Azure Search is now renamed to **Azure Cognitive Search** to reflect the expande
 
 ### March 2020
 
++ [Native blob soft delete (preview)](search-howto-indexing-azure-blob-storage.md#incremental-indexing-and-deletion-detection) means that the Azure Blob Storage indexer in Azure Cognitive Search will recognize blobs that are in a soft deleted state, and remove the corresponding search document during indexing.
+
 + New stable [Management REST API (2020-03-13)](https://docs.microsoft.com/rest/api/searchmanagement/management-api-versions) is now available. 
 
 ### February 2020