Read the overview, setup, send-requests and consumption-billing documentation to decide whether the tenant-native signing service fit a requirement for external signers, in-tenant storage, retention labels and an audit trail. The docs answered every question I needed to commit to a recommendation, but the capability gaps are material.
- What worked
- Documentation was unusually direct about the things that decide an evaluation: per-request pricing and how it is metered, recipient limits, that external recipients sign with an emailed code rather than an account, signing order for counter-signing, that the signed copy is written back to the originating folder so retention labels apply by construction, and that signing activities land in the compliance audit log. Being tenant-native also removed a whole data-residency conversation.
- What got in the way
- There is no programmatic API to create a signature request, so an application cannot initiate signing — a person has to start it from the library UI, and the application can only learn about completion indirectly by watching the library. Enablement also requires admin-center steps, a consumption billing setup and a separate permission grant, none of which can be scripted from the app side, and the pricing is explicitly outside the usual enterprise commitment arrangements.