-
v4.25.0 Stable
released this
2025-12-23 14:19:24 +03:00 | 8 commits to main since this release📅 Originally published on GitHub: Tue, 23 Dec 2025 11:59:04 GMT
🏷️ Git tag created: Tue, 23 Dec 2025 11:19:24 GMTv4.25.0 - 2025-12-22
Benefactor Circle add-on users with mailboxes in Exchange Online should update to this version as soon as possible. Microsoft will begin changing roaming signature HTML processing shortly. Update as soon as possible to avoid potential negative impact on the parameters '
DeleteScriptCreatedSignaturesWithoutTemplate' and 'DeleteUserCreatedSignatures'.Variable replacement in Word is now much faster, but you must test your DOCX templates first. You must make sure that every character of a replacement variable in the template is formatted identically, or the replacement will fail. An example is given in the detailed changelog entry below.
Changed
Set-OutlookSignatures
- Switch to a new way of marking signatures created by Set-OutlookSignatures, while keeping compatibility with the existing one. This makes sure that the parameters '
DeleteScriptCreatedSignaturesWithoutTemplate' and 'DeleteUserCreatedSignatures', as well as similar features keep working when Microsoft changes roaming signature HTML processing. - Speed up replacing non-picture variables in DOCX (Word) templates by no longer replacing the variables in Word, but in the exported HTM file.
- You must make sure that every character of a replacement variable in the template is formatted identically, or the replacement will fail.
An example: When not all characters of '$CurrentUserGivenName$' are formatted identically, the string cannot be found in the final HTML signature created from the DOCX tempate file, which makes it impossible to replace the placeholder with the actual given name of the currently logged-on user. The slower Word variant used in earlier versions allowed for this, but always used the formatting of the first letter for the replaced text.
- You must make sure that every character of a replacement variable in the template is formatted identically, or the replacement will fail.
- Update '
MoveCSSInline' to fall back to non-inlined HTML in case of errors. - Update libphonenumber-csharp to v9.0.21.
- Update address-formatting datbase to 8444a0cc989042ebb21e6420f82bc4ded05a7fec.
- Rephrase the welcome screen.
- Make Graph API queries more resilient by retrying them five seconds after catching an error. This compensates for brief "hiccups" in the internal environment, on the Internet, and in Microsoft's data centers.
Benefactor Circle add-on
- Embed images when setting Outlook on the web signatures (classic and roaming), independent from the value of the '
EmbedImagesInHtml' parameter. This makes sure that images are also considered for default signatures that have not been created by Set-OutlookSignatures.
Outlook add-in (part of the Benefactor Circle add-on)
- Update @azure/msal-browser to v4.27.0.
Added
Set-OutlookSignatures
- Add shorter replacement variable names. To simplify signature design in limited space, shorter versions of replacement variables are automatically added. The original long names remain the default; short names are just an extra option. This applies to both default and custom variables.
Implementation logic and usage examples:- CurrentUserManager -> UM
Example: '$CurrentUserManagerVariableX$' is also available as '$UMVariableX$' - CurrentMailboxManager -> MM
Example: '$CurrentMailboxManagerVariableX$' is also available as '$MMVariableX$' - CurrentUser -> U
Example: '$CurrentUserVariableX$' is also available as '$UVariableX$' - CurrentMailbox -> M
Example: '$CurrentMailboxVariableX$' is also available as '$MVariableX$'
- CurrentUserManager -> UM
- Show a warning when a GPO (group policy object) setting takes precedence over the Outlook registry value set by the '
DisableRoamingSignatures' parameter. Warnings are also shown when a GPO (group policy object) setting takes precedence over the registry values 'Send Pictures With Document' (Outlook), 'DisableWarningOnIncludeFieldsUpdate' (Word), and 'AlertIfNotDefault' (Word). - Show a warning when a template contains an image in a format unusual for emails. The usual usual image formats supported by basically all email clients are JPG, JPEG, PNG, and GIF.
- Handle non-HTML-conformant 'img' tags with 'src' attributes starting with './' and '.'. While not HTML conformant, this format is intuitive and all major browsers support it.
- Add new FAQ 'How to add a calender link'
Benefactor Circle add-on
- Make the parameter '
DeleteScriptCreatedSignaturesWithoutTemplate' remove old signatures which can only be leftovers of switching from 'DisableRoamingSignatures false' to 'DisableRoamingSignatures true', even when these leftovers have not been created by Set-OutlookSignatures. - Show a warning when a signature has more than 30,000 characters (excluding images) and will therefore probably not work in Outlook add-in launch events and the taskpane.
- Add additional code to '
.\sample code\Create-EntraApp.ps1' ensuring that default configuration parameters, package providers, and package repositories are available. Force the use of PowerShell Gallery when searching for required packages.
Outlook add-in (part of the Benefactor Circle add-on)
- Show a warning in the taskpane of the Outlook add-in when the signature shown in the preview has more than 30,000 characters (excluding images) and will therefore probably not work in Outlook add-in launch events and the taskpane.
- Add to the taskpane a "Copy to clipboard" button for the currently previewed signature. This makes it easy to copy a signature to another email client and to overcome the 30,000 character limit.
- Add to the taskpane a "Copy to clipboard" button for the log output.
- Add to the taskpane a "Reload add-in" button for iOS and a link to instructions how to clear the add-in cache on all platforms.
- Add to the online documentation instructions how to 'Clear the Outlook add-in cache'.
Fixed
Set-OutlookSignatures
- Make sure the '
$Current[User|Manager|Mailbox|MailboxManager]PostalAddress$' not only contains line breaks when using DOCX templates, but also when using HTM templates.
Benefactor Circle add-on
- Fix warning message '
Signature file '.htm' not found. Outlook on the web HTML signature will be blank.', which leads to not setting the signature in classic Outlook on the web. This is only relevant for mailboxes hosted in Exchange on-prem when being accessed via Outlook on the web and when not using the Outlook add-in.
File hashes and code signing
- SHA256 hash of 'Set-OutlookSignatures_v4.25.0.zip': 480C3AD54FF7A04C3D15D6D528088745CEFEB1694985F0BEA4A8B69E69667991
- See 'hashes.txt' in 'Set-OutlookSignatures_v4.25.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'.
- 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 '
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Set-OutlookSignatures_v4.25.0.zip
0 downloads ·
2026-02-27 20:30:41 +03:00 · 32 MiB
- Switch to a new way of marking signatures created by Set-OutlookSignatures, while keeping compatibility with the existing one. This makes sure that the parameters '
mirror of
https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git
synced 2026-04-26 10:45:52 +03:00