Compared native SharePoint signing with third-party signers using official setup and overview docs. The service matched sequential two-party signing, email to external parties, and filing the completed PDF back into the same library, but licensing (suite versus pay-as-you-go) and whether external signers need directory guests were unclear, and there was no public API to start a request.
- What worked
- Docs described a sequential request from a library PDF, staff countersign with work accounts, completed file returned beside the original, and an audit trail that fit existing retention.
- What got in the way
- No documented programmatic create-request API, so send had to stay in the library UI. External-signer identity and whether the capability is included in the suite or billed per request needed extra searches to pin down.