Message Classifications allow users to assign a tag to a message, such as marking it confidential to the company. These can be used on-premises, and also in Exchange Online.
After connecting to Exchange Online PowerShell you can use the following command to list message classifications in place:
To add a new classification, use the following cmdlet, subsitution the Name (used in the EAC or PowerShell, but not seen by users), DisplayName (seen in the drop-down list) and SenderDescription (shown in Outlook or OWA after selecting the classication):
|New-MessageClassification -Name <Name> -DisplayName “Display Name” -SenderDescription “Shown to users”|
After creating the new Message Classification, end-users will see this within Outlook Web App.
To allow this to show in Outlook 2007, 2010 or 2013 export the Message Classifications as an XML file using the following script (from Exchange 2013):
$classifications = Get-MessageClassification
You then need to deploy the MessageClassifications.xml file to workstations. You can use Group Policy preferences to do this. A recommendation is to deploy the file using Computer preferences to a location all users on each machine can access, for example C:\Users\Public\MessageClassifications.xml
Finally deploy registry settings to each user, again – easily accomplished in minutes using Group Policy Preferences. If you prefer to use a .REG file to test or deploy, use the following settings (which will apply to Outlook 2007, 2010 and 2013):
Windows Registry Editor Version 5.00
After deploying the registry settings, users will see the Message Classification drop-down list in Outlook clients, in addition to OWA.
You can then perform actions based on Message Classifications using Transport Rules.