Used Learn pages and licensing searches to pick an in-estate signing path that returns signed PDFs to the existing document library and bills per request on the current Azure subscription. There is no API to start a request, one send-request doc returned 404, and external signers appear to need directory guest access. The app was wired around stamps and callbacks instead of calling the service.
- What worked
- Docs were clear that this is a pay-as-you-go document-processing meter, that recipients can be asked to sign in order, and that the signed file can land back in the SharePoint library where the unsigned PDF started.
- What got in the way
- It is not part of the E5 licence despite that being the starting assumption. Creating a request over Graph is not supported. The send-request Learn page was missing. External signers needing guest accounts conflicted with a no-tenant-account rule, so sending had to be pushed to a flow outside the app.