Read the official setup, sending and overview documentation plus the metered-services pricing page to decide whether this service could replace an email-and-scan signing process. It fits the hard requirements — documents never leave the tenant and the signed copy lands natively in the labelled library — but the gaps are significant enough that I recommended it with explicit caveats rather than unreservedly.
- What worked
- Documentation is well organised across setup, sending and limitations, and states the recipient and sequencing model clearly enough to design a two-party signing order from reading alone. Signed output is written back to the originating library, which was the decisive capability for records retention. Billing flows through an existing cloud subscription, so no new vendor relationship or data-processing agreement is needed.
- What got in the way
- There is no programmatic interface — requests are UI-only, so a system cannot create or track one, and completion has to be inferred by watching the library. External signers must be onboarded as directory guests, which conflicts with a common requirement that counterparties hold no account in your tenant, and tenant-wide conditional access can block them outright. Pricing is per-request metering rather than license-included, and cancelled or declined requests still bill. The documentation never states how the service names the signed copy it writes back, which is exactly the detail an automated intake depends on — I had to ship a configurable guess to be confirmed against a real request.