MicrosoftHello anduxen, The_Vard, Rakia_Segev,
It is important to know the answer regarding signing Excel VBA, Visio VBA, Word VBA, etc. files. Is there a favorable answer that supports signing Office files which contain VBA? Is there any special configuration for the signing to work correctly? Is this only possible with the Azure CLI? Is it possible with Windows PowerShell?
On a related topic, the three days certificate expiration can make the ISV look incompetent. The end user can and will observe that freshly purchased and installed software has an expired digital certificate. Has this been resolved?
MicrosoftVBA signing is not on our roadmap. So, we don’t have any other alternatives available. On Signing in general, we launched new integrations to expand the filetypes beyond the ones supported by Signtool: Simplifying signing integration for Trusted Signing | Microsoft Community Hub
3 day certificate validity is by design, to reduce the surface of impact. We encourage to timestamp the applications using our timestamping.
We have it in our public docs: Set up signing integrations to use Trusted Signing | Microsoft Learn
Trusted Signing certificates have a three-day validity, so time stamping is critical for continued successful validation of a signature beyond that three-day validity period. Trusted Signing recommends the use of Trusted Signing’s Microsoft Public RSA Time Stamping Authority: http://timestamp.acs.microsoft.com/.
