01
Coordinate-aware PDF signing
The browser-based PDF interface and PDF processing layer use different coordinate systems, requiring coordinate mapping to place signatures accurately on the generated document.
Microsoft · Enterprise · Financial Services
Enterprise E-Signature Platform
Secure document signing inside the Microsoft 365 tenant.
A SharePoint-native e-signature solution built for a financial-services environment where confidential documents could not be sent to third-party signing providers.
Microsoft 365SharePoint OnlineSPFxASP.NET CoreDocument Workflow
The Challenge
Signing sensitive documents without leaving the tenant.
A financial-services client needed employees and counterparties to digitally sign highly confidential documents. Compliance requirements prevented these documents from being sent to external signing platforms.
The signing workflow therefore needed to operate directly within the organisation’s Microsoft 365 / SharePoint environment, while maintaining a complete record of who signed, when, and from where.
Confidential Documents
Documents had to remain within the organisation's environment.
Microsoft 365 / SharePoint
The workflow needed to start from the document library users already worked in.
Complete Audit Trail
Every signing action needed to be traceable.
The Solution
A SharePoint-native signing experience.
I built an e-signature workflow directly into SharePoint. Users can select a document from the library, open the signing interface, place and assign fields, configure the signing order, and send the document for signature — without moving the document to an external signing platform.
SharePoint Library→Signing System→Signed PDF
- In-tenant document handling
- Drag-and-drop signature fields
- Sequential multi-signer workflow
- Secure, time-limited signing links
- PDF signature stamping
- Microsoft Graph notifications
- Signing progress and audit tracking
How It Works
From SharePoint document to signed PDF.
01
Select Document
The user selects a PDF from the SharePoint document library and starts Send for Signature.
02
Configure Signing
Signature, text and date fields are placed on the document and assigned to specific signers and signing order.
03
Secure Invitation
Each signer receives a secure, time-limited signing link.
04
Sign
The signer opens the document and completes the assigned fields using the browser-based signing interface.
05
Generate Signed PDF
The captured signature is embedded into the PDF at the configured field position.
06
Store & Audit
The completed document is saved back to the SharePoint library, with signing activity recorded for audit purposes.
Architecture
Designed around the Microsoft 365 environment.
The solution combines a SharePoint-native frontend with an ASP.NET Core API for secure document access, signing workflow, PDF processing and audit operations.
Azure AD / Authentication
Microsoft Graph Notifications
- 01SharePoint Online
- 02SPFx Signing Interface
- 03PnPjs / Microsoft Graph
- 04ASP.NET Core 8 API
- 05SQL Server / PDF Processing
- 06Signed PDF
- 07SharePoint Library
Security & Compliance
Built around the client's compliance constraints.
In-Tenant Documents
Documents remain within the Microsoft 365 / SharePoint environment.
Encrypted Signing Links
Signing tokens are encrypted and time-limited.
CONTROLLED ACCESS
Signing links provide controlled access to the assigned document.
Sequential Signing
The next signer is activated only after the previous signer completes their step.
Audit Trail
Signer email, IP address, timestamp and user-agent information are recorded.
MICROSOFT IDENTITY
Microsoft Graph and Azure AD integrate the workflow with the existing Microsoft 365 environment.
Technical Implementation
A full-stack solution inside the Microsoft ecosystem.
Frontend / SharePoint
SPFx 1.20 · React 17 · TypeScript · Fluent UI · PnPjs · PDF.js · HTML Canvas · Axios
Backend
ASP.NET Core 8 · Entity Framework Core 8 · SQL Server · PdfSharpCore · REST API
Microsoft 365
SharePoint Online · Microsoft Graph · Azure AD · Azure.Identity
Document Processing
PDF.js · PdfSharpCore · OpenXML
Engineering Details
The details that made the workflow work.
02
Sequential signing workflow
Each signer is activated only after the previous signer completes their step, with controlled signing tokens and Microsoft Graph notifications.
03
Token-based document access
Encrypted and expiring signing links provide controlled access throughout the signing process.
The Outcome
A complete signing workflow without third-party signing SaaS.
Confidential documents remained within the Microsoft 365 environment while users gained a complete multi-signer signing workflow directly from SharePoint.
In-Tenant
Documents remain within the Microsoft 365 environment.
Multi-Signer
Sequential signing supports multiple participants.
Audit Ready
Signing activity is recorded with relevant signer and access information.
Native Workflow
Users start the process directly from the SharePoint document library.
Have a complex enterprise workflow to build?
I build secure, production-ready systems around real business, compliance and technical constraints.