Merge pull request #302441 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-app-configuration/feature-flag-telemetry-reference.md

@@ -50,7 +50,7 @@ When the Azure App Configuration provider libraries are used, additional propert
 - **ETag**: The current ETag for the feature flag.
 - **FeatureFlagReference**: A reference to the feature flag in the format of `<your_store_endpoint>kv/<feature_flag_key>`. When a label is present, the reference includes it as a query parameter: `<your_store_endpoint>kv/<feature_flag_key>?label=<feature_flag_label>`.
 
-The full schema can be found in the [App Configuration Feature Evaluation Event schema definition](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/AppConfigurationFeatureEvaluationEventv1.0.0.schema.json).
+The full schema can be found in the [App Configuration Feature Evaluation Event schema definition](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/AppConfigurationFeatureEvaluationEvent.v1.0.0.schema.json).
 
 ## Next steps
 

articles/migrate/concepts-vmware-agentless-migration.md

@@ -186,6 +186,9 @@ As a best practice, you should always complete the migration after the VM has mi
 ## Impact of churn
 
 We try to minimize the amount of data transfer in each replication cycle by allowing the data to fold as much as possible before we schedule the next cycle. Because agentless replication folds in data, the _churn pattern_ is more important than the _churn rate_. When a file is written again and again, the rate doesn't have much impact. However, a pattern in which every other sector is written causes high churn in the next cycle.
+If the current delta replication cycle experiences delays due to high data churn, the initiation of the subsequent cycle may be delayed. A higher volume of data to replicate for a specific disk will extend the duration required to create a recovery point. As a result, the final migration cycle will take longer, leading to an extended shutdown window for the source virtual machine (VM).
+
+In cases where the snapshot size increases(due to churn pattern) to an extent that crosses the available capacity of the datastore, there is a risk of the datastore running out of space. This can adversely affect production workloads and may render the source VM unresponsive. To mitigate this risk, it is recommended to increase the datastore size proactively. Additionally, if multiple VMs are being replicated concurrently are having disks in a datastore which has low available capacity, it is advisable to perform migrations one VM at a time to avoid resource contention.
 
 ## Management of replication