SharePoint eSignature Gets a Major Upgrade with Free Text Fields

SharePoint eSignature is getting a big upgrade.

I think SharePoint eSignature is a great option, but up until now it has had a really significant functional limitation versus a competitor like DocuSign, it was limited to only three very specific fields to collecting information from signers. If you needed something extra - as many signing scenarios do - you'd be out of luck with this solution.

Now though, rolling out between October and January, eSignature requests created in Word will be able to include free text fields. For the first time you'll be able to define what you want to capture on your request outside of the three provided default fields.

I'll link to my video summarizing SharePoint eSignature in the comments, but this is a quick overview of where you might, or might not, find this feature attractive:
✅ If you have a low volume of signature requests distributed across a team, SharePoint eSignature's per document versus per user pricing can be attractive versus mainstream competitors.
✅ If you want signature requests fully integrated into Microsoft 365 (or you can also optionally integrate Adobe Sign or DocuSign similarly if you are licensed for these)
❌ You require more complicated templating or signing scenarios than eSignature can handle, platforms like DocuSign are much more sophisticated here.
❌ You need eSign automation. Right now SharePoint eSignature requires user intervention to work. I hope bringing this tool to Power Automate is at the top of their product roadmap (nothing on the M365 Roadmap about this right now).

Until the end of 2025 you can try SharePoint eSignature out for free if you have PAYG activated in your tenant. See the link in the comments for more info.

See MC1152319 in the Microsoft Message center for more info.
Have you tried SharePoint eSignature yet? Does this new feature make it fit better to your situation? Or are there other features you're still waiting for?

First posted on Linkedin on 09/15/2025 -> View Linkedin post here