Chose this as the signing service so finished PDFs stay in the existing document library with sequential external-then-internal signers. Overview and setup docs were readable, but licensing is pay-as-you-go rather than included in the suite, native library signing expected guest accounts the project forbids, and there was no confirmed public API to start a request. Implemented a client and tests against an assumed create-request call; never ran a live signing request.
- What worked
- The documented model matched sequential signing, staff countersign with existing identity, and writing the signed file back to the same library so activation can keep using library pointers.
- What got in the way
- External-only email signers conflicted with guest-account requirements. Creating a request from an app was poorly documented; the implementation had to isolate an unverified endpoint and leave tenant pay-as-you-go enablement outside the repo.