- The desktop application: per-user EXE or machine-wide MSI.
- The Outlook add-in: who receives it, and which manifest URL you deploy.
Desktop application: EXE or MSI
Choose the EXE if
- You are one person, or a small team, installing on your own computers.
- You want updates to arrive without IT doing anything.
- You are running a short trial on a few computers.
Choose the MSI if
- You deploy software centrally with Configuration Manager, Intune or Group Policy.
- You need to control when each update reaches users.
- Users work on shared computers such as Citrix or Remote Desktop Services. Keep the Http service feature installed; it provides cleaning for the Outlook add-in on multi-user systems.
If
ADDLOCAL is used on the MSI command line, it replaces the default features. List HttpListener explicitly whenever you use ADDLOCAL, or the Http service is not installed.Outlook add-in: who gets it
A Microsoft 365 administrator deploys the add-in from Integrated apps in the Microsoft 365 admin center. When you deploy it, you choose:
Only assign the add-in to people who already have the desktop application installed and licensed. Without it, the add-in cannot clean their attachments.
It can take up to 72 hours for the add-in to appear for newly assigned users, so allow for this in your plan. See Installing Draftable Clean Outlook Add-in.
Outlook add-in: latest or pinned manifest
If you pin the add-in, also plan desktop updates so the two stay a supported pair. Installing Draftable Clean Outlook Add-in gives the recommended desktop and add-in versions and the minimum desktop version the add-in needs, and the release log lists what each release changes. Updating the desktop application does not update a pinned add-in.
Settings: Group Policy, Intune or registry
Draftable Clean reads its settings from the Windows registry, so any tool that writes registry policy works.
Whichever you use, a policy takes priority over the user’s own setting. User Configuration policy takes priority over Computer Configuration policy. See Configuring preferences for your organization.
Quick decisions
- One person, own computer: EXE, enter the product key on first launch. Ask your Microsoft 365 administrator for the add-in.
- Small organization, no central software tools: EXE on each computer, add-in assigned to a pilot group first, then to everyone.
- Organization with Configuration Manager or Intune: MSI deployed silently, product key and settings deployed by policy, add-in assigned by group.
- Citrix or Remote Desktop Services: MSI with the Http service, policies under Computer Configuration where noted.
- Strict change control: MSI and a pinned add-in manifest, so you decide when each update ships.
Next steps
Rolling out to your users
Plan a pilot, expand in stages and tell users what to expect.
Group Policy configuration
Deploy the product key, profiles and send protection centrally.

