Merged PR 20698: Add hydration policy not supported warning

Add hydration policy 'not supported' warning for `CF_HYDRATION_POLICY_PARTIAL`.

Author: alvinashcraft

sdk-api-src/content/cfapi/ne-cfapi-cf_hydration_policy_primary.md

@@ -6,7 +6,7 @@ helpviewer_keywords: ["CF_HYDRATION_POLICY_ALWAYS_FULL","CF_HYDRATION_POLICY_FUL
 old-location: cloudapi\cf_hydration_policy_primary.htm
 tech.root: cloudapi
 ms.assetid: 47ACA107-80AA-42B3-B583-399323E2B11C
-ms.date: 03/29/2023
+ms.date: 08/24/2023
 ms.keywords: CF_HYDRATION_POLICY_ALWAYS_FULL, CF_HYDRATION_POLICY_FULL, CF_HYDRATION_POLICY_PARTIAL, CF_HYDRATION_POLICY_PRIMARY, CF_HYDRATION_POLICY_PRIMARY enumeration, CF_HYDRATION_POLICY_PROGRESSIVE, cfapi/CF_HYDRATION_POLICY_ALWAYS_FULL, cfapi/CF_HYDRATION_POLICY_FULL, cfapi/CF_HYDRATION_POLICY_PARTIAL, cfapi/CF_HYDRATION_POLICY_PRIMARY, cfapi/CF_HYDRATION_POLICY_PROGRESSIVE, cloudApi.cf_hydration_policy_primary
 req.header: cfapi.h
 req.include-header: 
@@ -51,6 +51,9 @@ api_name:
 
 Allows a sync provider to control how placeholder files should be hydrated by the platform. This is the primary policy.
 
+> [!WARNING]
+> **CF_HYDRATION_POLICY_PARTIAL** policy is not currently supported.
+
 ## -enum-fields
 
 ### -field CF_HYDRATION_POLICY_PARTIAL:0
@@ -59,10 +62,7 @@ The same behavior as **CF_HYDRATION_POLICY_PROGRESSIVE**, except that **CF_HYDRA
 
 ### -field CF_HYDRATION_POLICY_PROGRESSIVE:1
 
-When **CF_HYDRATION_POLICY_PROGRESSIVE** is selected, the platform will allow a placeholder to be dehydrated. When the platform detects access to a dehydrated placeholder, it will complete the user IO request as soon as it determines that sufficient data is received from the sync provider. However, the platform will continue requesting the remaining content in the placeholder from the sync provider in the background until either the full content of the placeholder is available locally, or the last user handle on the placeholder is closed.
-
->[!NOTE]
->Sync providers who opt in for **CF_HYDRATION_POLICY_PROGRESSIVE** may not assume that hydration callbacks arrive sequentially from offset 0. In other words, sync providers with **CF_HYDRATION_POLICY_PROGRESSIVE** policy are expected to handle random seeks on the placeholder.
+When **CF_HYDRATION_POLICY_PROGRESSIVE** is selected, the platform will allow a placeholder to be dehydrated. When the platform detects access to a dehydrated placeholder, it will complete the user IO request as soon as it determines that sufficient data is received from the sync provider. However, the platform will continue requesting the remaining content in the placeholder from the sync provider in the background until either the full content of the placeholder is available locally, or the last user handle on the placeholder is closed. <br><br>**NOTE**<br>Sync providers who opt in for **CF_HYDRATION_POLICY_PROGRESSIVE** may not assume that hydration callbacks arrive sequentially from offset 0. In other words, sync providers with **CF_HYDRATION_POLICY_PROGRESSIVE** policy are expected to handle random seeks on the placeholder.
 
 ### -field CF_HYDRATION_POLICY_FULL:2