Merge pull request #110396 from ealsur/users/ealsur/bulkv3cp

Cosmos DB - Bulk migration note

Author: PRMerger14

articles/cosmos-db/how-to-migrate-from-bulk-executor-library.md

@@ -4,7 +4,7 @@ description: Learn how to migrate your application from using the bulk executor
 author: ealsur
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 03/24/2020
+ms.date: 04/06/2020
 ms.author: maquaran
 ---
 
@@ -69,6 +69,15 @@ The `BulkOperationResponse` contains:
 1. The total of request units consumed.
 1. If there are failures, it displays a list of tuples that contain the exception and the associated item for logging and identification purpose.
 
+## Retry configuration
+
+Bulk executor library had [guidance](bulk-executor-dot-net.md#bulk-import-data-to-an-azure-cosmos-account) that mentioned to set the `MaxRetryWaitTimeInSeconds` and `MaxRetryAttemptsOnThrottledRequests` of [RetryOptions](https://docs.microsoft.com/dotnet/api/microsoft.azure.documents.client.connectionpolicy.retryoptions) to `0` to delegate control to the library.
+
+For bulk support in the .NET SDK, there is no hidden behavior. You can configure the retry options directly through the [CosmosClientOptions.MaxRetryAttemptsOnRateLimitedRequests](https://docs.microsoft.com/dotnet/api/microsoft.azure.cosmos.cosmosclientoptions.maxretryattemptsonratelimitedrequests) and [CosmosClientOptions.MaxRetryWaitTimeOnRateLimitedRequests](https://docs.microsoft.com/dotnet/api/microsoft.azure.cosmos.cosmosclientoptions.maxretrywaittimeonratelimitedrequests).
+
+> [!NOTE]
+> In cases where the provisioned request units is much lower than the expected based on the amount of data, you might want to consider setting these to high values. The bulk operation will take longer but it has a higher chance of completely succeeding due to the higher retries.
+
 ## Performance improvements
 
 As with other operations with the .NET SDK, using the stream APIs results in better performance and avoids any unnecessary serialization.