v4.24.0 - 2025-11-26
Changed
Set-OutlookSignatures
- Update libphonenumber-csharp to v9.0.19.
- Update MSAL.Net to v4.79.2.
Outlook add-in (part of the Benefactor Circle add-on)
- Update @azure/msal-browser to v4.26.2.
Added
Set-OutlookSignatures
- Make it much easier and more flexible to add account pictures to DOCX templates: Simply add a shape, position it "inline with text" and add the name of the picture replacement variable ('
$CurrentUserPhoto$', for example) to the alternative text. The shape is then automatically filled with the picuture you selected, giving you new graphical possibilities. The old way via "link and embed" is still possible, so you do not need to change your templates. - Update the function '
ConvertEncoding' to handle and try to automatically correct HTM template files which are not following the required format (UTF-8 without BOM, meta charset definition). - Add new FAQ: 'How to deploy a signature only once'
- Show a warning when a mailbox does not have the '
mail' attribute set, if the mail attribute does not match the primary SMTP address, or if multiple primary SMTP addresses are defined. Each of these misconfigurations will lead to errors in Set-OutlookSignatures and other applications, including Microsoft software. - Show a warning when DOCX templates are used and a non-picture replacement variable has more than 255 characters. Use a slower replacement method for these cases.
- Add a workaround for Microsoft Graph sending malformed IDs for mailbox elements, which in turn can not be used with the Graph API as they are malformed (an error with the code '
ErrorInvalidIdMalformed' can be found in the log file).
Outlook add-in (part of the Benefactor Circle add-on)
- Show '
CUSTOM_RULES_CODE' in the log output of the Outlook add-in. - Add a new configuration parameter: '
LAUNCHEVENTS_HOSTS_AND_PLATFORMS' allows for additional fine-grained control by defining which launch events are enabled on which hosts and platforms (and not just for mobile and non-mobile as Microsoft allows). See 'run_before_deployment.ps1' for details. - Add a workaround for New Outlook (and in some cases Outlook Web) behavior: In events, an existing signature is not replaced but added as additional text below the existing one. This can lead to many signatures shown, as the Outlook add-in is triggered by each added or removed recipient.
Fixed
Set-OutlookSignatures
- Update Graph authentication module to handle a change in the Windows 'dsregcmd /status' output, which can include keys like 'NgcSet' multiple times when additional work accounts have been added to Windows. This could make 'Integrated Windows Authentation without login hint' impossible (silent authentication would still work with the authentication broker method tried later, as all Windows versions in support which allow work accounts also support the broker method).
- Update country detection for '
FormatPhoneNumber' and 'Format-PostalAddress' to correctly handle null values and whitespace strings.
File hashes and code signing
- SHA256 hash of 'Set-OutlookSignatures_v4.24.0.zip': 162BFDB235BD84F99FE3E90F59000FD7200B611D62ADBA7D5B8FF01776A46385
- See 'hashes.txt' in 'Set-OutlookSignatures_v4.24.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 -Algorithm SHA256'.
- Compare these hashes with the output of '
- 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'.
- Check the signature with '