diff --git a/windows/client-management/change-history-for-mdm-documentation.md b/windows/client-management/change-history-for-mdm-documentation.md
index 899c2dc399..80c06690e1 100644
--- a/windows/client-management/change-history-for-mdm-documentation.md
+++ b/windows/client-management/change-history-for-mdm-documentation.md
@@ -3,7 +3,7 @@ title: Change history for MDM documentation
 description: This article lists new and updated articles for Mobile Device Management.
 author: vinaypamnani-msft
 ms.author: vinpa
-ms.reviewer: 
+ms.reviewer:
 manager: aaroncz
 ms.topic: article
 ms.prod: windows-client
@@ -46,7 +46,7 @@ As of November 2020 This page will no longer be updated. This article lists new
 
 |New or updated article | Description|
 |--- | ---|
-|[Policy CSP - System](mdm/policy-csp-system.md)|Added the following new policy settings:<br>  - System/AllowDesktopAnalyticsProcessing <br>- System/AllowMicrosoftManagedDesktopProcessing <br> - System/AllowUpdateComplianceProcessing<br> - System/AllowWUfBCloudProcessing <br> <br><br>Updated the following policy setting:<br>-  <a href="mdm/policy-csp-system.md#system-allowcommercialdatapipeline" id="system-allowcommercialdatapipeline">System/AllowCommercialDataPipeline</a> <br>|
+|[Policy CSP - System](mdm/policy-csp-system.md)|Added the following new policy settings:<br>  - System/AllowDesktopAnalyticsProcessing <br>- System/AllowMicrosoftManagedDesktopProcessing <br> - System/AllowUpdateComplianceProcessing<br> - System/AllowWUfBCloudProcessing <br> <br><br>Updated the following policy setting:<br>-  <a href="mdm/policy-csp-system.md#allowcommercialdatapipeline" id="system-allowcommercialdatapipeline">System/AllowCommercialDataPipeline</a> <br>|
 
 ## June 2020
 
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md
index 5b7486628f..dccc4df62a 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md
@@ -1,7 +1,7 @@
 ---
 title: Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite
 description: Learn the policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite.
-ms.reviewer: 
+ms.reviewer:
 manager: aaroncz
 ms.author: vinpa
 ms.topic: article
