Request for Flexible Signature Placement in Outlook Replies Using Cloud-Based Add-ins

I work in IT at a medium-size law firm on Office 365, and we use Outlook Classic on firm laptops. We recently transitioned from Windows 10 laptops to new Windows 11 machines, and that's the point at which we changed the way our managed signatures insert. Originally, we had agents on each machine that interact with Outlook built-in local signatures, and now we use an Outlook plug-in from a cloud provider utilizing Office APIs to insert the signatures. Since the transition, we've been getting reports from users about signatures being inserted at the top of edited emails (rather than where the user has placed their cursor, at the bottom of the initial email in a chain for instance). This behavior is different than what they experienced when using Outlook local signature functionality. That combined with communications with our signature management provider (Exclaimer) about the coding of their app has led us to believe that Office APIs have different signature insertion logic than local signature insertion.

All that said, this change in behavior is particularly disruptive in workflows where attorneys or executives edit draft replies prepared by others. After finalizing the message and attempting to insert their signature at the bottom, the signature is automatically placed at the top—regardless of cursor placement. This does not occur when composing a brand-new email.

We understand this behavior is driven by the Office API and not by third-party signature tools like Exclaimer. However, we are requesting that Microsoft consider adding user-controlled flexibility to the API or Outlook itself, allowing signatures to be inserted at the cursor location for replies and forwards.

This change would restore functionality that was previously available with locally managed signatures and reduce friction for users who rely on precise formatting and message flow.

We appreciate Microsoft’s continued improvements to cloud-based tools and hope this request can be considered for future development.