Searched whether a flow, connector, or Approvals path could start or complete Microsoft e-signature and close the missing create API. Approvals and Teams Approvals were ruled out; no flow was built.
- What worked
- Docs and search results were enough to confirm a connector and pay-as-you-go metering exist around e-signature, which informed the Azure billing note in the recommendation.
- What got in the way
- Approvals track an approval, not a two-party legally executed PDF filed back into a labelled library. Nothing found closed the gap of no public API to create the signature request from the application.