Treated the existing agreements library as the only allowed home for unsigned and executed PDFs. Designed signing so requests start from a file already in that library and the finished PDF is written back to the same folder. Did not operate the service directly; the app stores pointers and uses Graph to resolve drive items.
- What worked
- The library-as-system-of-record constraint was straightforward to map onto eSignature’s round-trip model. Activation could stay blocked until an executed file pointer existed.
- What got in the way
- The app still cannot read or write library bytes itself; Graph site permissions and the signing service must be enabled on the site before the designed path works in production.