--- title: Policy CSP - ApplicationDefaults description: Learn about various Policy configuration service providers (CSP) - ApplicationDefaults, including SyncML, for Windows 10. ms.author: vinpa ms.topic: article ms.prod: w10 ms.technology: windows author: vinaypamnani-msft ms.localizationpriority: medium ms.date: 09/27/2019 ms.reviewer: manager: aaroncz --- # Policy CSP - ApplicationDefaults
## ApplicationDefaults policies
ApplicationDefaults/DefaultAssociationsConfiguration
ApplicationDefaults/EnableAppUriHandlers

**ApplicationDefaults/DefaultAssociationsConfiguration** |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy allows an administrator to set default file type and protocol associations. When set, default associations are applied on sign in to the PC. The association file can be created using the DISM tool (dism /online /export-defaultappassociations:appassoc.xml). Then, it needs to be base64 encoded before being added to SyncML. If policy is enabled and the client machine is having Azure Active Directory, the associations assigned in SyncML are processed and default associations are applied. ADMX Info: - GP Friendly name: *Set a default associations configuration file* - GP name: *DefaultAssociationsConfiguration* - GP element: *DefaultAssociationsConfiguration_TextBox* - GP path: *File Explorer* - GP ADMX file name: *WindowsExplorer.admx* To create the SyncML, follow these steps:
  1. Install a few apps and change your defaults.
  2. From an elevated prompt, run "dism /online /export-defaultappassociations:appassoc.xml"
  3. Take the XML output and put it through your favorite base64 encoder app.
  4. Paste the base64 encoded XML into the SyncML
Here's an example output from the dism default association export command: ```xml 101 chr text/plain ./Vendor/MSFT/Policy/Config/ApplicationDefaults/DefaultAssociationsConfiguration PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxEZWZhdWx0QXNzb2NpYXRpb25zPg0KICA8QXNzb2NpYXRpb24gSWRlbnRpZmllcj0iLmh0bSIgUHJvZ0lkPSJBcHBYNGh4dGFkNzdmYmszamtrZWVya3JtMHplOTR3amYzczkiIEFwcGxpY2F0aW9uTmFtZT0iTWljcm9zb2Z0IEVkZ2UiIC8+DQogIDxBc3NvY2lhdGlvbiBJZGVudGlmaWVyPSIuaHRtbCIgUHJvZ0lkPSJBcHBYNGh4dGFkNzdmYmszamtrZWVya3JtMHplOTR3amYzczkiIEFwcGxpY2F0aW9uTmFtZT0iTWljcm9zb2Z0IEVkZ2UiIC8+DQogIDxBc3NvY2lhdGlvbiBJZGVudGlmaWVyPSIucGRmIiBQcm9nSWQ9IkFwcFhkNG5yejhmZjY4c3JuaGY5dDVhOHNianlhcjFjcjcyMyIgQXBwbGljYXRpb25OYW1lPSJNaWNyb3NvZnQgRWRnZSIgLz4NCiAgPEFzc29jaWF0aW9uIElkZW50aWZpZXI9Imh0dHAiIFByb2dJZD0iQXBwWHEwZmV2em1lMnB5czYybjNlMGZicWE3cGVhcHlrcjh2IiBBcHBsaWNhdGlvbk5hbWU9Ik1pY3Jvc29mdCBFZGdlIiAvPg0KICA8QXNzb2NpYXRpb24gSWRlbnRpZmllcj0iaHR0cHMiIFByb2dJZD0iQXBwWDkwbnY2bmhheTVuNmE5OGZuZXR2N3RwazY0cHAzNWVzIiBBcHBsaWNhdGlvbk5hbWU9Ik1pY3Jvc29mdCBFZGdlIiAvPg0KPC9EZWZhdWx0QXNzb2NpYXRpb25zPg0KDQo= ```
**ApplicationDefaults/EnableAppUriHandlers** |Edition|Windows 10|Windows 11| |--- |--- |--- | |Home|No|No| |Pro|Yes|Yes| |Windows SE|No|Yes| |Business|Yes|Yes| |Enterprise|Yes|Yes| |Education|Yes|Yes|
[Scope](./policy-configuration-service-provider.md#policy-scope): > [!div class = "checklist"] > * Device
This policy setting determines whether Windows supports web-to-app linking with app URI handlers. Enabling this policy setting enables web-to-app linking so that apps can be launched with an http(s) URI. Disabling this policy disables web-to-app linking and http(s) URIs will be opened in the default browser instead of launching the associated app. If you don't configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot. ADMX Info: - GP Friendly name: *Configure web-to-app linking with app URI handlers* - GP name: *EnableAppUriHandlers* - GP path: *System/Group Policy* - GP ADMX file name: *GroupPolicy.admx* This setting supports a range of values between 0 and 1.