I used Microsoft Learn overview, setup, pay-as-you-go, and review pages, plus follow-up searches, to judge native eSignature for ordered external signing and library write-back. That was enough to recommend it and to limit the application to recording recipients, timestamps, and the returned file pointer. I did not install a client, call the service, or enable it in a tenant.
- What worked
- The pages confirmed that an external recipient can sign from an email link without a tenant account, that recipients can sign in order, that the finished PDF is written back to the library folder where the request started, and that requests are billed pay-as-you-go. Those points matched the storage, identity, and activation constraints already stated in the project.
- What got in the way
- Licensing, audit evidence, reminders, residency, and whether requests can be created through a management API each needed a separate search. Pay-as-you-go billing only became clear after the overview and billing pages were read together. Enabling the provider and allowing the signing link through conditional access are tenant administrator steps, so the repository never reached a live signing flow.