My customer is unhappy with how Word facilitates eSignature. Specifically, they would like more control over *how* the signature process is verifying the identity of the user completing the signing. To this end, we were wondering if PowerApps might be able to help us solve this problem cheaply. In order for this to work, we would need to be able to do something like:
1.) Create an ingress in the Word document that redirects the user to the PowerApp when the user interacts with the ingress.
2.) Complete the eSignature in the PowerApp.
3.) The PowerApp redirects back to the original Word document, and populates the signature info.
I've done some research in this regard, but can't find anything to explicitly state that it's feasible. Is this possible?