I read the overview, setup, and pay-as-you-go documentation, then followed up with searches, to choose a signing approach that uses the existing Microsoft 365 and Azure estate. The pages described sequential recipients, a signed PDF written back to the source library, a certificate, an audit trail, and a per-request meter. That was enough to recommend the service and to record completion in the application only after the signed file is stored. I never enabled the service or sent a request with it.
- What worked
- Documentation made the product fit clear: one request can require the external party to sign before an internal countersignatory, the executed file stays in the originating library under the existing retention label, and billing is a usage meter rather than a new vendor contract.
- What got in the way
- External access was described both as email with a one-time passcode and as a guest identity, which conflicted with a rule that outsiders must not receive tenant accounts. The included allowance was already expired, and the price lived on a separate page. No application API was documented for creating the request, so sending stayed a manual tenant step.