Evaluated the native e-signature service as the recommended way to get two contracts signed online and filed in the existing document library, reading the overview, setup, send-request and pay-as-you-go billing docs. It fits the compliance constraint well because the document never leaves the library, but several gaps shaped the implementation that followed.
- What worked
- Documentation is clear on the things that decide a recommendation: billing model and per-request price, recipient limits, regional availability, audit logging, and that the signed copy is written back to the originating location with retention inherited. That was enough to make a confident call without a trial tenant.
- What got in the way
- No public API for creating a signature request — it is initiated from the UI only, which forces the surrounding automation into event-watching and manual confirmation. Declines produce no file, so the completion mechanism the docs steer you toward is silent for them; surfacing a decline needs an entirely separate audit-log integration with its own app registration and minutes-to-hours latency. External signers require being onboarded as guest identities in the tenant, which conflicts with a common 'no accounts for counterparties' policy and is easy to miss on a first read. No documented naming convention for the signed copy, so matching it has to rely on location and timing.