Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Legacy Feature

Availability in Web Add-in

Reason for Removal

Automatic categorisation of saved e-mails (“Saved” purple category)

Not supported

Office JS exposes no API to add or edit Outlook categories.

Real-time monitoring of incoming e-mails (background operation)

Not supported

Modern add-ins execute only when the task-pane is open; global “all-items” events aren’t exposed.

Processing while Outlook is minimised (VSTO background thread)

Not supported

Office JS code stops once the pane closes; persistent background threads are disallowed.

Automatic display / persistent pinning of the add-in pane

Partially supported — user must open the pane; *Pin* works only in Windows desktop Outlook, not in Outlook on the web

Office JS cannot programmatically open or pin the pane; OWA currently lacks a pinning feature.

MSI installer / GPO push deployment

Replaced — install via Microsoft 365 admin center → Settings → Integrated Apps or per-user sideloading

Modern add-ins are manifest-based web apps; Microsoft has deprecated MSI + GPO deployment for Outlook add-ins.

Bulk / silent configuration for multiple users (registry or script)

Not supported

Office JS settings are stored per mailbox and must be set interactively; no bulk-write API is available yet.

Registry-based silent configuration

Replaced with interactive Settings UI

Web add-ins cannot read Windows Registry; settings must live in roaming storage.

Direct opening of cases in Patricia Desktop

Partially supported — requires separate DocIntegrate 4.2.0 or later acting as a bridge

Office JS cannot launch local desktop apps; the bridge handles the protocol hand-off.

Support for Outlook 2007 / 2010 / 2013

Dropped

Microsoft allows modern add-ins only on Outlook 2016 (build 16.0.9126) and newer.

Direct COM access to Outlook object model

Not supported

COM interop is unavailable in Office JS; only the subset exposed by Office JS can be used.

Local log file `DocIntegrateOutlook.log`

Replaced with in-pane diagnostics

Browser sandbox prevents writing to the local file system; diagnostics surface inside the pane.

Support for non-HTTPS DMS endpoints

Dropped — HTTPS required

Office JS blocks insecure HTTP requests inside Outlook; mixed content is disallowed.

What this means for users

  • The add-in pane is not shown automatically. In specific versions of Outlook for Windows you can open it once and press *Pin* to keep it docked; in Outlook on the web and new versions of Outlook you must open it manually every time.
  • No more “Saved” colour labels in the mailbox list. Open the message and check the add-in pane for DMS status.
  • The add-in processes e-mails only while its pane is open. Switch away and processing pauses.
  • Installation for multiple users goes through *Microsoft 365 admin center → Integrated Apps* (or each user can install individually); MSI + GPO deployment is no longer supported.
  • Each user must configure their own DMS connection (gear-icon *Settings*); bulk pre-loading is not available today.
  • To open a case in Patricia Desktop you need *DocIntegrate 4.2.0 or newer* installed locally; the add-in hands off the request to that bridge.
  • The DMS URL must start with https:// — plain http:// endpoints are rejected.
  • Outlook ≤ 2013 is no longer supported. Those users should stay on the legacy add-in or upgrade Outlook.

...