Merge branch 'MicrosoftDocs:main' into previewexp

Author: n0elleli

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

@@ -6,7 +6,7 @@ ms.author: esarroyo
 ms.service: cosmos-db
 ms.subservice: nosql
 ms.topic: how-to
-ms.date: 06/01/2022
+ms.date: 11/09/2022
 ms.devlang: csharp
 ---
 
@@ -84,11 +84,7 @@ The following classes have been replaced on the 3.0 SDK:
 
 * `Microsoft.Azure.Documents.UriFactory`
 
-* `Microsoft.Azure.Documents.Document`
-
-* `Microsoft.Azure.Documents.Resource`
-
-The Microsoft.Azure.Documents.UriFactory class has been replaced by the fluent design. 
+The Microsoft.Azure.Documents.UriFactory class has been replaced by the fluent design.
 
 # [.NET SDK v3](#tab/dotnet-v3)
 
@@ -112,8 +108,18 @@ await client.CreateDocumentAsync(
 
 ---
 
+* `Microsoft.Azure.Documents.Document`
+
 Because the .NET v3 SDK allows users to configure a custom serialization engine, there's no direct replacement for the `Document` type. When using Newtonsoft.Json (default serialization engine), `JObject` can be used to achieve the same functionality. When using a different serialization engine, you can use its base json document type (for example, `JsonDocument` for System.Text.Json). The recommendation is to use a C# type that reflects the schema of your items instead of relying on generic types.
 
+* `Microsoft.Azure.Documents.Resource`
+
+There is no direct replacement for `Resource`, in cases where it was used for documents, follow the guidance for `Document`.
+
+* `Microsoft.Azure.Documents.AccessCondition`
+
+`IfNoneMatch` or `IfMatch` are now available on the `Microsoft.Azure.Cosmos.ItemRequestOptions` directly.
+
 ### Changes to item ID generation
 
 Item ID is no longer auto populated in the .NET v3 SDK. Therefore, the Item ID must specifically include a generated ID. View the following example:
@@ -125,31 +131,22 @@ public Guid Id { get; set; }
 
 ### Changed default behavior for connection mode
 
-The SDK v3 now defaults to Direct + TCP connection modes compared to the previous v2 SDK, which defaulted to Gateway + HTTPS connections modes. This change provides enhanced performance and scalability.
+The SDK v3 now defaults to [Direct + TCP connection modes](sdk-connection-modes.md) compared to the previous v2 SDK, which defaulted to Gateway + HTTPS connections modes. This change provides enhanced performance and scalability.
 
 ### Changes to FeedOptions (QueryRequestOptions in v3.0 SDK)
 
 The `FeedOptions` class in SDK v2 has now been renamed to `QueryRequestOptions` in the SDK v3 and within the class, several properties have had changes in name and/or default value or been removed completely.  
 
-`FeedOptions.MaxDegreeOfParallelism` has been renamed to `QueryRequestOptions.MaxConcurrency` and default value and associated behavior remains the same, operations run client side during parallel query execution will be executed serially with no-parallelism.
-
-`FeedOptions.EnableCrossPartitionQuery` has been removed and the default behavior in SDK 3.0 is that cross-partition queries will be executed without the need to enable the property specifically.
-
-`FeedOptions.PopulateQueryMetrics` is enabled by default with the results being present in the `FeedResponse.Diagnostics` property of the response.
-
-`FeedOptions.RequestContinuation` has now been promoted to the query methods themselves.
-
-The following properties have been removed:
-
-* `FeedOptions.DisableRUPerMinuteUsage`
-
-* `FeedOptions.EnableCrossPartitionQuery`
-
-* `FeedOptions.JsonSerializerSettings`
-
-* `FeedOptions.PartitionKeyRangeId`
-
-* `FeedOptions.PopulateQueryMetrics`
+| .NET v2 SDK | .NET v3 SDK |
+|-------------|-------------|
+|`FeedOptions.MaxDegreeOfParallelism`|`QueryRequestOptions.MaxConcurrency` - Default value and associated behavior remains the same, operations run client side during parallel query execution will be executed serially with no-parallelism.|
+|`FeedOptions.PartitionKey`|`QueryRequestOptions.PartitionKey` - Behavior maintained. |
+|`FeedOptions.EnableCrossPartitionQuery`|Removed. Default behavior in SDK 3.0 is that cross-partition queries will be executed without the need to enable the property specifically. |
+|`FeedOptions.PopulateQueryMetrics`|Removed. It is now enabled by default and part of the [diagnostics](troubleshoot-dotnet-sdk.md#capture-diagnostics).|
+|`FeedOptions.RequestContinuation`|Removed. It is now promoted to the query methods themselves. |
+|`FeedOptions.JsonSerializerSettings`|Removed. Serialization can be customized through a [custom serializer](/dotnet/api/microsoft.azure.cosmos.cosmosclientoptions.serializer) or [serializer options](/dotnet/api/microsoft.azure.cosmos.cosmosclientoptions.serializeroptions).|
+|`FeedOptions.PartitionKeyRangeId`|Removed. Same outcome can be obtained from using [FeedRange](change-feed-pull-model.md#using-feedrange-for-parallelization) as input to the query method.|
+|`FeedOptions.DisableRUPerMinuteUsage`|Removed.|
 
 ### Constructing a client
 
@@ -213,7 +210,7 @@ catch (CosmosException cosmosException) {
 
 ### ConnectionPolicy
 
-Some settings in `ConnectionPolicy` have been renamed or replaced:
+Some settings in `ConnectionPolicy` have been renamed or replaced by `CosmosClientOptions`:
 
 | .NET v2 SDK | .NET v3 SDK |
 |-------------|-------------|

articles/purview/troubleshoot-policy-distribution.md

@@ -177,11 +177,11 @@ In this example, the delta pull communicates the event that the policy on the re
 
 
 ## Policy constructs
-There are 3 top-level policy constructs used within the full pull (/policyElements) and delta pull (/policyEvents) requests: PolicySet, Policy and AttributeRule.
+There are 3 top-level policy constructs used within the responses to the full pull (/policyElements) and delta pull (/policyEvents) requests: Policy, PolicySet and AttributeRule.
 
-### PolicySet
+### Policy
 
-PolicySet associates Policy to a resource scope. Purview policy decision compute starts with a list of PolicySets. PolicySet evaluation triggers evaluation of Policy referenced in the PolicySet.
+Policy specifies the decision the data source must enforce (permit vs. deny) when an Azure AD principal attempts an access via a client, provided request context attributes satisfy attribute predicates specified in the policy (for example scope, requested action, etc.). Evaluation of the Policy triggers evaluation of AttributeRules referenced in the Policy.
 
 |member|value|type|cardinality|description|
 |------|-----|----|-----------|-----------|
@@ -190,12 +190,12 @@ PolicySet associates Policy to a resource scope. Purview policy decision compute
 |kind| |string|1||
 |version|1|number|1||
 |updatedAt| |string|1|String representation of time in yyyy-MM-ddTHH:mm:ss.fffffffZ Ex: "2022-01-11T09:55:52.6472858Z"|
-|preconditionRules| |array[Object:Rule]|0..1||
-|policyRefs| |array[string]|1|List of policy IDs|
+|preconditionRules| |array[Object:Rule]|0..1|All the rules are 'anded'|
+|decisionRules| |array[Object:DecisionRule]|1||
 
-### Policy
+### PolicySet
 
-Policy specifies decision that should be emitted if the policy is applicable for the request provided request context attributes satisfy attribute predicates specified in the policy. Evaluation of policy triggers evaluation of AttributeRules referenced in the Policy.
+PolicySet associates an array of Policy IDs to a resource scope where they need to be enforced.
 
 |member|value|type|cardinality|description|
 |------|-----|----|-----------|-----------|
@@ -204,8 +204,8 @@ Policy specifies decision that should be emitted if the policy is applicable for
 |kind| |string|1||
 |version|1|number|1||
 |updatedAt| |string|1|String representation of time in yyyy-MM-ddTHH:mm:ss.fffffffZ Ex: "2022-01-11T09:55:52.6472858Z"|
-|preconditionRules| |array[Object:Rule]|0..1|All the rules are 'anded'|
-|decisionRules| |array[Object:DecisionRule]|1||
+|preconditionRules| |array[Object:Rule]|0..1||
+|policyRefs| |array[string]|1|List of policy IDs|
 
 
 ### AttributeRule