@@ -48,8 +48,8 @@ ms.date: 09/17/2019
 - [Settings/AllowDateTime](policy-csp-settings.md#settings-allowdatetime)
 - [Settings/AllowVPN](policy-csp-settings.md#settings-allowvpn)
 - [Speech/AllowSpeechModelUpdate](policy-csp-speech.md#speech-allowspeechmodelupdate)
-- [System/AllowLocation](policy-csp-system.md#system-allowlocation)
-- [System/AllowTelemetry](policy-csp-system.md#system-allowtelemetry)
+- [System/AllowLocation](policy-csp-system.md#allowlocation)
+- [System/AllowTelemetry](policy-csp-system.md#allowtelemetry)
 - [Update/AllowAutoUpdate](policy-csp-update.md#update-allowautoupdate)
 - [Update/AllowUpdateService](policy-csp-update.md#update-allowupdateservice)
 - [Update/RequireDeferUpgrade](policy-csp-update.md#update-requiredeferupgrade)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md
index eebc6a88cf..78c0ec3a24 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md
@@ -1,7 +1,7 @@
 ---
 title: Policies in Policy CSP supported by HoloLens (1st gen) Development Edition
 description: Learn about the policies in Policy CSP supported by HoloLens (1st gen) Development Edition.
-ms.reviewer: 
+ms.reviewer:
 manager: aaroncz
 ms.author: vinpa
 ms.topic: article
@@ -46,8 +46,8 @@ ms.date: 07/18/2019
 - [Settings/AllowDateTime](policy-csp-settings.md#settings-allowdatetime)
 - [Settings/AllowVPN](policy-csp-settings.md#settings-allowvpn)
 - [Speech/AllowSpeechModelUpdate](policy-csp-speech.md#speech-allowspeechmodelupdate)
-- [System/AllowTelemetry](policy-csp-system.md#system-allowtelemetry)
-- [System/AllowLocation](policy-csp-system.md#system-allowlocation)
+- [System/AllowTelemetry](policy-csp-system.md#allowtelemetry)
+- [System/AllowLocation](policy-csp-system.md#allowlocation)
 - [Update/AllowAutoUpdate](policy-csp-update.md#update-allowautoupdate)
 - [Update/AllowUpdateService](policy-csp-update.md#update-allowupdateservice)
 - [Update/RequireUpdateApproval](policy-csp-update.md#update-requireupdateapproval)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
index 62ead15ae0..082b79a3aa 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
@@ -1,7 +1,7 @@
 ---
 title: Policies in Policy CSP supported by HoloLens 2
 description: Learn about the policies in Policy CSP supported by HoloLens 2.
-ms.reviewer: 
+ms.reviewer:
 manager: aaroncz
 ms.author: vinpa
 ms.topic: article
@@ -104,10 +104,10 @@ ms.date: 08/01/2022
 - [Storage/ConfigStorageSenseCloudContentDehydrationThreshold](policy-csp-storage.md#storage-configstoragesensecloudcontentdehydrationthreshold) <sup>12</sup>
 - [Storage/ConfigStorageSenseDownloadsCleanupThreshold](policy-csp-storage.md#storage-configstoragesensedownloadscleanupthreshold) <sup>12</sup>
 - [Storage/ConfigStorageSenseGlobalCadence](policy-csp-storage.md#storage-configstoragesenseglobalcadence) <sup>12</sup>
-- [System/AllowCommercialDataPipeline](policy-csp-system.md#system-allowcommercialdatapipeline)
-- [System/AllowLocation](policy-csp-system.md#system-allowlocation)
-- [System/AllowStorageCard](policy-csp-system.md#system-allowstoragecard)
-- [System/AllowTelemetry](policy-csp-system.md#system-allowtelemetry)
+- [System/AllowCommercialDataPipeline](policy-csp-system.md#allowcommercialdatapipeline)
+- [System/AllowLocation](policy-csp-system.md#allowlocation)
+- [System/AllowStorageCard](policy-csp-system.md#allowstoragecard)
+- [System/AllowTelemetry](policy-csp-system.md#allowtelemetry)
 - [TimeLanguageSettings/ConfigureTimeZone](./policy-csp-timelanguagesettings.md#timelanguagesettings-configuretimezone) <sup>9</sup>
 - [Update/ActiveHoursEnd](./policy-csp-update.md#update-activehoursend) <sup>9</sup>
 - [Update/ActiveHoursMaxRange](./policy-csp-update.md#update-activehoursmaxrange) <sup>9</sup>
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md
index bcc22cc6cb..a1cd81ffcb 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md
@@ -64,9 +64,9 @@ ms.date: 07/22/2020
 - [DeliveryOptimization/DOPercentageMaxDownloadBandwidth](policy-csp-deliveryoptimization.md#deliveryoptimization-dopercentagemaxdownloadbandwidth)
 - [Desktop/PreventUserRedirectionOfProfileFolders](policy-csp-desktop.md#desktop-preventuserredirectionofprofilefolders)
 - [RestrictedGroups/ConfigureGroupMembership](policy-csp-restrictedgroups.md#restrictedgroups-configuregroupmembership)
-- [System/AllowLocation](policy-csp-system.md#system-allowlocation)
-- [System/AllowStorageCard](policy-csp-system.md#system-allowstoragecard)
-- [System/AllowTelemetry](policy-csp-system.md#system-allowtelemetry)
+- [System/AllowLocation](policy-csp-system.md#allowlocation)
+- [System/AllowStorageCard](policy-csp-system.md#allowstoragecard)
+- [System/AllowTelemetry](policy-csp-system.md#allowtelemetry)
 - [TextInput/AllowIMELogging](policy-csp-textinput.md#textinput-allowimelogging)
 - [TextInput/AllowIMENetworkAccess](policy-csp-textinput.md#textinput-allowimenetworkaccess)
 - [TextInput/AllowInputPanel](policy-csp-textinput.md#textinput-allowinputpanel)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md b/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md
index 601ad0b197..ee156ca4b2 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md
@@ -1,7 +1,7 @@
 ---
 title: Policies in Policy CSP that can be set using Exchange Active Sync (EAS)
 description: Learn about the policies in Policy CSP that can be set using Exchange Active Sync (EAS).
-ms.reviewer: 
+ms.reviewer:
 manager: aaroncz
 ms.author: vinpa
 ms.topic: article
@@ -30,8 +30,8 @@ ms.date: 07/18/2019
 - [DeviceLock/PreventLockScreenSlideShow](policy-csp-devicelock.md#devicelock-preventlockscreenslideshow)
 - [Search/AllowSearchToUseLocation](policy-csp-search.md#search-allowsearchtouselocation)
 - [Security/RequireDeviceEncryption](policy-csp-security.md#security-requiredeviceencryption)
-- [System/AllowStorageCard](policy-csp-system.md#system-allowstoragecard)
-- [System/TelemetryProxy](policy-csp-system.md#system-telemetryproxy)
+- [System/AllowStorageCard](policy-csp-system.md#allowstoragecard)
+- [System/TelemetryProxy](policy-csp-system.md#telemetryproxy)
 - [Wifi/AllowInternetSharing](policy-csp-wifi.md#wifi-allowinternetsharing)
 - [Wifi/AllowWiFi](policy-csp-wifi.md#wifi-allowwifi)
 
diff --git a/windows/client-management/mdm/policy-csp-admx-datacollection.md b/windows/client-management/mdm/policy-csp-admx-datacollection.md
index 657cdef18f..d658533761 100644
--- a/windows/client-management/mdm/policy-csp-admx-datacollection.md
+++ b/windows/client-management/mdm/policy-csp-admx-datacollection.md
@@ -1,92 +1,95 @@
 ---
-title: Policy CSP - ADMX_DataCollection
-description: Learn about the Policy CSP - ADMX_DataCollection.
+title: ADMX_DataCollection Policy CSP
+description: Learn more about the ADMX_DataCollection Area in Policy CSP.
+author: vinaypamnani-msft
+manager: aaroncz
 ms.author: vinpa
+ms.date: 01/09/2023
 ms.localizationpriority: medium
-ms.topic: article
 ms.prod: windows-client
 ms.technology: itpro-manage
-author: vinaypamnani-msft
-ms.date: 12/01/2020
-ms.reviewer: 
-manager: aaroncz
+ms.topic: reference
 ---
 
+<!-- Auto-Generated CSP Document -->
+
+<!-- ADMX_DataCollection-Begin -->
 # Policy CSP - ADMX_DataCollection
 
-<hr/>
-
-<!--Policies-->
-## ADMX_DataCollection policies
-
 > [!TIP]
-> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
+> This CSP contains ADMX-backed policies which require a special SyncML format to enable or disable. You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
 >
-> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
->
-> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it.  For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
 
-<dl>
-  <dd>
-    <a href="#admx-datacollection-commercialidpolicy">ADMX_DataCollection/CommercialIdPolicy</a>
-  </dd>
-</dl>
+<!-- ADMX_DataCollection-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- ADMX_DataCollection-Editable-End -->
 
+<!-- CommercialIdPolicy-Begin -->
+## CommercialIdPolicy
 
-<hr/>
+<!-- CommercialIdPolicy-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- CommercialIdPolicy-Applicability-End -->
 
-<!--Policy-->
-<a href="" id="admx-datacollection-commercialidpolicy"></a>**ADMX_DataCollection/CommercialIdPolicy**
+<!-- CommercialIdPolicy-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/ADMX_DataCollection/CommercialIdPolicy
+```
+<!-- CommercialIdPolicy-OmaUri-End -->
 
-<!--SupportedSKUs-->
+<!-- CommercialIdPolicy-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting defines the identifier used to uniquely associate this device's diagnostic data data as belonging to a given organization. If your organization is participating in a program that requires this device to be identified as belonging to your organization then use this setting to provide that identification. The value for this setting will be provided by Microsoft as part of the onboarding process for the program.
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Business|Yes|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+- If you disable or do not configure this policy setting, then Microsoft will not be able to use this identifier to associate this machine and its diagnostic data data with your organization.
+<!-- CommercialIdPolicy-Description-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- CommercialIdPolicy-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+> [!IMPORTANT]
+> Starting with the January 2023 preview cumulative update, this policy is no longer supported to configure the processor option. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
+<!-- CommercialIdPolicy-Editable-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- CommercialIdPolicy-DFProperties-Begin -->
+**Description framework properties**:
 
-> [!div class = "checklist"]
-> * Device
+| Property name | Property value |
+|:--|:--|
+| Format | chr (string) |
+| Access Type | Add, Delete, Get, Replace |
+<!-- CommercialIdPolicy-DFProperties-End -->
 
-<hr/>
+<!-- CommercialIdPolicy-AdmxBacked-Begin -->
+> [!TIP]
+> This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
 
-<!--/Scope-->
-<!--Description-->
-This policy setting defines the identifier used to uniquely associate this device’s telemetry data as belonging to a given organization.
+**ADMX mapping**:
 
-If your organization is participating in a program that requires this device to be identified as belonging to your organization, then use this setting to provide that identification. The value for this setting will be provided by Microsoft as part of the onboarding process for the program.
+| Name | Value |
+|:--|:--|
+| Name | CommercialIdPolicy |
+| Friendly Name | Configure the Commercial ID |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- CommercialIdPolicy-AdmxBacked-End -->
 
-If you disable or don't configure this policy setting, then Microsoft won't be able to use this identifier to associate this machine and its telemetry data with your organization.
+<!-- CommercialIdPolicy-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- CommercialIdPolicy-Examples-End -->
 
-<!--/Description-->
+<!-- CommercialIdPolicy-End -->
 
+<!-- ADMX_DataCollection-CspMoreInfo-Begin -->
+<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
+<!-- ADMX_DataCollection-CspMoreInfo-End -->
 
-<!--ADMXBacked-->
-ADMX Info:
--   GP Friendly name: *Configure the Commercial ID*
--   GP name: *CommercialIdPolicy*
--   GP path: *Windows Components\Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- ADMX_DataCollection-End -->
 
-<!--/ADMXBacked-->
-<!--/Policy-->
-<hr/>
+## Related articles
 
-> [!NOTE]
-> These policies are for upcoming release.
-
-<!--/Policies-->
-
-## Related topics
-
-[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
+[Policy configuration service provider](policy-configuration-service-provider.md)
diff --git a/windows/client-management/mdm/policy-csp-system.md b/windows/client-management/mdm/policy-csp-system.md
index e26bcb675c..3475130df0 100644
--- a/windows/client-management/mdm/policy-csp-system.md
+++ b/windows/client-management/mdm/policy-csp-system.md
@@ -1,1615 +1,2159 @@
 ---
-title: Policy CSP - System
-description: Learn policy settings that determine whether users can access the Insider build controls in the advanced options for Windows Update.
+title: System Policy CSP
+description: Learn more about the System Area in Policy CSP.
+author: vinaypamnani-msft
+manager: aaroncz
 ms.author: vinpa
-ms.topic: article
+ms.date: 01/09/2023
+ms.localizationpriority: medium
 ms.prod: windows-client
 ms.technology: itpro-manage
-author: vinaypamnani-msft
-ms.localizationpriority: medium
-ms.date: 08/26/2021
-ms.reviewer: 
-manager: aaroncz
+ms.topic: reference
 ---
 
+<!-- Auto-Generated CSP Document -->
+
+<!-- System-Begin -->
 # Policy CSP - System
 
-<hr/>
+> [!TIP]
+> This CSP contains ADMX-backed policies which require a special SyncML format to enable or disable. You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
+>
+> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it.  For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
 
-<!--Policies-->
-## System policies
+<!-- System-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- System-Editable-End -->
 
-<dl>
-  <dd>
-    <a href="#system-allowbuildpreview">System/AllowBuildPreview</a>
-  </dd>
-  <dd>
-    <a href="#system-allowcommercialdatapipeline">System/AllowCommercialDataPipeline</a>
-  </dd>
-  <dd>
-    <a href="#system-allowdesktopanalyticsprocessing">System/AllowDesktopAnalyticsProcessing </a>
-  </dd>
-  <dd>
-    <a href="#system-allowdevicenameindiagnosticdata">System/AllowDeviceNameInDiagnosticData</a>
-  </dd>
-  <dd>
-    <a href="#system-allowembeddedmode">System/AllowEmbeddedMode</a>
-  </dd>
-  <dd>
-    <a href="#system-allowexperimentation">System/AllowExperimentation</a>
-  </dd>
-  <dd>
-    <a href="#system-allowfontproviders">System/AllowFontProviders</a>
-  </dd>
-  <dd>
-    <a href="#system-allowlocation">System/AllowLocation</a>
-  </dd>
-  <dd>
-    <a href="#system-allowmicrosoftmanageddesktopprocessing">System/AllowMicrosoftManagedDesktopProcessing</a>
-  </dd>
-  <dd>
-    <a href="#system-allowstoragecard">System/AllowStorageCard</a>
-  </dd>
-  <dd>
-    <a href="#system-allowtelemetry">System/AllowTelemetry</a>
-  </dd>
-  <dd>
-    <a href="#system-allowupdatecomplianceprocessing">System/AllowUpdateComplianceProcessing</a>
-  </dd>
-  <dd>
-    <a href="#system-allowusertoresetphone">System/AllowUserToResetPhone</a>
-  </dd>
- <dd>
-    <a href="#system-allowwufbcloudprocessing">System/AllowWUfBCloudProcessing</a>
-  </dd>
-  <dd>
-    <a href="#system-bootstartdriverinitialization">System/BootStartDriverInitialization</a>
-  </dd>
-  <dd>
-    <a href="#system-configuremicrosoft365uploadendpoint">System/ConfigureMicrosoft365UploadEndpoint</a>
-  </dd>
-  <dd>
-    <a href="#system-configuretelemetryoptinchangenotification">System/ConfigureTelemetryOptInChangeNotification</a>
-  </dd>
-  <dd>
-    <a href="#system-configuretelemetryoptinsettingsux">System/ConfigureTelemetryOptInSettingsUx</a>
-  </dd>
-  <dd>
-    <a href="#system-disabledevicedelete">System/DisableDeviceDelete</a>
-  </dd>
-  <dd>
-    <a href="#system-disablediagnosticdataviewer">System/DisableDiagnosticDataViewer</a>
-  </dd>
-  <dd>
-    <a href="#system-disableenterpriseauthproxy">System/DisableEnterpriseAuthProxy</a>
-  </dd>
-  <dd>
-    <a href="#system-disableonedrivefilesync">System/DisableOneDriveFileSync</a>
-  </dd>
-  <dd>
-    <a href="#system-disablesystemrestore">System/DisableSystemRestore</a>
-  </dd>
-  <dd>
-    <a href="#system-feedbackhubalwayssavediagnosticslocally">System/FeedbackHubAlwaysSaveDiagnosticsLocally</a>
-  </dd>
-  <dd>
-    <a href="#system-limitdiagnosticlogcollection">System/LimitDiagnosticLogCollection</a>
-  </dd>
-  <dd>
-    <a href="#system-limitdumpcollection">System/LimitDumpCollection</a>
-  </dd>
-  <dd>
-    <a href="#system-limitenhanceddiagnosticdatawindowsanalytics">System/LimitEnhancedDiagnosticDataWindowsAnalytics</a>
-  </dd>
-  <dd>
-    <a href="#system-telemetryproxy">System/TelemetryProxy</a>
-  </dd>
-  <dd>
-    <a href="#system-turnofffilehistory">System/TurnOffFileHistory</a>
-  </dd>
-</dl>
+<!-- AllowBuildPreview-Begin -->
+## AllowBuildPreview
 
+<!-- AllowBuildPreview-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1507 [10.0.10240] and later |
+<!-- AllowBuildPreview-Applicability-End -->
 
-<hr/>
+<!-- AllowBuildPreview-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowBuildPreview
+```
+<!-- AllowBuildPreview-OmaUri-End -->
 
-<!--Policy-->
-<a href="" id="system-allowbuildpreview"></a>**System/AllowBuildPreview**
+<!-- AllowBuildPreview-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting determines whether users can get preview builds of Windows, by configuring controls in Settings > Update and security > Windows Insider Program.
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+- If you enable or do not configure this policy setting, users can download and install preview builds of Windows by configuring Windows Insider Program settings.
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+- If you disable this policy setting, Windows Insider Program settings will be unavailable to users through the Settings app.
 
-<!--/SupportedSKUs-->
-<hr/>
+This policy is only supported up to Windows 10, Version 1703. Please use 'Manage preview builds' under 'Windows Update for Business' for newer Windows 10 versions.
+<!-- AllowBuildPreview-Description-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowBuildPreview-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowBuildPreview-Editable-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- AllowBuildPreview-DFProperties-Begin -->
+**Description framework properties**:
 
-<hr/>
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 2 |
+<!-- AllowBuildPreview-DFProperties-End -->
 
-<!--/Scope-->
-<!--Description-->
+<!-- AllowBuildPreview-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 | Not allowed. The item "Get Insider builds" is unavailable, users are unable to make their devices available for preview software. |
+| 1 | Allowed. Users can make their devices available for downloading and installing preview software. |
+| 2 (Default) | Not configured. Users can make their devices available for downloading and installing preview software. |
+<!-- AllowBuildPreview-AllowedValues-End -->
+
+<!-- AllowBuildPreview-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | AllowBuildPreview |
+| Friendly Name | Toggle user control over Insider builds |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\PreviewBuilds |
+| Registry Value Name | AllowBuildPreview |
+| ADMX File Name | AllowBuildPreview.admx |
+<!-- AllowBuildPreview-GpMapping-End -->
+
+<!-- AllowBuildPreview-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowBuildPreview-Examples-End -->
+
+<!-- AllowBuildPreview-End -->
+
+<!-- AllowCommercialDataPipeline-Begin -->
+## AllowCommercialDataPipeline
+
+<!-- AllowCommercialDataPipeline-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1903 [10.0.18362] and later |
+<!-- AllowCommercialDataPipeline-Applicability-End -->
+
+<!-- AllowCommercialDataPipeline-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline
+```
+<!-- AllowCommercialDataPipeline-OmaUri-End -->
+
+<!-- AllowCommercialDataPipeline-Description-Begin -->
+<!-- Description-Source-ADMX -->
+AllowCommercialDataPipeline configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at <https://go.microsoft.com/fwlink/?linkid=2185086>.
+To enable this behavior:
+
+1. Enable this policy setting
+2. Join an Azure Active Directory account to the device
+
+Windows diagnostic data is collected when the Allow Telemetry policy setting is set to value 1 - Required or above. Configuring this setting does not change the Windows diagnostic data collection level set for the device
+- If you disable or do not configure this setting, Microsoft will be the controller of the Windows diagnostic data collected from the device and processed in accordance with Microsoft's privacy statement at <https://go.microsoft.com/fwlink/?LinkId=521839> unless you have enabled policies like 'Allow Update Compliance Processing' or 'Allow Desktop Analytics Processing".
+See the documentation at <https://go.microsoft.com/fwlink/?linkid=2011107> for information on this and other policies that will result in Microsoft being the processor of Windows diagnostic data.
+<!-- AllowCommercialDataPipeline-Description-End -->
+
+<!-- AllowCommercialDataPipeline-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
 > [!NOTE]
-> This policy setting applies only to devices running Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education.
+> Configuring this setting doesn't affect the operation of optional analytics processor services like Desktop Analytics and Windows Update for Business reports.
 
-This policy setting determines whether users can access the Insider build controls in the Advanced Options for Windows Update. These controls are located under "Get Insider builds," and enable users to make their devices available for downloading and installing Windows preview software.
+> [!IMPORTANT]
+> Starting with the January 2023 preview cumulative update, this policy is no longer supported to configure the processor option. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
+<!-- AllowCommercialDataPipeline-Editable-End -->
 
-If you enable or don't configure this policy setting, users can download and install Windows preview software on their devices. If you disable this policy setting, the item "Get Insider builds" will be unavailable.
+<!-- AllowCommercialDataPipeline-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Toggle user control over Insider builds*
--   GP name: *AllowBuildPreview*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *AllowBuildPreview.admx*
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowCommercialDataPipeline-DFProperties-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- AllowCommercialDataPipeline-AllowedValues-Begin -->
+**Allowed values**:
 
--   0 – Not allowed. The item "Get Insider builds" is unavailable, users are unable to make their devices available for preview software.
--   1 – Allowed. Users can make their devices available for downloading and installing preview software.
--   2 (default) – Not configured. Users can make their devices available for downloading and installing preview software.
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Enabled. |
+<!-- AllowCommercialDataPipeline-AllowedValues-End -->
 
-<!--/SupportedValues-->
-<!--/Policy-->
+<!-- AllowCommercialDataPipeline-GpMapping-Begin -->
+**Group policy mapping**:
 
-<hr/>
+| Name | Value |
+|:--|:--|
+| Name | AllowCommercialDataPipeline |
+| Friendly Name | Allow commercial data pipeline |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- AllowCommercialDataPipeline-GpMapping-End -->
 
-<!--Policy-->
-<a href="" id="system-allowcommercialdatapipeline"></a>**System/AllowCommercialDataPipeline**
+<!-- AllowCommercialDataPipeline-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowCommercialDataPipeline-Examples-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowCommercialDataPipeline-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowDesktopAnalyticsProcessing-Begin -->
+## AllowDesktopAnalyticsProcessing
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- AllowDesktopAnalyticsProcessing-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763.1217] and later <br> :heavy_check_mark: Windows 10, version 1903 [10.0.18362.836] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- AllowDesktopAnalyticsProcessing-Applicability-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowDesktopAnalyticsProcessing-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowDesktopAnalyticsProcessing
+```
+<!-- AllowDesktopAnalyticsProcessing-OmaUri-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- AllowDesktopAnalyticsProcessing-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID, enables organizations to configure the device so that Microsoft is the processor for Windows diagnostic data collected from the device, subject to the Product Terms at <https://go.microsoft.com/fwlink/?linkid=2185086>.
+To enable this behavior:
 
-<hr/>
+1. Enable this policy setting
+2. Join an Azure Active Directory account to the device
 
-<!--/Scope-->
-<!--Description-->
-This policy setting configures an Azure Active Directory-joined device, so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the [Product Terms](https://www.microsoft.com/licensing/terms/productoffering).
-
-To enable this behavior, you must complete two steps:
-
- 1. Enable this policy setting.
- 2. Join an Azure Active Directory account to the device.
-
-Windows diagnostic data is collected when the Allow Telemetry policy setting is set to 1 – **Required (Basic)** or above.
-
-If you disable or don't configure this setting, Microsoft will be the controller of the Windows diagnostic data collected from the device and processed in accordance with Microsoft’s [privacy statement](https://go.microsoft.com/fwlink/?LinkId=521839) unless you have enabled policies like Allow Update Compliance Processing or Allow Desktop Analytics Processing.
-
-Configuring this setting doesn't change the Windows diagnostic data collection level set for the device or the operation of optional analytics processor services like Desktop Analytics and Windows Update for Business reports.
-
-See the documentation at [ConfigureWDD](https://aka.ms/ConfigureWDD) for information on this and other policies that will result in Microsoft being the processor of Windows diagnostic data.
-
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Allow commercial data pipeline*
--   GP name: *AllowCommercialDataPipeline*
--   GP element: *AllowCommercialDataPipeline*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
-
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
-
--   0 (default) - Disabled.
--   1 - Enabled.
-
-<!--/SupportedValues-->
-<!--Example-->
-
-<!--/Example-->
-<!--Validation-->
-
-<!--/Validation-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-allowdesktopanalyticsprocessing"></a>**System/AllowDesktopAnalyticsProcessing**
-
-<!--/Scope-->
-<!--Description-->
-
-This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID policy settings, enables organizations to configure the device so that Microsoft is the processor for Windows diagnostic data collected from the device, subject to the [Product Terms](https://www.microsoft.com/licensing/terms/productoffering).
-
-To enable this behavior, you must complete three steps:
-
- 1. Enable this policy setting.
- 2. Set **AllowTelemetry** to 1 – **Required (Basic)** or above.
- 3. Set the Configure the Commercial ID setting for your Desktop Analytics workspace.
-
-This setting has no effect on devices, unless they're properly enrolled in Desktop Analytics.
+3. Set Allow Telemetry to value 1 - Required, or higher
+4. Set the Configure the Commercial ID setting for your Desktop Analytics workspace
 
 When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
+This setting has no effect on devices unless they are properly enrolled in Desktop Analytics.
+- If you disable this policy setting, devices will not appear in Desktop Analytics.
+<!-- AllowDesktopAnalyticsProcessing-Description-End -->
 
-If you disable or don't configure this policy setting, devices won't appear in Desktop Analytics.
+<!-- AllowDesktopAnalyticsProcessing-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+> [!IMPORTANT]
+> Starting with the January 2023 preview cumulative update, this policy is no longer supported to configure the processor option. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
+<!-- AllowDesktopAnalyticsProcessing-Editable-End -->
 
-The following list shows the supported values:
+<!-- AllowDesktopAnalyticsProcessing-DFProperties-Begin -->
+**Description framework properties**:
 
--   0 (default) – Disabled.
--   2 – Allowed.
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowDesktopAnalyticsProcessing-DFProperties-End -->
 
+<!-- AllowDesktopAnalyticsProcessing-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/Policy-->
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 2 | Allowed. |
+<!-- AllowDesktopAnalyticsProcessing-AllowedValues-End -->
 
-<hr/>
+<!-- AllowDesktopAnalyticsProcessing-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--Policy-->
-<a href="" id="system-allowdevicenameindiagnosticdata"></a>**System/AllowDeviceNameInDiagnosticData**
+| Name | Value |
+|:--|:--|
+| Name | AllowDesktopAnalyticsProcessing |
+| Friendly Name | Allow Desktop Analytics Processing |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- AllowDesktopAnalyticsProcessing-GpMapping-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowDesktopAnalyticsProcessing-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowDesktopAnalyticsProcessing-Examples-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowDesktopAnalyticsProcessing-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- AllowDeviceNameInDiagnosticData-Begin -->
+## AllowDeviceNameInDiagnosticData
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowDeviceNameInDiagnosticData-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763] and later |
+<!-- AllowDeviceNameInDiagnosticData-Applicability-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- AllowDeviceNameInDiagnosticData-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowDeviceNameInDiagnosticData
+```
+<!-- AllowDeviceNameInDiagnosticData-OmaUri-End -->
 
-<hr/>
+<!-- AllowDeviceNameInDiagnosticData-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy allows the device name to be sent to Microsoft as part of Windows diagnostic data.
 
-<!--/Scope-->
-<!--Description-->
-This policy allows the device name to be sent to Microsoft as part of Windows diagnostic data. If you disable or don't configure this policy setting, then device name won't be sent to Microsoft as part of Windows diagnostic data.
+- If you disable or do not configure this policy setting, then device name will not be sent to Microsoft as part of Windows diagnostic data.
+<!-- AllowDeviceNameInDiagnosticData-Description-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Allow device name to be sent in Windows diagnostic data*
--   GP name: *AllowDeviceNameInDiagnosticData*
--   GP element: *AllowDeviceNameInDiagnosticData*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- AllowDeviceNameInDiagnosticData-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowDeviceNameInDiagnosticData-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- AllowDeviceNameInDiagnosticData-DFProperties-Begin -->
+**Description framework properties**:
 
--   0 (default) – Disabled.
--   1 – Allowed.
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowDeviceNameInDiagnosticData-DFProperties-End -->
 
-<!--/SupportedValues-->
-<!--Example-->
+<!-- AllowDeviceNameInDiagnosticData-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/Example-->
-<!--Validation-->
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Allowed. |
+<!-- AllowDeviceNameInDiagnosticData-AllowedValues-End -->
 
-<!--/Validation-->
-<!--/Policy-->
+<!-- AllowDeviceNameInDiagnosticData-GpMapping-Begin -->
+**Group policy mapping**:
 
-<hr/>
+| Name | Value |
+|:--|:--|
+| Name | AllowDeviceNameInDiagnosticData |
+| Friendly Name | Allow device name to be sent in Windows diagnostic data |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- AllowDeviceNameInDiagnosticData-GpMapping-End -->
 
-<!--Policy-->
-<a href="" id="system-allowembeddedmode"></a>**System/AllowEmbeddedMode**
+<!-- AllowDeviceNameInDiagnosticData-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowDeviceNameInDiagnosticData-Examples-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowDeviceNameInDiagnosticData-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowEmbeddedMode-Begin -->
+## AllowEmbeddedMode
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- AllowEmbeddedMode-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1607 [10.0.14393] and later |
+<!-- AllowEmbeddedMode-Applicability-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowEmbeddedMode-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowEmbeddedMode
+```
+<!-- AllowEmbeddedMode-OmaUri-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- AllowEmbeddedMode-Description-Begin -->
+<!-- Description-Source-DDF -->
+Specifies whether set general purpose device to be in embedded mode. Most restricted value is 0.
+<!-- AllowEmbeddedMode-Description-End -->
 
-<hr/>
+<!-- AllowEmbeddedMode-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowEmbeddedMode-Editable-End -->
 
-<!--/Scope-->
-<!--Description-->
-Specifies whether set general purpose device to be in embedded mode.
+<!-- AllowEmbeddedMode-DFProperties-Begin -->
+**Description framework properties**:
 
-Most restricted value is 0.
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowEmbeddedMode-DFProperties-End -->
 
-<!--/Description-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- AllowEmbeddedMode-AllowedValues-Begin -->
+**Allowed values**:
 
--   0 (default) – Not allowed.
--   1 – Allowed.
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Not allowed. |
+| 1 | Allowed. |
+<!-- AllowEmbeddedMode-AllowedValues-End -->
 
-<!--/SupportedValues-->
-<!--/Policy-->
+<!-- AllowEmbeddedMode-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowEmbeddedMode-Examples-End -->
 
-<hr/>
+<!-- AllowEmbeddedMode-End -->
 
-<!--Policy-->
-<a href="" id="system-allowexperimentation"></a>**System/AllowExperimentation**
+<!-- AllowExperimentation-Begin -->
+## AllowExperimentation
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowExperimentation-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1607 [10.0.14393] and later |
+<!-- AllowExperimentation-Applicability-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowExperimentation-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowExperimentation
+```
+<!-- AllowExperimentation-OmaUri-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
+<!-- AllowExperimentation-Description-Begin -->
+<!-- Description-Source-DDF -->
 > [!NOTE]
-> This policy isn't supported in Windows 10, version 1607.
+> This policy is not supported in Windows 10, version 1607. This policy setting determines the level that Microsoft can experiment with the product to study user preferences or device behavior. Most restricted value is 0.
+<!-- AllowExperimentation-Description-End -->
 
-This policy setting determines the level that Microsoft can experiment with the product to study user preferences or device behavior.
+<!-- AllowExperimentation-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowExperimentation-Editable-End -->
 
-Most restricted value is 0.
+<!-- AllowExperimentation-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/Description-->
-<!--SupportedValues-->
-The following list shows the supported values:
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 1 |
+<!-- AllowExperimentation-DFProperties-End -->
 
--   0 – Disabled.
--   1 (default) – Permits Microsoft to configure device settings only.
--   2 – Allows Microsoft to conduct full experimentation.
+<!-- AllowExperimentation-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/SupportedValues-->
-<!--/Policy-->
+| Value | Description |
+|:--|:--|
+| 0 | Disabled. |
+| 1 (Default) | Permits Microsoft to configure device settings only. |
+| 2 | Allows Microsoft to conduct full experimentation. |
+<!-- AllowExperimentation-AllowedValues-End -->
 
-<hr/>
+<!-- AllowExperimentation-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowExperimentation-Examples-End -->
 
-<!--Policy-->
-<a href="" id="system-allowfontproviders"></a>**System/AllowFontProviders**
+<!-- AllowExperimentation-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowFontProviders-Begin -->
+## AllowFontProviders
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowFontProviders-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
+<!-- AllowFontProviders-Applicability-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- AllowFontProviders-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowFontProviders
+```
+<!-- AllowFontProviders-OmaUri-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowFontProviders-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting determines whether Windows is allowed to download fonts and font catalog data from an online font provider.
 
-> [!div class = "checklist"]
-> * Device
+- If you enable this policy setting, Windows periodically queries an online font provider to determine whether a new font catalog is available. Windows may also download font data if needed to format or render text.
 
-<hr/>
+- If you disable this policy setting, Windows does not connect to an online font provider and only enumerates locally-installed fonts.
 
-<!--/Scope-->
-<!--Description-->
-Boolean policy setting that determines whether Windows is allowed to download fonts and font catalog data from an online font provider. If you enable this setting, Windows periodically queries an online font provider to determine whether a new font catalog is available. Windows may also download font data if needed to format or render text. If you disable this policy setting, Windows doesn't connect to an online font provider and only enumerates locally installed fonts.
+- If you do not configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
+<!-- AllowFontProviders-Description-End -->
 
+<!-- AllowFontProviders-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
 This MDM setting corresponds to the EnableFontProviders Group Policy setting. If both the Group Policy and the MDM settings are configured, the group policy setting takes precedence. If neither is configured, the behavior depends on a DisableFontProviders registry value. In server editions, this registry value is set to 1 by default, so the default behavior is false (disabled). In all other editions, the registry value isn't set by default, so the default behavior is true (enabled).
 
 This setting is used by lower-level components for text display and fond handling and hasn't direct effect on web browsers, which may download web fonts used in web content.
 
 > [!NOTE]
 > Reboot is required after setting the policy; alternatively you can stop and restart the FontCache service.
+<!-- AllowFontProviders-Editable-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Enable Font Providers*
--   GP name: *EnableFontProviders*
--   GP path: *Network/Fonts*
--   GP ADMX file name: *GroupPolicy.admx*
+<!-- AllowFontProviders-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 1 |
+<!-- AllowFontProviders-DFProperties-End -->
 
--   0 - false - No traffic to fs.microsoft.com, and only locally installed fonts are available.
--   1 - true (default) - There may be network traffic to fs.microsoft.com, and downloadable fonts are available to apps that support them.
+<!-- AllowFontProviders-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/SupportedValues-->
-<!--Validation-->
-To verify if System/AllowFontProviders is set to true:
+| Value | Description |
+|:--|:--|
+| 0 | Not allowed. No traffic to fs.microsoft.com and only locally installed fonts are available. |
+| 1 (Default) | Allowed. There may be network traffic to fs.microsoft.com and downloadable fonts are available to apps that support them. |
+<!-- AllowFontProviders-AllowedValues-End -->
 
--  After a client machine is rebooted, check whether there's any network traffic from client machine to fs.microsoft.com.
+<!-- AllowFontProviders-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--/Validation-->
-<!--/Policy-->
+| Name | Value |
+|:--|:--|
+| Name | EnableFontProviders |
+| Friendly Name | Enable Font Providers |
+| Location | Computer Configuration |
+| Path | Network > Fonts |
+| Registry Key Name | Software\Policies\Microsoft\Windows\System |
+| Registry Value Name | EnableFontProviders |
+| ADMX File Name | GroupPolicy.admx |
+<!-- AllowFontProviders-GpMapping-End -->
 
-<hr/>
+<!-- AllowFontProviders-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowFontProviders-Examples-End -->
 
-<!--Policy-->
-<a href="" id="system-allowlocation"></a>**System/AllowLocation**
+<!-- AllowFontProviders-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowLocation-Begin -->
+## AllowLocation
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowLocation-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1507 [10.0.10240] and later |
+<!-- AllowLocation-Applicability-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- AllowLocation-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowLocation
+```
+<!-- AllowLocation-OmaUri-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowLocation-Description-Begin -->
+<!-- Description-Source-DDF -->
+Specifies whether to allow app access to the Location service. Most restricted value is 0. While the policy is set to 0 (Force Location Off) or 2 (Force Location On), any Location service call from an app would trigger the value set by this policy. When switching the policy back from 0 (Force Location Off) or 2 (Force Location On) to 1 (User Control), the app reverts to its original Location service setting. For example, an app's original Location setting is Off. The administrator then sets the AllowLocation policy to 2 (Force Location On. ) The Location service starts working for that app, overriding the original setting. Later, if the administrator switches the AllowLocation policy back to 1 (User Control), the app will revert to using its original setting of Off.
+<!-- AllowLocation-Description-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- AllowLocation-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowLocation-Editable-End -->
 
-<hr/>
+<!-- AllowLocation-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/Scope-->
-<!--Description-->
-Specifies whether to allow app access to the Location service.
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 1 |
+<!-- AllowLocation-DFProperties-End -->
 
-Most restricted value is 0.
+<!-- AllowLocation-AllowedValues-Begin -->
+**Allowed values**:
 
-While the policy is set to 0 (Force Location Off) or 2 (Force Location On), any Location service call from an app would trigger the value set by this policy.
+| Value | Description |
+|:--|:--|
+| 0 | Force Location Off. All Location Privacy settings are toggled off and grayed out. Users cannot change the settings, and no apps are allowed access to the Location service, including Cortana and Search. |
+| 1 (Default) | Location service is allowed. The user has control and can change Location Privacy settings on or off. |
+| 2 | Force Location On. All Location Privacy settings are toggled on and grayed out. Users cannot change the settings and all consent permissions will be automatically suppressed. |
+<!-- AllowLocation-AllowedValues-End -->
 
-When switching the policy back from 0 (Force Location Off) or 2 (Force Location On) to 1 (User Control), the app reverts to its original Location service setting.
+<!-- AllowLocation-GpMapping-Begin -->
+**Group policy mapping**:
 
-For example, an app's original Location setting is Off. The administrator then sets the **AllowLocation** policy to 2 (Force Location On.) The Location service starts working for that app, overriding the original setting. Later, if the administrator switches the **AllowLocation** policy back to 1 (User Control), the app will revert to using its original setting of Off.
+| Name | Value |
+|:--|:--|
+| Name | DisableLocation_2 |
+| Friendly Name | Turn off location |
+| Location | Computer Configuration |
+| Path | Windows Components > Location and Sensors |
+| Registry Key Name | Software\Policies\Microsoft\Windows\LocationAndSensors |
+| Registry Value Name | DisableLocation |
+| ADMX File Name | Sensors.admx |
+<!-- AllowLocation-GpMapping-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Turn off location*
--   GP name: *DisableLocation_2*
--   GP path: *Windows Components/Location and Sensors*
--   GP ADMX file name: *Sensors.admx*
+<!-- AllowLocation-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowLocation-Examples-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- AllowLocation-End -->
 
--   0 – Force Location Off. All Location Privacy settings are toggled off and grayed out. Users can't change the settings, and no apps are allowed access to the Location service, including Cortana and Search.
--   1 (default) – Location service is allowed. The user has control and can change Location Privacy settings on or off.
--   2 – Force Location On. All Location Privacy settings are toggled on and grayed out. Users can't change the settings and all consent permissions will be automatically suppressed.
+<!-- AllowMicrosoftManagedDesktopProcessing-Begin -->
+## AllowMicrosoftManagedDesktopProcessing
 
-<!--/SupportedValues-->
-<!--/Policy-->
-<hr/>
+<!-- AllowMicrosoftManagedDesktopProcessing-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763.1217] and later <br> :heavy_check_mark: Windows 10, version 1903 [10.0.18362.836] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- AllowMicrosoftManagedDesktopProcessing-Applicability-End -->
 
-<!--Policy-->
-<a href="" id="system-allowmicrosoftmanageddesktopprocessing"></a>**System/AllowMicrosoftManagedDesktopProcessing**
+<!-- AllowMicrosoftManagedDesktopProcessing-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowMicrosoftManagedDesktopProcessing
+```
+<!-- AllowMicrosoftManagedDesktopProcessing-OmaUri-End -->
 
-<!--/Scope-->
-<!--Description-->
+<!-- AllowMicrosoftManagedDesktopProcessing-Description-Begin -->
+<!-- Description-Source-DDF -->
+This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows.
+This policy setting configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at <https://go.microsoft.com/fwlink/?linkid=2185086>.
+For customers who enroll into the Microsoft Managed Desktop service, enabling this policy is required to allow Microsoft to process data for operational and analytic needs. See <https://go.microsoft.com/fwlink/?linkid=2184944> for more information.
+hen these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
+This setting has no effect on devices unless they are properly enrolled in Microsoft Managed Desktop.
+- If you disable this policy setting, devices may not appear in Microsoft Managed Desktop.
+<!-- AllowMicrosoftManagedDesktopProcessing-Description-End -->
 
-This policy setting configures an Azure Active Directory-joined device so that Microsoft is the processor of the Windows diagnostic data.
+<!-- AllowMicrosoftManagedDesktopProcessing-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+> [!IMPORTANT]
+> Starting with the January 2023 preview cumulative update, this policy is no longer supported to configure the processor option. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
+<!-- AllowMicrosoftManagedDesktopProcessing-Editable-End -->
 
-For customers who enroll into the Microsoft Managed Desktop service, this policy will be enabled by default to allow Microsoft to process data for operational and analytic needs. For more information, see [Privacy and personal data](/microsoft-365/managed-desktop/service-description/privacy-personal-data).
+<!-- AllowMicrosoftManagedDesktopProcessing-DFProperties-Begin -->
+**Description framework properties**:
 
-This setting has no effect on devices, unless they're properly enrolled in Microsoft Managed Desktop.
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowMicrosoftManagedDesktopProcessing-DFProperties-End -->
+
+<!-- AllowMicrosoftManagedDesktopProcessing-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 32 | Allowed. |
+<!-- AllowMicrosoftManagedDesktopProcessing-AllowedValues-End -->
+
+<!-- AllowMicrosoftManagedDesktopProcessing-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowMicrosoftManagedDesktopProcessing-Examples-End -->
+
+<!-- AllowMicrosoftManagedDesktopProcessing-End -->
+
+<!-- AllowStorageCard-Begin -->
+## AllowStorageCard
+
+<!-- AllowStorageCard-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1507 [10.0.10240] and later |
+<!-- AllowStorageCard-Applicability-End -->
+
+<!-- AllowStorageCard-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowStorageCard
+```
+<!-- AllowStorageCard-OmaUri-End -->
+
+<!-- AllowStorageCard-Description-Begin -->
+<!-- Description-Source-DDF -->
+Controls whether the user is allowed to use the storage card for device storage. This setting prevents programmatic access to the storage card. Most restricted value is 0.
+<!-- AllowStorageCard-Description-End -->
+
+<!-- AllowStorageCard-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowStorageCard-Editable-End -->
+
+<!-- AllowStorageCard-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 1 |
+<!-- AllowStorageCard-DFProperties-End -->
+
+<!-- AllowStorageCard-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 | SD card use is not allowed and USB drives are disabled. This setting does not prevent programmatic access to the storage card. |
+| 1 (Default) | Allow a storage card. |
+<!-- AllowStorageCard-AllowedValues-End -->
+
+<!-- AllowStorageCard-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowStorageCard-Examples-End -->
+
+<!-- AllowStorageCard-End -->
+
+<!-- AllowTelemetry-Begin -->
+## AllowTelemetry
+
+<!-- AllowTelemetry-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :heavy_check_mark: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1507 [10.0.10240] and later |
+<!-- AllowTelemetry-Applicability-End -->
+
+<!-- AllowTelemetry-OmaUri-Begin -->
+```User
+./User/Vendor/MSFT/Policy/Config/System/AllowTelemetry
+```
+
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowTelemetry
+```
+<!-- AllowTelemetry-OmaUri-End -->
+
+<!-- AllowTelemetry-Description-Begin -->
+<!-- Description-Source-ADMX -->
+By configuring this policy setting you can adjust what diagnostic data is collected from Windows. This policy setting also restricts the user from increasing the amount of diagnostic data collection via the Settings app. The diagnostic data collected under this policy impacts the operating system and apps that are considered part of Windows and does not apply to any additional apps installed by your organization.
+
+- Diagnostic data off (not recommended). Using this value, no diagnostic data is sent from the device. This value is only supported on Enterprise, Education, and Server editions.
+- Send required diagnostic data. This is the minimum diagnostic data necessary to keep Windows secure, up to date, and performing as expected. Using this value disables the "Optional diagnostic data" control in the Settings app.
+- Send optional diagnostic data. Additional diagnostic data is collected that helps us to detect, diagnose and fix issues, as well as make product improvements. Required diagnostic data will always be included when you choose to send optional diagnostic data. Optional diagnostic data can also include diagnostic log files and crash dumps. Use the "Limit Dump Collection" and the "Limit Diagnostic Log Collection" policies for more granular control of what optional diagnostic data is sent.
+
+- If you disable or do not configure this policy setting, the device will send required diagnostic data and the end user can choose whether to send optional diagnostic data from the Settings app.
+
+**Note**:
+The "Configure diagnostic data opt-in settings user interface" group policy can be used to prevent end users from changing their data collection settings.
+<!-- AllowTelemetry-Description-End -->
+
+<!-- AllowTelemetry-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowTelemetry-Editable-End -->
+
+<!-- AllowTelemetry-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 1 |
+<!-- AllowTelemetry-DFProperties-End -->
+
+<!-- AllowTelemetry-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 | Security. Information that is required to help keep Windows more secure, including data about the Connected User Experience and Telemetry component settings, the Malicious Software Removal Tool, and Windows Defender. <br>Note: This value is only applicable to Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile Enterprise, Windows 10 IoT Core (IoT Core), and Windows Server 2016. Using this setting on other devices is equivalent to setting the value of 1. |
+| 1 (Default) | Basic. Basic device info, including: quality-related data, app compatibility, app usage data, and data from the Security level. |
+| 3 | Full. All data necessary to identify and help to fix problems, plus data from the Security, Basic, and Enhanced levels. |
+<!-- AllowTelemetry-AllowedValues-End -->
+
+<!-- AllowTelemetry-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | AllowTelemetry |
+| Friendly Name | Allow Diagnostic Data |
+| Location | Computer and User Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- AllowTelemetry-GpMapping-End -->
+
+<!-- AllowTelemetry-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowTelemetry-Examples-End -->
+
+<!-- AllowTelemetry-End -->
+
+<!-- AllowUpdateComplianceProcessing-Begin -->
+## AllowUpdateComplianceProcessing
+
+<!-- AllowUpdateComplianceProcessing-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763.1217] and later <br> :heavy_check_mark: Windows 10, version 1903 [10.0.18362.836] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- AllowUpdateComplianceProcessing-Applicability-End -->
+
+<!-- AllowUpdateComplianceProcessing-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowUpdateComplianceProcessing
+```
+<!-- AllowUpdateComplianceProcessing-OmaUri-End -->
+
+<!-- AllowUpdateComplianceProcessing-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID, enables organizations to configure the device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at <https://go.microsoft.com/fwlink/?linkid=2185086>.
+To enable this behavior:
+
+1. Enable this policy setting
+2. Join an Azure Active Directory account to the device
+
+3. Set Allow Telemetry to value 1 - Required, or higher
+4. Set the Configure the Commercial ID setting for your Update Compliance workspace
 
 When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
+- If you disable or do not configure this policy setting, devices will not appear in Update Compliance.
+<!-- AllowUpdateComplianceProcessing-Description-End -->
 
-If you disable this policy setting, devices may not appear in Microsoft Managed Desktop.
+<!-- AllowUpdateComplianceProcessing-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+> [!IMPORTANT]
+> Starting with the January 2023 preview cumulative update, this policy is no longer supported to configure the processor option. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
+<!-- AllowUpdateComplianceProcessing-Editable-End -->
 
->[!IMPORTANT]
-> You should not disable or make changes to this policy as that will severely impact the ability of Microsoft Managed Desktop to manage the devices.
+<!-- AllowUpdateComplianceProcessing-DFProperties-Begin -->
+**Description framework properties**:
 
-<hr/>
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowUpdateComplianceProcessing-DFProperties-End -->
 
-<!--Policy-->
-<a href="" id="system-allowstoragecard"></a>**System/AllowStorageCard**
+<!-- AllowUpdateComplianceProcessing-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 16 | Enabled. |
+<!-- AllowUpdateComplianceProcessing-AllowedValues-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowUpdateComplianceProcessing-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--/SupportedSKUs-->
-<hr/>
+| Name | Value |
+|:--|:--|
+| Name | AllowUpdateComplianceProcessing |
+| Friendly Name | Allow Update Compliance Processing |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- AllowUpdateComplianceProcessing-GpMapping-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowUpdateComplianceProcessing-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowUpdateComplianceProcessing-Examples-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- AllowUpdateComplianceProcessing-End -->
 
-<hr/>
+<!-- AllowUserToResetPhone-Begin -->
+## AllowUserToResetPhone
 
-<!--/Scope-->
-<!--Description-->
-Controls whether the user is allowed to use the storage card for device storage. This setting prevents programmatic access to the storage card.
+<!-- AllowUserToResetPhone-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1507 [10.0.10240] and later |
+<!-- AllowUserToResetPhone-Applicability-End -->
 
-Most restricted value is 0.
+<!-- AllowUserToResetPhone-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowUserToResetPhone
+```
+<!-- AllowUserToResetPhone-OmaUri-End -->
 
-<!--/Description-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- AllowUserToResetPhone-Description-Begin -->
+<!-- Description-Source-DDF -->
+Specifies whether to allow the user to factory reset the device by using control panel and hardware key combination. Most restricted value is 0. Tip, This policy is also applicable to Windows 10 and not exclusive to phone.
+<!-- AllowUserToResetPhone-Description-End -->
 
--   0 – SD card use isn't allowed, and USB drives are disabled. This setting doesn't prevent programmatic access to the storage card.
--   1 (default) – Allow a storage card.
+<!-- AllowUserToResetPhone-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- AllowUserToResetPhone-Editable-End -->
 
-<!--/SupportedValues-->
-<!--/Policy-->
+<!-- AllowUserToResetPhone-DFProperties-Begin -->
+**Description framework properties**:
 
-<hr/>
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 1 |
+<!-- AllowUserToResetPhone-DFProperties-End -->
 
-<!--Policy-->
-<a href="" id="system-allowtelemetry"></a>**System/AllowTelemetry**
+<!-- AllowUserToResetPhone-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+| Value | Description |
+|:--|:--|
+| 0 | Not allowed. |
+| 1 (Default) | Allowed to reset to factory default settings. |
+<!-- AllowUserToResetPhone-AllowedValues-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowUserToResetPhone-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowUserToResetPhone-Examples-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- AllowUserToResetPhone-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- AllowWUfBCloudProcessing-Begin -->
+## AllowWUfBCloudProcessing
 
-> [!div class = "checklist"]
-> * User
-> * Device
+<!-- AllowWUfBCloudProcessing-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763.1217] and later <br> :heavy_check_mark: Windows 10, version 1903 [10.0.18362.836] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- AllowWUfBCloudProcessing-Applicability-End -->
 
-<hr/>
+<!-- AllowWUfBCloudProcessing-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/AllowWUfBCloudProcessing
+```
+<!-- AllowWUfBCloudProcessing-OmaUri-End -->
 
-<!--/Scope-->
-<!--Description-->
-Allows the device to send diagnostic and usage telemetry data, such as Watson.
+<!-- AllowWUfBCloudProcessing-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at <https://go.microsoft.com/fwlink/?linkid=2185086>.
+To enable this behavior:
 
-For more information about diagnostic data, including what is and what isn't collected by Windows, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization).
+1. Enable this policy setting
+2. Join an Azure Active Directory account to the device
 
-The following list shows the supported values for Windows 8.1:
--   0 - Not allowed.
--   1 – Allowed, except for Secondary Data Requests.
--   2 (default) – Allowed.
-
-In Windows 10, you can configure this policy setting to decide what level of diagnostic data to send to Microsoft.
-
-The following list shows the supported values for Windows 10 version 1809 and older, choose the value that is applicable to your OS version (older OS values are displayed in the brackets):
-
-- 0 – **Off (Security)** This value turns Windows diagnostic data off.
-
-    > [!NOTE]
-    > This value is only applicable to Windows 10 Enterprise, Windows 10 Education, Windows 10 IoT Core (IoT Core), HoloLens 2, and Windows Server 2016 (and later versions). Using this setting on other devices editions of Windows is equivalent to setting the value of 1.
-
-- 1 – **Required (Basic)** Sends basic device info, including quality-related data, app compatibility, and other similar data to keep the device secure and up-to-date.
-
-- 2 – (**Enhanced**) Sends the same data as a value of 1, plus extra insights, including how Windows apps are used, how they perform, and advanced reliability data, such as limited crash dumps.
-
-    > [!NOTE]
-    > **Enhanced** is no longer an option for Windows Holographic, version 21H1.
-
-- 3 – **Optional (Full)** Sends the same data as a value of 2, plus extra data necessary to identify and fix problems with devices such as enhanced error logs.
-
-Most restrictive value is 0.
-
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Allow Telemetry*
--   GP name: *AllowTelemetry*
--   GP element: *AllowTelemetry*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
-
-<!--/ADMXMapped-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-allowupdatecomplianceprocessing"></a>**System/AllowUpdateComplianceProcessing**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-
-This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID policy settings, enables organizations to configure the device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the [Product Terms](https://www.microsoft.com/licensing/terms/productoffering).
-
-To enable this behavior, you must complete three steps:
-
- 1. Enable this policy setting.
- 2. Set **AllowTelemetry** to 1 – **Required (Basic)** or above.
- 3. If you're using Update Compliance rather than Windows Update for Business reports, set the Configure the Commercial ID setting for your Update Compliance workspace.
+3. Set Allow Telemetry to value 1 - Required, or higher
 
 When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
+- If you disable or do not configure this policy setting, devices enrolled to the Windows Update for Business deployment service will not be able to take advantage of some deployment service features.
+<!-- AllowWUfBCloudProcessing-Description-End -->
 
-If you disable or don't configure this policy setting, devices won't appear in Windows Update for Business reports or Update Compliance.
+<!-- AllowWUfBCloudProcessing-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+> [!IMPORTANT]
+> Starting with the January 2023 preview cumulative update, this policy is no longer supported to configure the processor option. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
+<!-- AllowWUfBCloudProcessing-Editable-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Allow Update Compliance Processing*
--   GP name: *AllowUpdateComplianceProcessing*
--   GP element: *AllowUpdateComplianceProcessing*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- AllowWUfBCloudProcessing-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- AllowWUfBCloudProcessing-DFProperties-End -->
 
--   0 - Disabled.
--   16 - Enabled.
-<!--/SupportedValues-->
-<!--/Policy-->
+<!-- AllowWUfBCloudProcessing-AllowedValues-Begin -->
+**Allowed values**:
 
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 8 | Enabled. |
+<!-- AllowWUfBCloudProcessing-AllowedValues-End -->
 
-<hr/>
+<!-- AllowWUfBCloudProcessing-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--Policy-->
-<a href="" id="system-allowusertoresetphone"></a>**System/AllowUserToResetPhone**
+| Name | Value |
+|:--|:--|
+| Name | AllowWUfBCloudProcessing |
+| Friendly Name | Allow WUfB Cloud Processing |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- AllowWUfBCloudProcessing-GpMapping-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- AllowWUfBCloudProcessing-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- AllowWUfBCloudProcessing-Examples-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- AllowWUfBCloudProcessing-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- BootStartDriverInitialization-Begin -->
+## BootStartDriverInitialization
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- BootStartDriverInitialization-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
+<!-- BootStartDriverInitialization-Applicability-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- BootStartDriverInitialization-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/BootStartDriverInitialization
+```
+<!-- BootStartDriverInitialization-OmaUri-End -->
 
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-Specifies whether to allow the user to factory reset the device by using control panel and hardware key combination.
-
-Most restricted value is 0.
-
-> [!TIP]
-> This policy is also applicable to Windows 10 and not exclusive to phone.
-<!--/Description-->
-<!--SupportedValues-->
-The following list shows the supported values:
--   0 – Not allowed.
--   1 (default) – Allowed to reset to factory default settings.
-<!--/SupportedValues-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-allowwufbcloudprocessing"></a>**System/AllowWUfBCloudProcessing**
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-
-This policy setting configures an Azure Active Directory-joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the [Product Terms](https://www.microsoft.com/licensing/terms/productoffering).
-
-To enable this behavior, you must complete three steps:
-
- 1. Enable this policy setting.
- 2. Set **AllowTelemetry** to 1 – **Required (Basic)** or above.
- 3. Join an Azure Active Directory account to the device.
-
-When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
-
-If you disable or don't configure this policy setting, devices enrolled to the Windows Update for Business deployment service won't be able to take advantage of some deployment service features.
-
-<hr/>
-
-<!--/Description-->
-<!--SupportedValues-->
-The following list shows the supported values:
-
--   0 - Disabled.
--   8 - Enabled.
-<!--/SupportedValues-->
-
-
-<!--Policy-->
-<a href="" id="system-bootstartdriverinitialization"></a>**System/BootStartDriverInitialization**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
+<!-- BootStartDriverInitialization-Description-Begin -->
+<!-- Description-Source-ADMX -->
 This policy setting allows you to specify which boot-start drivers are initialized based on a classification determined by an Early Launch Antimalware boot-start driver. The Early Launch Antimalware boot-start driver can return the following classifications for each boot-start driver:
--  Good: The driver has been signed and hasn't been tampered with.
--  Bad: The driver has been identified as malware. It's recommended that you don't allow known bad drivers to be initialized.
--  Bad, but required for boot: The driver has been identified as malware, but the computer can't successfully boot without loading this driver.
--  Unknown: This driver hasn't been attested to by your malware detection application and hasn't been classified by the Early Launch Antimalware boot-start driver.
+- Good: The driver has been signed and has not been tampered with.
+- Bad: The driver has been identified as malware. It is recommended that you do not allow known bad drivers to be initialized.
+- Bad, but required for boot: The driver has been identified as malware, but the computer cannot successfully boot without loading this driver.
+- Unknown: This driver has not been attested to by your malware detection application and has not been classified by the Early Launch Antimalware boot-start driver.
 
-If you enable this policy setting, you'll be able to choose which boot-start drivers to initialize next time the computer is started.
+- If you enable this policy setting you will be able to choose which boot-start drivers to initialize the next time the computer is started.
 
-If you disable or don't configure this policy setting, the boot start drivers determined to be Good, Unknown, or Bad, but Boot Critical are initialized and the initialization of drivers determined to be Bad is skipped.
+- If you disable or do not configure this policy setting, the boot start drivers determined to be Good, Unknown or Bad but Boot Critical are initialized and the initialization of drivers determined to be Bad is skipped.
 
-If your malware detection application doesn't include an Early Launch Antimalware boot-start driver or if your Early Launch Antimalware boot-start driver has been disabled, this setting has no effect and all boot-start drivers are initialized.
+If your malware detection application does not include an Early Launch Antimalware boot-start driver or if your Early Launch Antimalware boot-start driver has been disabled, this setting has no effect and all boot-start drivers are initialized.
+<!-- BootStartDriverInitialization-Description-End -->
 
-<!--/Description-->
+<!-- BootStartDriverInitialization-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- BootStartDriverInitialization-Editable-End -->
+
+<!-- BootStartDriverInitialization-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | chr (string) |
+| Access Type | Add, Delete, Get, Replace |
+<!-- BootStartDriverInitialization-DFProperties-End -->
+
+<!-- BootStartDriverInitialization-AdmxBacked-Begin -->
 > [!TIP]
-> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
->
-> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
->
-> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
+> This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
 
-<!--ADMXBacked-->
-ADMX Info:
--   GP Friendly name: *Boot-Start Driver Initialization Policy*
--   GP name: *POL_DriverLoadPolicy_Name*
--   GP path: *System/Early Launch Antimalware*
--   GP ADMX file name: *earlylauncham.admx*
+**ADMX mapping**:
 
-<!--/ADMXBacked-->
-<!--/Policy-->
+| Name | Value |
+|:--|:--|
+| Name | POL_DriverLoadPolicy_Name |
+| Friendly Name | Boot-Start Driver Initialization Policy |
+| Location | Computer Configuration |
+| Path | System > Early Launch Antimalware |
+| Registry Key Name | System\CurrentControlSet\Policies\EarlyLaunch |
+| Registry Value Name | DriverLoadPolicy |
+| ADMX File Name | EarlyLaunchAM.admx |
+<!-- BootStartDriverInitialization-AdmxBacked-End -->
 
-<hr/>
+<!-- BootStartDriverInitialization-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- BootStartDriverInitialization-Examples-End -->
 
-<!--Policy-->
-<a href="" id="system-configuremicrosoft365uploadendpoint"></a>**System/ConfigureMicrosoft365UploadEndpoint**
+<!-- BootStartDriverInitialization-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- ConfigureMicrosoft365UploadEndpoint-Begin -->
+## ConfigureMicrosoft365UploadEndpoint
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- ConfigureMicrosoft365UploadEndpoint-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763] and later |
+<!-- ConfigureMicrosoft365UploadEndpoint-Applicability-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- ConfigureMicrosoft365UploadEndpoint-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/ConfigureMicrosoft365UploadEndpoint
+```
+<!-- ConfigureMicrosoft365UploadEndpoint-OmaUri-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-This policy sets the upload endpoint for this device’s diagnostic data as part of the Microsoft 365 Update Readiness program.
+<!-- ConfigureMicrosoft365UploadEndpoint-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy sets the upload endpoint for this device's diagnostic data as part of the Desktop Analytics program.
 
 If your organization is participating in the program and has been instructed to configure a custom upload endpoint, then use this setting to define that endpoint.
-
 The value for this setting will be provided by Microsoft as part of the onboarding process for the program.
+<!-- ConfigureMicrosoft365UploadEndpoint-Description-End -->
 
-Supported value type is string.
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Configure Microsoft 365 Update Readiness upload endpoint*
--   GP name: *ConfigureMicrosoft365UploadEndpoint*
--   GP element: *ConfigureMicrosoft365UploadEndpoint*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- ConfigureMicrosoft365UploadEndpoint-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- ConfigureMicrosoft365UploadEndpoint-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
+<!-- ConfigureMicrosoft365UploadEndpoint-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/SupportedValues-->
-<!--Example-->
+| Property name | Property value |
+|:--|:--|
+| Format | chr (string) |
+| Access Type | Add, Delete, Get, Replace |
+<!-- ConfigureMicrosoft365UploadEndpoint-DFProperties-End -->
 
-<!--/Example-->
-<!--Validation-->
+<!-- ConfigureMicrosoft365UploadEndpoint-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--/Validation-->
-<!--/Policy-->
+| Name | Value |
+|:--|:--|
+| Name | ConfigureMicrosoft365UploadEndpoint |
+| Friendly Name | Configure diagnostic data upload endpoint for Desktop Analytics |
+| Element Name | Desktop Analytics Custom Upload Endpoint |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- ConfigureMicrosoft365UploadEndpoint-GpMapping-End -->
 
-<hr/>
+<!-- ConfigureMicrosoft365UploadEndpoint-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- ConfigureMicrosoft365UploadEndpoint-Examples-End -->
 
-<!--Policy-->
-<a href="" id="system-configuretelemetryoptinchangenotification"></a>**System/ConfigureTelemetryOptInChangeNotification**
+<!-- ConfigureMicrosoft365UploadEndpoint-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- ConfigureTelemetryOptInChangeNotification-Begin -->
+## ConfigureTelemetryOptInChangeNotification
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- ConfigureTelemetryOptInChangeNotification-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1803 [10.0.17134] and later |
+<!-- ConfigureTelemetryOptInChangeNotification-Applicability-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- ConfigureTelemetryOptInChangeNotification-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInChangeNotification
+```
+<!-- ConfigureTelemetryOptInChangeNotification-OmaUri-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- ConfigureTelemetryOptInChangeNotification-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting controls whether notifications are shown, following a change to diagnostic data opt-in settings, on first logon and when the changes occur in settings.
 
-> [!div class = "checklist"]
-> * Device
+If you set this policy setting to "Disable diagnostic data change notifications", diagnostic data opt-in change notifications will not appear.
 
-<hr/>
+If you set this policy setting to "Enable diagnostic data change notifications" or don't configure this policy setting, diagnostic data opt-in change notifications appear at first logon and when the changes occur in Settings.
+<!-- ConfigureTelemetryOptInChangeNotification-Description-End -->
 
-<!--/Scope-->
-<!--Description-->
-This policy setting determines whether a device shows notifications about telemetry levels to people on first sign in or when changes occur in Settings. 
+<!-- ConfigureTelemetryOptInChangeNotification-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- ConfigureTelemetryOptInChangeNotification-Editable-End -->
 
-- If you set this policy setting to "Disable telemetry change notifications", telemetry level notifications stop appearing.
-- If you set this policy setting to "Enable telemetry change notifications" or don't configure this policy setting, telemetry notifications appear at first sign in and when changes occur in Settings.
+<!-- ConfigureTelemetryOptInChangeNotification-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Configure telemetry opt-in change notifications.*
--   GP name: *ConfigureTelemetryOptInChangeNotification*
--   GP element: *ConfigureTelemetryOptInChangeNotification*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- ConfigureTelemetryOptInChangeNotification-DFProperties-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
--   0 (default) - Enable telemetry change notifications
--   1 - Disable telemetry change notifications
-<!--/SupportedValues-->
-<!--/Policy-->
+<!-- ConfigureTelemetryOptInChangeNotification-AllowedValues-Begin -->
+**Allowed values**:
 
-<hr/>
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Enable telemetry change notifications. |
+| 1 | Disable telemetry change notifications. |
+<!-- ConfigureTelemetryOptInChangeNotification-AllowedValues-End -->
 
-<!--Policy-->
-<a href="" id="system-configuretelemetryoptinsettingsux"></a>**System/ConfigureTelemetryOptInSettingsUx**
+<!-- ConfigureTelemetryOptInChangeNotification-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+| Name | Value |
+|:--|:--|
+| Name | ConfigureTelemetryOptInChangeNotification |
+| Friendly Name | Configure diagnostic data opt-in change notifications |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- ConfigureTelemetryOptInChangeNotification-GpMapping-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- ConfigureTelemetryOptInChangeNotification-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- ConfigureTelemetryOptInChangeNotification-Examples-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- ConfigureTelemetryOptInChangeNotification-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- ConfigureTelemetryOptInSettingsUx-Begin -->
+## ConfigureTelemetryOptInSettingsUx
 
-> [!div class = "checklist"]
-> * Device
+<!-- ConfigureTelemetryOptInSettingsUx-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1803 [10.0.17134] and later |
+<!-- ConfigureTelemetryOptInSettingsUx-Applicability-End -->
 
-<hr/>
+<!-- ConfigureTelemetryOptInSettingsUx-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInSettingsUx
+```
+<!-- ConfigureTelemetryOptInSettingsUx-OmaUri-End -->
 
-<!--/Scope-->
-<!--Description-->
-This policy setting determines whether people can change their own telemetry levels in Settings. This setting should be used in conjunction with the Allow Telemetry settings.
+<!-- ConfigureTelemetryOptInSettingsUx-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting determines whether an end user can change diagnostic data settings in the Settings app.
 
-If you set this policy setting to "Disable Telemetry opt-in Settings", telemetry levels are disabled in Settings, preventing people from changing them.
+If you set this policy setting to "Disable diagnostic data opt-in settings", diagnostic data settings are disabled in the Settings app.
 
-If you set this policy setting to "Enable Telemetry opt-in Settings" or don't configure this policy setting, people can change their own telemetry levels in Settings.
+- If you don't configure this policy setting, or you set it to "Enable diagnostic data opt-in settings", end users can change the device diagnostic settings in the Settings app.
 
-> [!Note]
-> Set the Allow Telemetry policy setting to prevent people from sending diagnostic data to Microsoft beyond your organization's acceptable level of data disclosure.
+**Note**:
+To set a limit on the amount of diagnostic data that is sent to Microsoft by your organization, use the "Allow Diagnostic Data" policy setting.
+<!-- ConfigureTelemetryOptInSettingsUx-Description-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Configure telemetry opt-in setting user interface.*
--   GP name: *ConfigureTelemetryOptInSettingsUx*
--   GP element: *ConfigureTelemetryOptInSettingsUx*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- ConfigureTelemetryOptInSettingsUx-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- ConfigureTelemetryOptInSettingsUx-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
--   0 (default) - Enable Telemetry opt-in Settings
--   1 - Disable Telemetry opt-in Settings
-<!--/SupportedValues-->
-<!--/Policy-->
+<!-- ConfigureTelemetryOptInSettingsUx-DFProperties-Begin -->
+**Description framework properties**:
 
-<hr/>
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- ConfigureTelemetryOptInSettingsUx-DFProperties-End -->
 
-<!--Policy-->
-<a href="" id="system-disabledevicedelete"></a>**System/DisableDeviceDelete**
+<!-- ConfigureTelemetryOptInSettingsUx-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Enable Telemetry opt-in Settings. |
+| 1 | Disable Telemetry opt-in Settings. |
+<!-- ConfigureTelemetryOptInSettingsUx-AllowedValues-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- ConfigureTelemetryOptInSettingsUx-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--/SupportedSKUs-->
-<hr/>
+| Name | Value |
+|:--|:--|
+| Name | ConfigureTelemetryOptInSettingsUx |
+| Friendly Name | Configure diagnostic data opt-in settings user interface |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- ConfigureTelemetryOptInSettingsUx-GpMapping-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- ConfigureTelemetryOptInSettingsUx-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- ConfigureTelemetryOptInSettingsUx-Examples-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- ConfigureTelemetryOptInSettingsUx-End -->
 
-<hr/>
+<!-- DisableDeviceDelete-Begin -->
+## DisableDeviceDelete
 
-<!--/Scope-->
-<!--Description-->
-This policy setting controls whether the Delete diagnostic data button is enabled in Diagnostic & Feedback Settings page.
+<!-- DisableDeviceDelete-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763] and later |
+<!-- DisableDeviceDelete-Applicability-End -->
+
+<!-- DisableDeviceDelete-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableDeviceDelete
+```
+<!-- DisableDeviceDelete-OmaUri-End -->
+
+<!-- DisableDeviceDelete-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting controls whether the Delete diagnostic data button is enabled in Diagnostic & feedback Settings page.
 
 - If you enable this policy setting, the Delete diagnostic data button will be disabled in Settings page, preventing the deletion of diagnostic data collected by Microsoft from the device.
+
 - If you disable or don't configure this policy setting, the Delete diagnostic data button will be enabled in Settings page, which allows people to erase all diagnostic data collected by Microsoft from that device.
+<!-- DisableDeviceDelete-Description-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Disable deleting diagnostic data*
--   GP name: *DisableDeviceDelete*
--   GP element: *DisableDeviceDelete*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- DisableDeviceDelete-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableDeviceDelete-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
+<!-- DisableDeviceDelete-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/SupportedValues-->
-<!--Example-->
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- DisableDeviceDelete-DFProperties-End -->
 
-<!--/Example-->
-<!--Validation-->
+<!-- DisableDeviceDelete-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/Validation-->
-<!--/Policy-->
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Not disabled. |
+| 1 | Disabled. |
+<!-- DisableDeviceDelete-AllowedValues-End -->
 
-<hr/>
+<!-- DisableDeviceDelete-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--Policy-->
-<a href="" id="system-disablediagnosticdataviewer"></a>**System/DisableDiagnosticDataViewer**
+| Name | Value |
+|:--|:--|
+| Name | DisableDeviceDelete |
+| Friendly Name | Disable deleting diagnostic data |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- DisableDeviceDelete-GpMapping-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- DisableDeviceDelete-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableDeviceDelete-Examples-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- DisableDeviceDelete-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- DisableDiagnosticDataViewer-Begin -->
+## DisableDiagnosticDataViewer
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- DisableDiagnosticDataViewer-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1809 [10.0.17763] and later |
+<!-- DisableDiagnosticDataViewer-Applicability-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- DisableDiagnosticDataViewer-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableDiagnosticDataViewer
+```
+<!-- DisableDiagnosticDataViewer-OmaUri-End -->
 
-<hr/>
+<!-- DisableDiagnosticDataViewer-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting controls whether users can enable and launch the Diagnostic Data Viewer from the Diagnostic & feedback Settings page.
 
-<!--/Scope-->
-<!--Description-->
-This policy setting controls whether users can enable and launch the Diagnostic Data Viewer from the Diagnostic & Feedback Settings page.
+- If you enable this policy setting, the Diagnostic Data Viewer will not be enabled in Settings page, and it will prevent the viewer from showing diagnostic data collected by Microsoft from the device.
 
-- If you enable this policy setting, the Diagnostic Data Viewer won't be enabled in Settings page, and it will prevent the viewer from showing diagnostic data collected by Microsoft from the device.
 - If you disable or don't configure this policy setting, the Diagnostic Data Viewer will be enabled in Settings page.
+<!-- DisableDiagnosticDataViewer-Description-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Disable diagnostic data viewer.*
--   GP name: *DisableDiagnosticDataViewer*
--   GP element: *DisableDiagnosticDataViewer*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- DisableDiagnosticDataViewer-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableDiagnosticDataViewer-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
+<!-- DisableDiagnosticDataViewer-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/SupportedValues-->
-<!--Example-->
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- DisableDiagnosticDataViewer-DFProperties-End -->
 
-<!--/Example-->
-<!--Validation-->
+<!-- DisableDiagnosticDataViewer-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/Validation-->
-<!--/Policy-->
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Not disabled. |
+| 1 | Disabled. |
+<!-- DisableDiagnosticDataViewer-AllowedValues-End -->
 
-<hr/>
+<!-- DisableDiagnosticDataViewer-GpMapping-Begin -->
+**Group policy mapping**:
 
-<!--Policy-->
-<a href="" id="system-disableenterpriseauthproxy"></a>**System/DisableEnterpriseAuthProxy**
+| Name | Value |
+|:--|:--|
+| Name | DisableDiagnosticDataViewer |
+| Friendly Name | Disable diagnostic data viewer |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- DisableDiagnosticDataViewer-GpMapping-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- DisableDiagnosticDataViewer-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableDiagnosticDataViewer-Examples-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- DisableDiagnosticDataViewer-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- DisableDirectXDatabaseUpdate-Begin -->
+## DisableDirectXDatabaseUpdate
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- DisableDirectXDatabaseUpdate-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1903 [10.0.18362] and later |
+<!-- DisableDirectXDatabaseUpdate-Applicability-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- DisableDirectXDatabaseUpdate-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableDirectXDatabaseUpdate
+```
+<!-- DisableDirectXDatabaseUpdate-OmaUri-End -->
 
-<hr/>
+<!-- DisableDirectXDatabaseUpdate-Description-Begin -->
+<!-- Description-Source-DDF -->
+This group policy allows control over whether the DirectX Database Updater task will be run on the system.
+<!-- DisableDirectXDatabaseUpdate-Description-End -->
 
-<!--/Scope-->
-<!--Description-->
-This policy setting blocks the Connected User Experience and Telemetry service from automatically using an authenticated proxy, to send data back to Microsoft on Windows 10. If you disable or don't configure this policy setting, the Connected User Experience and Telemetry service will automatically use an authenticated proxy, to send data back to Microsoft. Enabling this policy will block the Connected User Experience and Telemetry service from automatically using an authenticated proxy.
+<!-- DisableDirectXDatabaseUpdate-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableDirectXDatabaseUpdate-Editable-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Configure Authenticated Proxy usage for the Connected User Experience and Telemetry service*
--   GP name: *DisableEnterpriseAuthProxy*
--   GP element: *DisableEnterpriseAuthProxy*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
+<!-- DisableDirectXDatabaseUpdate-DFProperties-Begin -->
+**Description framework properties**:
 
-<!--/ADMXMapped-->
-<!--/Policy-->
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- DisableDirectXDatabaseUpdate-DFProperties-End -->
 
-<hr/>
+<!-- DisableDirectXDatabaseUpdate-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--Policy-->
-<a href="" id="system-disableonedrivefilesync"></a>**System/DisableOneDriveFileSync**
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Not disabled. |
+| 1 | Disabled. |
+<!-- DisableDirectXDatabaseUpdate-AllowedValues-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- DisableDirectXDatabaseUpdate-GpMapping-Begin -->
+**Group policy mapping**:
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+| Name | Value |
+|:--|:--|
+| Name | DisableDirectXDatabaseUpdate |
+| Path | GroupPolicy > AT > Network > DirectXDatabase |
+<!-- DisableDirectXDatabaseUpdate-GpMapping-End -->
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- DisableDirectXDatabaseUpdate-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableDirectXDatabaseUpdate-Examples-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- DisableDirectXDatabaseUpdate-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- DisableEnterpriseAuthProxy-Begin -->
+## DisableEnterpriseAuthProxy
 
-<hr/>
+<!-- DisableEnterpriseAuthProxy-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1709 [10.0.16299] and later |
+<!-- DisableEnterpriseAuthProxy-Applicability-End -->
 
-<!--/Scope-->
-<!--Description-->
-Allows IT Admins to prevent apps and features from working with files on OneDrive. If you enable this policy setting:
+<!-- DisableEnterpriseAuthProxy-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableEnterpriseAuthProxy
+```
+<!-- DisableEnterpriseAuthProxy-OmaUri-End -->
 
-* Users can't access OneDrive from the OneDrive app or file picker.
-* Microsoft Store apps can't access OneDrive using the WinRT API.
+<!-- DisableEnterpriseAuthProxy-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting blocks the Connected User Experience and Telemetry service from automatically using an authenticated proxy to send data back to Microsoft on Windows 10.
+- If you disable or do not configure this policy setting, the Connected User Experience and Telemetry service will automatically use an authenticated proxy to send data back to Microsoft. Enabling this policy will block the Connected User Experience and Telemetry service from automatically using an authenticated proxy.
+<!-- DisableEnterpriseAuthProxy-Description-End -->
+
+<!-- DisableEnterpriseAuthProxy-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableEnterpriseAuthProxy-Editable-End -->
+
+<!-- DisableEnterpriseAuthProxy-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- DisableEnterpriseAuthProxy-DFProperties-End -->
+
+<!-- DisableEnterpriseAuthProxy-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 1 | Enable. |
+| 0 (Default) | Disable. |
+<!-- DisableEnterpriseAuthProxy-AllowedValues-End -->
+
+<!-- DisableEnterpriseAuthProxy-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | DisableEnterpriseAuthProxy |
+| Friendly Name | Configure Authenticated Proxy usage for the Connected User Experience and Telemetry service |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- DisableEnterpriseAuthProxy-GpMapping-End -->
+
+<!-- DisableEnterpriseAuthProxy-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableEnterpriseAuthProxy-Examples-End -->
+
+<!-- DisableEnterpriseAuthProxy-End -->
+
+<!-- DisableOneDriveFileSync-Begin -->
+## DisableOneDriveFileSync
+
+<!-- DisableOneDriveFileSync-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
+<!-- DisableOneDriveFileSync-Applicability-End -->
+
+<!-- DisableOneDriveFileSync-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableOneDriveFileSync
+```
+<!-- DisableOneDriveFileSync-OmaUri-End -->
+
+<!-- DisableOneDriveFileSync-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting lets you prevent apps and features from working with files on OneDrive.
+- If you enable this policy setting:
+
+* Users can't access OneDrive from the OneDrive app and file picker.
+* Windows Store apps can't access OneDrive using the WinRT API.
 * OneDrive doesn't appear in the navigation pane in File Explorer.
 * OneDrive files aren't kept in sync with the cloud.
 * Users can't automatically upload photos and videos from the camera roll folder.
 
-If you disable or don't configure this policy setting, apps and features can work with OneDrive file storage.
+- If you disable or do not configure this policy setting, apps and features can work with OneDrive file storage.
+<!-- DisableOneDriveFileSync-Description-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Prevent the usage of OneDrive for file storage*
--   GP name: *PreventOnedriveFileSync*
--   GP path: *Windows Components/OneDrive*
--   GP ADMX file name: *SkyDrive.admx*
+<!-- DisableOneDriveFileSync-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableOneDriveFileSync-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- DisableOneDriveFileSync-DFProperties-Begin -->
+**Description framework properties**:
 
--   0 (default) – False (sync enabled).
--   1 – True (sync disabled).
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- DisableOneDriveFileSync-DFProperties-End -->
 
-<!--/SupportedValues-->
-<!--Validation-->
-To validate on Desktop, do the following steps:
+<!-- DisableOneDriveFileSync-AllowedValues-Begin -->
+**Allowed values**:
 
-1.   Enable policy.
-2.   Restart machine.
-3.   Verify that OneDrive.exe isn't running in Task Manager.
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Sync enabled. |
+| 1 | Sync disabled. |
+<!-- DisableOneDriveFileSync-AllowedValues-End -->
 
-<!--/Validation-->
-<!--/Policy-->
+<!-- DisableOneDriveFileSync-GpMapping-Begin -->
+**Group policy mapping**:
 
-<hr/>
+| Name | Value |
+|:--|:--|
+| Name | PreventOnedriveFileSync |
+| Friendly Name | Prevent the usage of OneDrive for file storage |
+| Location | Computer Configuration |
+| Path | Windows Components > OneDrive |
+| Registry Key Name | Software\Policies\Microsoft\Windows\OneDrive |
+| Registry Value Name | DisableFileSyncNGSC |
+| ADMX File Name | SkyDrive.admx |
+<!-- DisableOneDriveFileSync-GpMapping-End -->
 
-<!--Policy-->
-<a href="" id="system-disablesystemrestore"></a>**System/DisableSystemRestore**
+<!-- DisableOneDriveFileSync-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableOneDriveFileSync-Examples-End -->
 
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
+<!-- DisableOneDriveFileSync-End -->
 
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
+<!-- DisableOneSettingsDownloads-Begin -->
+## DisableOneSettingsDownloads
 
-<!--/SupportedSKUs-->
-<hr/>
+<!-- DisableOneSettingsDownloads-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- DisableOneSettingsDownloads-Applicability-End -->
 
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
+<!-- DisableOneSettingsDownloads-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableOneSettingsDownloads
+```
+<!-- DisableOneSettingsDownloads-OmaUri-End -->
 
-> [!div class = "checklist"]
-> * Device
+<!-- DisableOneSettingsDownloads-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting controls whether Windows attempts to connect with the OneSettings service.
 
-<hr/>
+- If you enable this policy, Windows will not attempt to connect with the OneSettings Service.
 
-<!--/Scope-->
-<!--Description-->
+- If you disable or don't configure this policy setting, Windows will periodically attempt to connect with the OneSettings service to download configuration settings.
+<!-- DisableOneSettingsDownloads-Description-End -->
+
+<!-- DisableOneSettingsDownloads-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableOneSettingsDownloads-Editable-End -->
+
+<!-- DisableOneSettingsDownloads-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- DisableOneSettingsDownloads-DFProperties-End -->
+
+<!-- DisableOneSettingsDownloads-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Not disabled. |
+| 1 | Disabled. |
+<!-- DisableOneSettingsDownloads-AllowedValues-End -->
+
+<!-- DisableOneSettingsDownloads-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | DisableOneSettingsDownloads |
+| Friendly Name | Disable OneSettings Downloads |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- DisableOneSettingsDownloads-GpMapping-End -->
+
+<!-- DisableOneSettingsDownloads-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableOneSettingsDownloads-Examples-End -->
+
+<!-- DisableOneSettingsDownloads-End -->
+
+<!-- DisableSystemRestore-Begin -->
+## DisableSystemRestore
+
+<!-- DisableSystemRestore-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
+<!-- DisableSystemRestore-Applicability-End -->
+
+<!-- DisableSystemRestore-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/DisableSystemRestore
+```
+<!-- DisableSystemRestore-OmaUri-End -->
+
+<!-- DisableSystemRestore-Description-Begin -->
+<!-- Description-Source-ADMX -->
 Allows you to disable System Restore.
 
 This policy setting allows you to turn off System Restore.
 
-System Restore enables users, in case of a problem, to restore their computers to a previous state without losing personal data files. By default, System Restore is turned on for the boot volume.
+System Restore enables users, in the event of a problem, to restore their computers to a previous state without losing personal data files. By default, System Restore is turned on for the boot volume.
 
-If you enable this policy setting, System Restore is turned off, then System Restore Wizard can't be accessed. The option to configure System Restore or create a restore point through System Protection is also disabled.
+- If you enable this policy setting, System Restore is turned off, and the System Restore Wizard cannot be accessed. The option to configure System Restore or create a restore point through System Protection is also disabled.
 
-If you disable or don't configure this policy setting, users can perform System Restore, and configure System Restore settings through System Protection.
+- If you disable or do not configure this policy setting, users can perform System Restore and configure System Restore settings through System Protection.
 
 Also, see the "Turn off System Restore configuration" policy setting. If the "Turn off System Restore" policy setting is disabled or not configured, the "Turn off System Restore configuration" policy setting is used to determine whether the option to configure System Restore is available.
+<!-- DisableSystemRestore-Description-End -->
 
-<!--/Description-->
+<!-- DisableSystemRestore-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- DisableSystemRestore-Editable-End -->
+
+<!-- DisableSystemRestore-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | chr (string) |
+| Access Type | Add, Delete, Get, Replace |
+<!-- DisableSystemRestore-DFProperties-End -->
+
+<!-- DisableSystemRestore-AdmxBacked-Begin -->
 > [!TIP]
-> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
->
-> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
->
-> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
-
-<!--ADMXBacked-->
-ADMX Info:
--   GP Friendly name: *Turn off System Restore*
--   GP name: *SR_DisableSR*
--   GP path: *System/System Restore*
--   GP ADMX file name: *systemrestore.admx*
-
-<!--/ADMXBacked-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-feedbackhubalwayssavediagnosticslocally"></a>**System/FeedbackHubAlwaysSaveDiagnosticsLocally**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|Yes|Yes|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-When feedback in the Feedback Hub is being filed, diagnostic logs are collected for certain types of feedback. We now offer the option for users to save it locally, in addition to sending it to Microsoft. This policy will allow enterprises to mandate that all diagnostics are saved locally for use in internal investigations.
-
-<!--/Description-->
-<!--SupportedValues-->
-The following list shows the supported values:
-
-- 0 (default) - False. The Feedback Hub won't always save a local copy of diagnostics that may be created when feedback is submitted. The user will have the option to do so.
-- 1 - True. The Feedback Hub should always save a local copy of diagnostics that may be created when feedback is submitted.
-
-<!--/SupportedValues-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-limitdiagnosticlogcollection"></a>**System/LimitDiagnosticLogCollection**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-This policy setting specifies whether diagnostic log data can be collected when more information is needed to troubleshoot a problem. It's sent only if we have permission to collect optional diagnostic data, and only if the device meets the criteria for more data collection.
-
-If you disable or don't configure this policy setting, we may occasionally collect advanced diagnostic data if the user has opted to send optional diagnostic data.
-
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Limit Diagnostic Log Collection*
--   GP name: *LimitDiagnosticLogCollection*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
-
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
-
--   0 – Disabled
--   1 – Enabled
-
-<!--/SupportedValues-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-limitdumpcollection"></a>**System/LimitDumpCollection**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-This policy setting limits the type of dumps that can be collected when more information is needed to troubleshoot a problem. These dumps aren't sent unless we have permission to collect optional diagnostic data.
-
-With this policy setting being enabled, Windows Error Reporting is limited to sending kernel mini dumps and user mode triage dumps only.
-
-If you disable or don't configure this policy setting, we may occasionally collect full or heap dumps if the user has opted to send optional diagnostic data.
-
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Limit Dump Collection*
--   GP name: *LimitDumpCollection*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
-
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
-
--   0 – Disabled
--   1 – Enabled
-<!--/SupportedValues-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-limitenhanceddiagnosticdatawindowsanalytics"></a>**System/LimitEnhancedDiagnosticDataWindowsAnalytics**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-This policy setting, in combination with the Allow Telemetry policy setting, enables organizations to send Microsoft a specific set of diagnostic data for IT insights via Windows Analytics services.
-
-To enable this behavior, you must complete two steps:
-
- 1. Enable this policy setting.
-
- 2. Set the **AllowTelemetry** level:
-
-    - For Windows 10 version 1809 and older: set **AllowTelemetry** to Enhanced.
-
-      > [!NOTE]
-      > **Enhanced** is no longer an option for Windows Holographic, version 21H1.
-
-    - For Windows 10 version 19H1 and later: set **AllowTelemetry** to Optional (Full).
-
-When you configure these policy settings, a basic level of diagnostic data plus other events that are required for Windows Analytics are sent to Microsoft. These events are documented here: <a href="/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields" data-raw-source="[Windows 10, version 1709 enhanced telemetry events and fields used by Windows Analytics](/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields)">Windows 10, version 1709 enhanced telemetry events and fields used by Windows Analytics</a>.
-
-Enabling enhanced diagnostic data in the Allow Telemetry policy in combination with not configuring this policy will also send the required events for Windows Analytics, plus enhanced level telemetry data. This setting has no effect on computers configured to send Required (Basic) or Optional (Full) diagnostic data to Microsoft.
-
-If you disable or don't configure this policy setting, then the level of diagnostic data sent to Microsoft is determined by the System/AllowTelemetry policy.
-
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Limit Enhanced diagnostic data to the minimum required by Windows Analytics*
--   GP name: *LimitEnhancedDiagnosticDataWindowsAnalytics*
--   GP element: *LimitEnhancedDiagnosticDataWindowsAnalytics*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
-
-<!--/ADMXMapped-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-telemetryproxy"></a>**System/TelemetryProxy**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
-Allows you to specify the fully qualified domain name (FQDN) or IP address of a proxy server to forward Connected User Experiences and Telemetry requests. The format for this setting is *&lt;server&gt;:&lt;port&gt;*. The connection is made over a Secure Sockets Layer (SSL) connection. If the named proxy fails, or if there's no proxy specified when this policy is enabled, the Connected User Experiences and Telemetry data won't be transmitted and will remain on the local device.
-
-If you disable or don't configure this policy setting, Connected User Experiences and Telemetry will go to Microsoft using the default proxy configuration.
-
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Configure Connected User Experiences and Telemetry*
--   GP name: *TelemetryProxy*
--   GP element: *TelemetryProxyName*
--   GP path: *Data Collection and Preview Builds*
--   GP ADMX file name: *DataCollection.admx*
-
-<!--/ADMXMapped-->
-<!--/Policy-->
-
-<hr/>
-
-<!--Policy-->
-<a href="" id="system-turnofffilehistory"></a>**System/TurnOffFileHistory**
-
-<!--SupportedSKUs-->
-The table below shows the applicability of Windows:
-
-|Edition|Windows 10|Windows 11|
-|--- |--- |--- |
-|Home|No|No|
-|Pro|Yes|Yes|
-|Windows SE|No|Yes|
-|Enterprise|Yes|Yes|
-|Education|Yes|Yes|
-
-<!--/SupportedSKUs-->
-<hr/>
-
-<!--Scope-->
-[Scope](./policy-configuration-service-provider.md#policy-scope):
-
-> [!div class = "checklist"]
-> * Device
-
-<hr/>
-
-<!--/Scope-->
-<!--Description-->
+> This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
+
+**ADMX mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | SR_DisableSR |
+| Friendly Name | Turn off System Restore |
+| Location | Computer Configuration |
+| Path | System > System Restore |
+| Registry Key Name | Software\Policies\Microsoft\Windows NT\SystemRestore |
+| Registry Value Name | DisableSR |
+| ADMX File Name | SystemRestore.admx |
+<!-- DisableSystemRestore-AdmxBacked-End -->
+
+<!-- DisableSystemRestore-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- DisableSystemRestore-Examples-End -->
+
+<!-- DisableSystemRestore-End -->
+
+<!-- EnableOneSettingsAuditing-Begin -->
+## EnableOneSettingsAuditing
+
+<!-- EnableOneSettingsAuditing-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- EnableOneSettingsAuditing-Applicability-End -->
+
+<!-- EnableOneSettingsAuditing-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/EnableOneSettingsAuditing
+```
+<!-- EnableOneSettingsAuditing-OmaUri-End -->
+
+<!-- EnableOneSettingsAuditing-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting controls whether Windows records attempts to connect with the OneSettings service to the EventLog.
+
+- If you enable this policy, Windows will record attempts to connect with the OneSettings service to the Microsoft\Windows\Privacy-Auditing\Operational EventLog channel.
+
+- If you disable or don't configure this policy setting, Windows will not record attempts to connect with the OneSettings service to the EventLog.
+<!-- EnableOneSettingsAuditing-Description-End -->
+
+<!-- EnableOneSettingsAuditing-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- EnableOneSettingsAuditing-Editable-End -->
+
+<!-- EnableOneSettingsAuditing-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- EnableOneSettingsAuditing-DFProperties-End -->
+
+<!-- EnableOneSettingsAuditing-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Enabled. |
+<!-- EnableOneSettingsAuditing-AllowedValues-End -->
+
+<!-- EnableOneSettingsAuditing-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | EnableOneSettingsAuditing |
+| Friendly Name | Enable OneSettings Auditing |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- EnableOneSettingsAuditing-GpMapping-End -->
+
+<!-- EnableOneSettingsAuditing-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- EnableOneSettingsAuditing-Examples-End -->
+
+<!-- EnableOneSettingsAuditing-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Begin -->
+## FeedbackHubAlwaysSaveDiagnosticsLocally
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1709 [10.0.16299] and later |
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Applicability-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/FeedbackHubAlwaysSaveDiagnosticsLocally
+```
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-OmaUri-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Description-Begin -->
+<!-- Description-Source-DDF -->
+Diagnostic files created when a feedback is filed in the Feedback Hub app will always be saved locally. If this policy is not present or set to false, users will be presented with the option to save locally. The default is to not save locally.
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Description-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Editable-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-DFProperties-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | False. The Feedback Hub will not always save a local copy of diagnostics that may be created when a feedback is submitted. The user will have the option to do so. |
+| 1 | True. The Feedback Hub should always save a local copy of diagnostics that may be created when a feedback is submitted. |
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-AllowedValues-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-Examples-End -->
+
+<!-- FeedbackHubAlwaysSaveDiagnosticsLocally-End -->
+
+<!-- HideUnsupportedHardwareNotifications-Begin -->
+## HideUnsupportedHardwareNotifications
+
+<!-- HideUnsupportedHardwareNotifications-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows Insider Preview |
+<!-- HideUnsupportedHardwareNotifications-Applicability-End -->
+
+<!-- HideUnsupportedHardwareNotifications-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/HideUnsupportedHardwareNotifications
+```
+<!-- HideUnsupportedHardwareNotifications-OmaUri-End -->
+
+<!-- HideUnsupportedHardwareNotifications-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy controls messages which are shown when Windows is running on a device that does not meet the minimum system requirements for this OS version.
+
+- If you enable this policy setting, these messages will never appear on desktop or in the Settings app.
+
+- If you disable or do not configure this policy setting, these messages will appear on desktop and in the Settings app when Windows is running on a device that does not meet the minimum system requirements for this OS version.
+<!-- HideUnsupportedHardwareNotifications-Description-End -->
+
+<!-- HideUnsupportedHardwareNotifications-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- HideUnsupportedHardwareNotifications-Editable-End -->
+
+<!-- HideUnsupportedHardwareNotifications-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- HideUnsupportedHardwareNotifications-DFProperties-End -->
+
+<!-- HideUnsupportedHardwareNotifications-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Enabled. |
+<!-- HideUnsupportedHardwareNotifications-AllowedValues-End -->
+
+<!-- HideUnsupportedHardwareNotifications-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | HideUnsupportedHardwareNotifications |
+| Friendly Name | Hide messages when Windows system requirements are not met |
+| Location | Computer Configuration |
+| Path | System |
+| Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\System |
+| Registry Value Name | HideUnsupportedHardwareNotifications |
+| ADMX File Name | ControlPanel.admx |
+<!-- HideUnsupportedHardwareNotifications-GpMapping-End -->
+
+<!-- HideUnsupportedHardwareNotifications-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- HideUnsupportedHardwareNotifications-Examples-End -->
+
+<!-- HideUnsupportedHardwareNotifications-End -->
+
+<!-- LimitDiagnosticLogCollection-Begin -->
+## LimitDiagnosticLogCollection
+
+<!-- LimitDiagnosticLogCollection-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- LimitDiagnosticLogCollection-Applicability-End -->
+
+<!-- LimitDiagnosticLogCollection-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/LimitDiagnosticLogCollection
+```
+<!-- LimitDiagnosticLogCollection-OmaUri-End -->
+
+<!-- LimitDiagnosticLogCollection-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting controls whether additional diagnostic logs are collected when more information is needed to troubleshoot a problem on the device. Diagnostic logs are only sent when the device has been configured to send optional diagnostic data.
+
+By enabling this policy setting, diagnostic logs will not be collected.
+
+- If you disable or do not configure this policy setting, we may occasionally collect diagnostic logs if the device has been configured to send optional diagnostic data.
+<!-- LimitDiagnosticLogCollection-Description-End -->
+
+<!-- LimitDiagnosticLogCollection-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- LimitDiagnosticLogCollection-Editable-End -->
+
+<!-- LimitDiagnosticLogCollection-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- LimitDiagnosticLogCollection-DFProperties-End -->
+
+<!-- LimitDiagnosticLogCollection-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Enabled. |
+<!-- LimitDiagnosticLogCollection-AllowedValues-End -->
+
+<!-- LimitDiagnosticLogCollection-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | LimitDiagnosticLogCollection |
+| Friendly Name | Limit Diagnostic Log Collection |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- LimitDiagnosticLogCollection-GpMapping-End -->
+
+<!-- LimitDiagnosticLogCollection-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- LimitDiagnosticLogCollection-Examples-End -->
+
+<!-- LimitDiagnosticLogCollection-End -->
+
+<!-- LimitDumpCollection-Begin -->
+## LimitDumpCollection
+
+<!-- LimitDumpCollection-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
+<!-- LimitDumpCollection-Applicability-End -->
+
+<!-- LimitDumpCollection-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/LimitDumpCollection
+```
+<!-- LimitDumpCollection-OmaUri-End -->
+
+<!-- LimitDumpCollection-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting limits the type of dumps that can be collected when more information is needed to troubleshoot a problem. Dumps are only sent when the device has been configured to send optional diagnostic data.
+
+By enabling this setting, Windows Error Reporting is limited to sending kernel mini dumps and user mode triage dumps.
+
+- If you disable or do not configure this policy setting, we may occasionally collect full or heap dumps if the user has opted to send optional diagnostic data.
+<!-- LimitDumpCollection-Description-End -->
+
+<!-- LimitDumpCollection-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- LimitDumpCollection-Editable-End -->
+
+<!-- LimitDumpCollection-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- LimitDumpCollection-DFProperties-End -->
+
+<!-- LimitDumpCollection-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Enabled. |
+<!-- LimitDumpCollection-AllowedValues-End -->
+
+<!-- LimitDumpCollection-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | LimitDumpCollection |
+| Friendly Name | Limit Dump Collection |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- LimitDumpCollection-GpMapping-End -->
+
+<!-- LimitDumpCollection-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- LimitDumpCollection-Examples-End -->
+
+<!-- LimitDumpCollection-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Begin -->
+## LimitEnhancedDiagnosticDataWindowsAnalytics
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1709 [10.0.16299] and later |
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Applicability-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/LimitEnhancedDiagnosticDataWindowsAnalytics
+```
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-OmaUri-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Description-Begin -->
+<!-- Description-Source-ADMX -->
+This policy setting, in combination with the "Allow Diagnostic Data" policy setting, enables organizations to send the minimum data required by Desktop Analytics.
+
+To enable the behavior described above, complete the following steps:
+
+1. Enable this policy setting
+2. Set the "Allow Diagnostic Data" policy to "Send optional diagnostic data"
+
+3. Enable the "Limit Dump Collection" policy
+4. Enable the "Limit Diagnostic Log Collection" policy
+
+When these policies are configured, Microsoft will collect only required diagnostic data and the events required by Desktop Analytics, which can be viewed at <https://go.microsoft.com/fwlink/?linkid=2116020>.
+
+- If you disable or do not configure this policy setting, diagnostic data collection is determined by the "Allow Diagnostic Data" policy setting or by the end user from the Settings app.
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Description-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Editable-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-DFProperties-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-AllowedValues-Begin -->
+**Allowed values**:
+
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Disabled. |
+| 1 | Enabled. |
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-AllowedValues-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | LimitEnhancedDiagnosticDataWindowsAnalytics |
+| Friendly Name | Limit optional diagnostic data for Desktop Analytics |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-GpMapping-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-Examples-End -->
+
+<!-- LimitEnhancedDiagnosticDataWindowsAnalytics-End -->
+
+<!-- TelemetryProxy-Begin -->
+## TelemetryProxy
+
+<!-- TelemetryProxy-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1607 [10.0.14393] and later |
+<!-- TelemetryProxy-Applicability-End -->
+
+<!-- TelemetryProxy-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/TelemetryProxy
+```
+<!-- TelemetryProxy-OmaUri-End -->
+
+<!-- TelemetryProxy-Description-Begin -->
+<!-- Description-Source-DDF -->
+Allows you to specify the fully qualified domain name (FQDN) or IP address of a proxy server to forward Connected User Experiences and Telemetry requests. The format for this setting is `<server>`:`<port>`. The connection is made over a Secure Sockets Layer (SSL) connection. If the named proxy fails, or if there is no proxy specified when this policy is enabled, the Connected User Experiences and Telemetry data will not be transmitted and will remain on the local device.
+- If you disable or do not configure this policy setting, Connected User Experiences and Telemetry will go to Microsoft using the default proxy configuration.
+<!-- TelemetryProxy-Description-End -->
+
+<!-- TelemetryProxy-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- TelemetryProxy-Editable-End -->
+
+<!-- TelemetryProxy-DFProperties-Begin -->
+**Description framework properties**:
+
+| Property name | Property value |
+|:--|:--|
+| Format | chr (string) |
+| Access Type | Add, Delete, Get, Replace |
+<!-- TelemetryProxy-DFProperties-End -->
+
+<!-- TelemetryProxy-GpMapping-Begin -->
+**Group policy mapping**:
+
+| Name | Value |
+|:--|:--|
+| Name | TelemetryProxy |
+| Friendly Name | Configure Connected User Experiences and Telemetry |
+| Element Name | Proxy Server Name |
+| Location | Computer Configuration |
+| Path | WindowsComponents > Data Collection and Preview Builds |
+| Registry Key Name | Software\Policies\Microsoft\Windows\DataCollection |
+| ADMX File Name | DataCollection.admx |
+<!-- TelemetryProxy-GpMapping-End -->
+
+<!-- TelemetryProxy-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- TelemetryProxy-Examples-End -->
+
+<!-- TelemetryProxy-End -->
+
+<!-- TurnOffFileHistory-Begin -->
+## TurnOffFileHistory
+
+<!-- TurnOffFileHistory-Applicability-Begin -->
+| Scope | Editions | Applicable OS |
+|:--|:--|:--|
+| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1903 [10.0.18362] and later |
+<!-- TurnOffFileHistory-Applicability-End -->
+
+<!-- TurnOffFileHistory-OmaUri-Begin -->
+```Device
+./Device/Vendor/MSFT/Policy/Config/System/TurnOffFileHistory
+```
+<!-- TurnOffFileHistory-OmaUri-End -->
+
+<!-- TurnOffFileHistory-Description-Begin -->
+<!-- Description-Source-ADMX -->
 This policy setting allows you to turn off File History.
 
-If you enable this policy setting, File History can't be activated to create regular, automatic backups.
+- If you enable this policy setting, File History cannot be activated to create regular, automatic backups.
 
-If you disable or don't configure this policy setting, File History can be activated to create regular, automatic backups.
+- If you disable or do not configure this policy setting, File History can be activated to create regular, automatic backups.
+<!-- TurnOffFileHistory-Description-End -->
 
-<!--/Description-->
-<!--ADMXMapped-->
-ADMX Info:
--   GP Friendly name: *Turn off File History*
--   GP name: *DisableFileHistory*
--   GP path: *Windows Components/File History*
--   GP ADMX file name: *FileHistory.admx*
+<!-- TurnOffFileHistory-Editable-Begin -->
+<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
+<!-- TurnOffFileHistory-Editable-End -->
 
-<!--/ADMXMapped-->
-<!--SupportedValues-->
-The following list shows the supported values:
+<!-- TurnOffFileHistory-DFProperties-Begin -->
+**Description framework properties**:
 
--   false (default) - allow File History
--   true  - turn off File History
-<!--/SupportedValues-->
-<!--Example-->
+| Property name | Property value |
+|:--|:--|
+| Format | int |
+| Access Type | Add, Delete, Get, Replace |
+| Default Value  | 0 |
+<!-- TurnOffFileHistory-DFProperties-End -->
 
-<!--/Example-->
-<!--Validation-->
+<!-- TurnOffFileHistory-AllowedValues-Begin -->
+**Allowed values**:
 
-<!--/Validation-->
-<!--/Policy-->
-<hr/>
+| Value | Description |
+|:--|:--|
+| 0 (Default) | Allow file history. |
+| 1 | Turn off file history. |
+<!-- TurnOffFileHistory-AllowedValues-End -->
 
-<!--/Policies-->
+<!-- TurnOffFileHistory-GpMapping-Begin -->
+**Group policy mapping**:
 
-## Related topics
+| Name | Value |
+|:--|:--|
+| Name | DisableFileHistory |
+| Friendly Name | Turn off File History |
+| Location | Computer Configuration |
+| Path | Windows Components > File History |
+| Registry Key Name | Software\Policies\Microsoft\Windows\FileHistory |
+| Registry Value Name | Disabled |
+| ADMX File Name | FileHistory.admx |
+<!-- TurnOffFileHistory-GpMapping-End -->
 
-[Policy configuration service provider](policy-configuration-service-provider.md)
\ No newline at end of file
+<!-- TurnOffFileHistory-Examples-Begin -->
+<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
+<!-- TurnOffFileHistory-Examples-End -->
+
+<!-- TurnOffFileHistory-End -->
+
+<!-- System-CspMoreInfo-Begin -->
+<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
+<!-- System-CspMoreInfo-End -->
+
+<!-- System-End -->
+
+## Related articles
+
+[Policy configuration service provider](policy-configuration-service-provider.md)