> ## Documentation Index
> Fetch the complete documentation index at: https://help.draftable.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring preferences with Microsoft Intune (Draftable Clean)

> Centrally configure Draftable Clean on cloud-managed Windows devices using Microsoft Intune — by importing ADMX administrative templates or deploying registry settings via OMA-URI configuration profiles.

This guide is for administrators managing Draftable Clean settings through **Microsoft Intune**. For on-premises Active Directory environments, see [Configuring preferences with Group Policy (Draftable Clean)](/hc/en-us/Draftable-Clean-articles/Configuring-preferences-with-Group-Policy-Draftable-Clean). For an overview of both methods, see [Configuring preferences for your organization](/hc/en-us/Draftable-Clean-articles/Configuring-preferences-for-your-organisation-Draftable-Clean).

## How Intune configures Draftable Clean

Draftable Clean reads its configuration from the **Windows Registry**. Intune can write those registry values in two ways:

### Option 1: Import ADMX templates

Import the Draftable Clean ADMX templates into Intune to manage settings from the Microsoft Intune admin center — the same settings experience as Group Policy, managed from the cloud.

See the [Microsoft documentation for importing custom ADMX templates](https://learn.microsoft.com/en-us/mem/intune/configuration/administrative-templates-import-custom).

The templates are found on an installed Draftable Clean machine at:

```
%LocalAppData%\DraftableClean\current\GroupPolicy
```

<Tip>
  If the `current` shortcut is not available, look for the folder with the highest version number under `%LocalAppData%\DraftableClean\` — the latest templates will be inside its `GroupPolicy` subfolder.
</Tip>

<Note>
  **v26.6.0 (June 2026)** ships updated ADMX/ADML templates. Import templates from a v26.6.0 or later installation before configuring policies in Intune. Ensure only one copy of each ADMX/ADML file is uploaded to Intune at a time — uploading duplicates with different names can cause configuration issues.
</Note>

Once imported, the same Computer Configuration and User Configuration settings available in Group Policy can be assigned to device or user groups in Intune. See [Available policy settings](/hc/en-us/Draftable-Clean-articles/Configuring-preferences-with-Group-Policy-Draftable-Clean#available-policy-settings) in the Group Policy guide for the full list.

<Warning>
  **Breaking change in v26.6.0 — Outlook add-in policy format.** If you previously deployed Outlook add-in settings as a single combined JSON value, migrate to the new **individual administrative template fields** introduced in v26.6.0. Re-import the updated templates and reconfigure default profile, send-protection, attachment summary, and profile-override settings separately. See [Configuring preferences with Group Policy](/hc/en-us/Draftable-Clean-articles/Configuring-preferences-with-Group-Policy-Draftable-Clean#available-policy-settings) for the field list and [v26.6.0 release notes](/hc/en-us/Draftable-Clean-articles/Release-logs-and-notes/Release-Notes-Draftable-Clean-June-2026-v26-6-0) for context.
</Warning>

### Option 2: Configure registry settings directly

Use Intune **Settings Catalog**, **OMA-URI**, or **Configuration Profiles** to write specific registry values. This does not require the ADMX templates and gives you direct control over individual registry keys.

Refer to the ADMX templates or registry on a configured machine for the correct key paths and value formats when building custom profiles.

## v26.6.0 administrator updates

Draftable Clean **v26.6.0 (June 2026)** adds enterprise controls that apply whether you use Intune or Group Policy:

* **Enforce must-clean metadata types across all profiles** — require specific metadata types to always be removed, regardless of which cleaning profile is active. Configure via the **Enforced cleaning rules** policy (Computer Configuration) when using imported ADMX templates, or the equivalent registry value when using OMA-URI.
* **Outlook add-in lockdown** — lock the default profile, send-protection behaviours, attachment summary format, and per-attachment profile override. v26.6.0 exposes these as **individual policy fields** rather than a single JSON blob.
* **Updated ADMX templates** — **DomainRules** and **AddInSettings** policies are surfaced explicitly for import into Intune.
* **MSI prerequisite change** — the machine-wide MSI no longer requires .NET 10 Desktop Runtime as a separate prerequisite check.

See the [v26.6.0 release notes](/hc/en-us/Draftable-Clean-articles/Release-logs-and-notes/Release-Notes-Draftable-Clean-June-2026-v26-6-0) for the full list of changes.

### Locking Outlook add-in defaults via Intune

When you deploy add-in settings through imported administrative templates, each Outlook add-in field can be set as a fixed value that end users **cannot override** from **Settings > Add-In** in the desktop application. Where a field is left unset by policy, the user's own setting applies. See [Priority of settings](/hc/en-us/Draftable-Clean-articles/Configuring-preferences-for-your-organisation-Draftable-Clean#priority-of-settings).

### Admin cleaning profiles via Intune

The **Configure admin cleaning profiles** policy deploys administrator-managed cleaning profiles that users cannot edit. The policy value is a JSON string representing the profile collection.

<Note>
  The visual **admin profile editor** (`DraftableClean.exe --admin-profile-editor`) is designed for the Group Policy copy-paste workflow. Intune administrators can still use the editor on a reference machine to build or update the JSON, then deploy that value through an imported administrative template or a custom registry/OMA-URI profile. See [Configuring admin cleaning profiles](/hc/en-us/Draftable-Clean-articles/Configuring-preferences-with-Group-Policy-Draftable-Clean#configuring-admin-cleaning-profiles) for the editor workflow.
</Note>

### Enforcing must-clean metadata types

The **Enforced cleaning rules** policy requires that specified metadata types are always removed — across built-in profiles, admin profiles, and any custom profiles users create later. The policy value is JSON; the available metadata types match the [Supported Metadata Types](/hc/en-us/Draftable-Clean-articles/Supported-Metadata-Types) reference.

## Deploying Draftable Clean with Intune

Intune can also deploy the Draftable Clean desktop application itself (required for the Outlook add-in). See [Deployment options](/hc/en-us/Draftable-Clean-articles/Deployment-options) for installer types, then add the MSI or EXE as a Windows app in Intune following [Microsoft's app deployment documentation](https://learn.microsoft.com/en-us/mem/intune/apps/apps-windows-10-app-deploy).

Configure application settings in a separate configuration profile after the app is deployed.

## Need help?

If you need assistance configuring Draftable Clean with Microsoft Intune, contact the Draftable team at [support@draftable.com](mailto:support@draftable.com).