New portal MSIs (v26.2+) are self-contained — the plugins ship inside the installer. To switch on a customer's Report Message button you add one additive backend record. This is purely additive — never edit or delete existing rows; add-ins already installed in the field keep working untouched.

The bundled MSI reports bootstrap version 21.1.10.1, so the customer needs a DcoyaOutlookRibbonBootstraper Generic Plugin row at that version:

1. Django admin → Dcoya → Generic plugins; filter by the customer.
2. Is there a DcoyaOutlookRibbonBootstraper row at version 21.1.10.1 for this customer? If yes → done, nothing to do.
3. If not: open any existing DcoyaOutlookRibbonBootstraper row for that same customer (e.g. the 26.5.20.2 one) → "Save as new" → change version to 21.1.10.1 → keep everything else as-is → Save. (Copying the customer's own row carries the correct backend host across.)
4. Done. No AdvantivePolicy, no EFS, no server restart — the plugins ship inside the MSI and load via the signature whitelist.

⚠️ Verify the backend host: the new row's settings must reference the customer's correct host — EU customers = https://api.dcoyacloud.com (NOT always api-eu.goninjio.com).

📘 HOW-TO: Release a new Outlook Add-in version  ·  🛠️ Build & Code-Signing Runbook