Merge pull request #176494 from timsander1/master

add note about indexing policy for V3 SDK migration

Author: PRMerger19

articles/cosmos-db/sql/migrate-dotnet-v3.md

@@ -6,7 +6,7 @@ ms.author: esarroyo
 ms.service: cosmos-db
 ms.subservice: cosmosdb-sql
 ms.topic: how-to
-ms.date: 10/04/2021
+ms.date: 10/19/2021
 ---
 
 # Migrate your application to use the Azure Cosmos DB .NET SDK v3
@@ -193,6 +193,17 @@ Some settings in `ConnectionPolicy` have been renamed or replaced:
 |`ConnectionProtocol`|Removed. Protocol is tied to the Mode, either it's Gateway (HTTPS) or Direct (TCP). Direct mode with HTTPS protocol is no longer supported on V3 SDK and the recommendation is to use TCP protocol. |
 |`MediaRequestTimeout`|Removed. Attachments are no longer supported.|
 
+### Indexing policy
+
+In the indexing policy, it is not possible to configure these properties. When not specified, these properties will now always have the following values:
+
+| **Property Name**     | **New Value (not configurable)** |
+| ----------------------- | -------------------------------- |
+| `Kind`   | `range` |
+| `dataType`    | `String` and `Number` |
+
+See [this section](how-to-manage-indexing-policy.md#indexing-policy-examples) for indexing policy examples for including and excluding paths. Due to improvements in the query engine, configuring these properties, even if using an older SDK version, has no impact on performance.
+
 ### Session token
 
 Where the v2 SDK exposed the session token of a response as `ResourceResponse.SessionToken` for cases where capturing the session token was required, because the session token is a header, the v3 SDK exposes that value in the `Headers.Session` property of any response.