Release v4.29.0

v4.29.0 - 2026-06-11

Code signing certificate updated, annual rotation enabled:

• Our partner ExplicIT Consulting has renewed the enterprise validated (EV) certificate being used to digitally sign the code of Set-OutlookSignatures and the Benefactor Circle add-on. Thanks for this donation!
• You may need to update the configuration of your endpoint security software (AppLocker, Defender, CrowdStrike…) if it is locked to the old certificate.
• To comply with new industry-wide Certificate Authority (CA) guidelines, this certificate will now be rotated every year moving forward.

Set-OutlookSignatures

Security

• Append ExplicIT's code signing certificate instead of replacing existing certificates. This way, original code signing certificates from Microsoft, the .NET Foundation, and others are kept intact.

Additions

• Add a Security questionnaire section to the documentation, with a basic set of questions and answers for security reviews.
• Add blog articles:
  • Goodbye Rollout Panic: How to Test Outlook Signatures & Out-of-Office Notes Without Accessing Live Mailboxes
  • Hot Tips for Cool Signatures: How to Make Your Summer Campaigns Shine

Changes

• Refactor registry checks so that the transcript does not log a try/catch error when the key (folder) of a value exists, but not the value itself.
• Update libphonenumber-csharp to v9.0.32.
• Update MSAL.Net to v4.84.2.
• Use an updated code signing certificate to sign PowerShell and DLL files.
  • You may need to update the configuration of your endpoint security software (AppLocker, Defender, CrowdStrike…) if it is locked to the old certificate.
  • To comply with new industry-wide Certificate Authority (CA) guidelines, this certificate will now be rotated every year moving forward.
• Change the behavior of the INI file parameter OutlookSignatureName so that it does not overwrite signature names already used for higher priority mailboxes.

Fixes

• Make assembly resolver work with DLL files that have not been unblocked, therefore still have the "mark of the web" and can not be loaded. (#155)
• Make sure the heading pane right of the divider of sample code\IniEditor.html and https://set-outlooksignatures.com/inieditor is visible even when scrolling.
• Load Word Interop DLL before actually starting Word and running automation tasks. This early-being avoids possible errors due to late-binding.

Benefactor Circle add-on

Additions

• Add a Security questionnaire section to the documentation, with a basic set of questions and answers for security reviews.

Changes

• Use an updated code signing certificate to sign PowerShell and DLL files.
  • You may need to update the configuration of your endpoint security software (AppLocker, Defender, CrowdStrike…) if it is locked to the old certificate.
  • To comply with new industry-wide Certificate Authority (CA) guidelines, this certificate will now be rotated every year moving forward.

Outlook add-in (part of the Benefactor Circle add-on)

Changes

• Update @azure/msal-browser to v5.13.0.
• Update the Logging and troubleshooting section in the documentation.

File hashes and code signing

• SHA256 hash of 'Set-OutlookSignatures_v4.29.0.zip': 0ABAFF3B64A1F6B57E4FCB0B75F39554236A1EC666EE09131B18CEFA795DF7BA
• See 'hashes.txt' in 'Set-OutlookSignatures_v4.29.0.zip' for the hash value of every single file in the release.
  • Compare these hashes with the output of 'Get-ChildItem -Recurse | Get-FileHash -LiteralPath $_.FullName -Algorithm SHA256'.
• Files are code signed with ExplicIT Consulting's Extended Validation (EV) certificate.
  • Check the signature with 'Get-ChildItem -Include '*.ps*1', '*.dll' -Recurse | Get-AuthenticodeSignature'.