Update articles/availability-zones/migrate-search-service.md

Co-authored-by: Anastasia Harris <[email protected]>

Author: mattgotteiner

articles/availability-zones/migrate-search-service.md

@@ -42,7 +42,9 @@ If your search service was was created in a region that supports availability zo
 
 1. [Create a new search service](../search/search-create-service-portal.md) in the same region as the old search service. This region should [support availability zones on or after the current date](../search/search-performance-optimization.md#availability-zones). The [free and basic tiers do not support availability zones](../search/search-sku-tier#feature-availability-by-tier), so they should not be used.
 1. Add at [least 2 replicas to your new search service](..search/search-capacity-planning.md#add-or-reduce-replicas-and-partitions). Once the search service has at least 2 replicas, it automatically takes advantage of availability zone support.
-1. Migrate your data from your old search service to your new search service. This requires a complete rebuild of all your search indexes from your old service.
+1. Migrate your data from your old search service to your new search service by rebuilding of all your search indexes from your old service.
+
+To rebuild all of your search indexes, choose one of the following two options:
    1. You can [move individual indexes from your old search service to your new one](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/master/index-backup-restore), or you can rebuild indexes from an external data source if one is available.
 1. Redirect traffic from your old search service to your new search service. This may require updates to your application that uses the old search service.
 >[!TIP]