Hi ,
Thanks for reaching out to Microsoft Q&A.
To sign an Excel file with a certificate that “lives” in Azure, the easiest path (if policy permits) is:
- Export the code-signing certificate (.pfx) from Azure.
- Import it to your local Windows certificate store.
- Use Excel’s built-in signing feature to add the signature.
If that export step is blocked by security policy, you’ll have to resort to a remote signing process, which is not natively supported by Excel’s built-in UI and requires a more complex approach.
- Most common route: Export (or generate) the certificate from Azure, store it locally, then use Excel’s built-in “Add Digital Signature” functionality.
- If export of the private key is restricted, you’ll need a custom signing workflow where a tool communicates with Azure to sign the file. This isn’t straightforward for Office documents, and most of the Microsoft documentation for Azure Trusted Signing focuses on executables/scripts rather than Word/Excel docs.
The key point is that Azure holds your signing certificate and private key in the cloud, while Excel’s built-in “Add a digital signature” function expects a locally installed certificate (usually in the Windows certificate store).
- Azure Trusted Signing is primarily designed for code-signing workflows, especially executables or scripts, while keeping your private key secure in Azure.
- Excel’s “Add Digital Signature” feature expects a certificate in your personal certificate store on your Windows machine.
If the private key is only stored in Azure (i.e., you never exported a PFX to your local machine), Excel won’t see that certificate.
Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.