How to configure labels and templates for different languages in Azure Information Protection
Applies to: Azure Information Protection
Instructions for: Azure Information Protection client for Windows
Although the default labels for Azure Information Protection support multiple languages, you must configure support for label names and descriptions that you specify. This configuration requires you to do the following:
Select the languages that your users use.
Export your current label names and descriptions to a file.
Edit the file to supply your translations.
Import the file back into your Azure Information Protection policy.
You can also configure templates for different languages when either of the following conditions apply. This configuration is appropriate if users or administrators need to see the current template name and description in their localized language.
The template was created in the Azure classic portal or by using PowerShell, and the template is not linked to a label by using the Select a predefined template protection setting.
You do not have a subscription that supports labels, so you can only create and manage templates in the Azure portal.
Select the languages that match your users' language setting for Office and Windows. These label names and descriptions then display in the Azure Information Protection bar in Office apps, and in the Classify and protect - Azure Information Protection dialog box, respectively. For more information about which language is chosen, see the [How the Azure Information Protection client determines the language to display](#how-the-azure-information-protection-client-determines-the-language-to- display) section on this page.
To configure labels and templates for different languages
If you haven't already done so, open a new browser window and sign in to the Azure portal. Then navigate to the Azure Information Protection blade.
For example, on the hub menu, click All services and start typing Information in the Filter box. Select Azure Information Protection.
From the Manage > Languages menu option: On the Azure Information Protection - Languages blade, select Add a new language for translation. Select the languages that you want to add and then select OK. You can either type the name of the language in the search box, or scroll through the list of available languages
Your selected languages now display on the Azure Information Protection - Languages blade:
To add another language, select Add a new language for translation and repeat the previous step.
Be sure to select the languages that your users have for Office, and for Windows. In some cases, this might require two different selections per computer.
If you change your mind about any language that you have added, select that entry from the list, and then click Remove.
When all the languages you want to support are listed, select the check box next to LANGUAGE NAME to select all the entries (or alternatively, select individual entries), and then click Export to save a local copy of the existing label names and descriptions to a file.
The downloaded file is named exported localization.zip and is saved in your local Downloads folder. It can also be accessed by selecting this file name on the status bar of the Azure portal.
Extract the files from exported localization.zip so that you have .xml files for each language that you selected for download.
Edit each .xml file: For each string within
<LocalizedText>tags, provide the translations that you want for each chosen language.
When you have edited each .xml file, create a new compressed (zipped) folder that contains these files. The compressed folder can have any name, but must have a .zip extension.
Tip: You don't have to wait until you've edited each language file that you've downloaded. Instead, you could roll out different languages in a phased mannor, by including in the .zip file a subset of the total files you downloaded. Then repeat steps 7 and 8 when you have completed the translations for more languages.
Return to the Azure Information Protection - Languages blade, and select Import. Note that if this option is unavailable, first clear the check box for LANGUAGE NAME or the check boxes for the individually selected languages.
When the import completes, the localized names and descriptions download to users.
You must repeat this procedure if you need to support a new language, create new labels, or you change the name or description of labels in the Azure portal.
How the Azure Information Protection client determines the language to display
When users download an Azure Information Protection policy that supports different languages, the language that users see for their label names and tooltips is determined by the following logic:
For the labels and tooltips that users see on the Azure Information Protection bar in Office apps:
When there is a direct match for the language of their Office app, label names and descriptions display in that language.
When there is no match for the language of their Office app, label names and descriptions display in the language you specified by default for all users. This language is typically English, which is the language used in the default policy.
For the labels and tooltips that users see when they use right-click to classify and protect files or folders:
When there is a direct match for the language of their operating system, label names and descriptions display in that language.
When there is no match for the language of their operating system, label names and descriptions display in the language you specified by default for all users. This language is typically English, which is the language used in the default policy.
When localized label names are not used
In the following scenarios, localized label (and sublabel) names are not used. For consistency across your tenant, the default language is always used for the following:
Client usage logs
PowerShell (output from Get-AIPFileStatus)
Document metadata and email headers
For more information about configuring the options that you can make for a label, and other settings for your Azure Information Protection policies, use the links in the Configuring your organization's policy section.