Similar to Word, there is also a template file for e-mails in Outlook. This Outlook / Mail template can be easily distributed with Intune and a PowerShell Script or Win32 App. Unfortunately, not all settings are included in it. In addition, there are some registry entries that are required for the standard font etc.

How you can distribute the "Normal.dotm" for Word I show you here.

Table of Contents

PowerShell to distribute the Outlook template

The script consists of two parts. In the first, the registry entries for the standard fonts for new mails and replies are set. In the second, I distribute the "NormalEmail.dotm" to also have the format templates under "Format Text".

To start, download the whole package using the button above.

Unfortunately, the writing (stationery and fonts) is only activated for users if Outlook was already open.
If you want to make sure that the font is always up-to-date for all users, I recommend creating a Proactive Remediations package for it.

In the first lines you have to specify the desired fonts and sizes. These are in a binary format. But don't worry, you can simply click together the settings in Outlook and then insert the variables in the script.
To do this, navigate in Outlook under "File > Options > Mail > Stationery and Fonts".
Here you can now prepare the settings.
Please do not use any special / custom fonts. These are displayed unformatted for external recipients.

You can now find the settings you have made in the Registry Editor under:

Registry, MailSettings

However, you cannot simply copy them out here. I have put together the following PowerShell commands for you. Select this and copy the output into the "install.ps1" in the "Font Settings Outlook".
Tipp: Execute each line individually and keep the overview better.

$($(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\MailSettings").ComposeFontComplex -join ",")
$($(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\MailSettings").ComposeFontSimple -join ",")
$($(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\MailSettings").ReplyFontComplex -join ",")
$($(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\MailSettings").ReplyFontSimple -join ",")
$($(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\MailSettings").TextFontComplex -join ",")
$($(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Common\MailSettings").TextFontSimple -join ",")Code language: PowerShell (powershell)

Here is an example of executing the first line. You then copy the output into the variable $ComposeFontComplex between the two "".

# Font Settings Outlook
$ComposeFontComplex = "60,104,116,109,108,62...."
$ComposeFontSimple = ""
$MarkCommentsWith = ""
$ReplyFontComplex = ""
$ReplyFontSimple = ""
$TextFontComplex = ""
$TextFontSimple = ""Code language: PowerShell (powershell)

The easiest way to prepare the "NormalEmail.dotm" is in Word. You can download my version from GitHub or rename an existing "Normal.dotm" to "NormalEmail.dotm" and customize it to suit you.
You don't have to change anything in the script to configure this file, just put it in the package and create a Win32 app from it.

With the "NormalEmail.dotm" you set the format templates in Outlook:

Demo-E-Mail, Styles

Create and upload Win32 app

As soon as you have filled in the registry keys and put your "NormalEmail.dotm" file in the folder, you can create a Win32 app from the whole thing. To do this, proceed as follows:

  1. Download the current "Microsoft Win32 Content Prep Tool" down.
  2. Open the tool and enter the following variables:
    1. Path to the folder, for example: C:\GitHub\scloud\Normal mail template
    2. install.ps1
    3. Path to the folder, for example: C:\GitHub\scloud\Normal mail template
Create Win32 App for NormalEmail.dotm

You will then find the finished win32 app with the name "install.intunewin" in the specified folder and can use it in the Microsoft Endpoint Manager under "Apps > Windows +Add" upload.

In the first step you enter at least a name, a description and a publisher. In the second you have to enter the following installation and deinstallation command.
It is also important that the installation context "users" is selected.

install command%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\install.ps1
uninstall command%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\uninstall.ps1

In the "Requirements" make sure that your managed operating systems are supported. There is no special requirement apart from Office 2016.

With the "Detection Rule" you can upload the prepared "check.ps1" file from my template.

We have no dependencies and only have to assign the package to the desired group at the end. If you wait a bit or install the app via Company Portal, the user has received the default Outlook template via Intune and you can update or delete it at any time.

Proactive Remediations for "Stationery and Fonts"

If Win32 was installed on a PC before Outlook was first started, the "Stationery and Fonts" values will be overwritten. To make sure the fonts are correct, you can create a Proactive Remediations package. As usual, I have put the template for you on GitHub.

Fill in the registry values in the detection and remediation script as described above in the WIn32 app and distribute the package user-based.

Beispiel Font Settings Outlook
Example of Font Settings (RegKeys)

Distribute the update of the Outlook template

If you want to update your template, you can do this by adjusting the "NormalEmail.dotm" and / or the registry entries and adjusting the version in the second line of "install.ps1" and "check.ps1". You can then repackage the Win32 app and upload it to the existing app in the Endpoint Manager. Don't forget to re-upload the "check.ps1" too!