Anavem
Languagefr
How to Change Default Mailbox Language in Microsoft Outlook and Exchange

How to Change Default Mailbox Language in Microsoft Outlook and Exchange

Learn to change default mailbox language for single or multiple users in Microsoft Outlook using web interface and PowerShell commands for Exchange Online and on-premises environments.

April 15, 2026 12 min
easyoutlook 6 steps 12 min

Why Change Default Mailbox Language in Outlook and Exchange?

Managing mailbox language settings is a fundamental administrative task in Microsoft Exchange environments. Whether you're supporting a multinational organization or helping users work in their preferred language, understanding how to change default mailbox language settings ensures users can work efficiently in their native language.

The default mailbox language affects several key areas: the display language for system folders (Inbox, Sent Items, Drafts), date and time formats, and the overall interface language in Outlook. When users work in different languages than the system default, they often struggle with folder names and interface elements that don't match their expectations.

What Methods Are Available for Changing Mailbox Language?

Microsoft provides two primary methods for changing mailbox language settings. The Outlook web interface offers a user-friendly approach perfect for individual users or small-scale changes. This method works seamlessly across both Exchange Online and on-premises environments without requiring administrative privileges beyond the user's own mailbox.

PowerShell commands provide the administrative power needed for bulk operations and enterprise-scale deployments. Using the Set-MailboxRegionalConfiguration cmdlet, administrators can efficiently change language settings for single users, specific groups, or entire organizations. This approach is essential when onboarding users from different regions or implementing organization-wide language standardization.

How Do Exchange Online and On-Premises Environments Differ?

While the core functionality remains consistent, Exchange Online and on-premises environments require slightly different approaches. Exchange Online uses the Connect-ExchangeOnline PowerShell module and requires internet connectivity for remote management. On-premises Exchange uses the local Exchange Management Shell and operates directly against your internal Exchange servers.

Both environments support the same language codes and regional settings, ensuring consistent user experiences regardless of your Exchange deployment model. The verification steps and troubleshooting procedures apply universally, making this knowledge transferable across different Exchange architectures.

Implementation Guide

Full Procedure

01

Change Language Using Outlook Web Interface

The easiest method for changing a single user's mailbox language is through the Outlook web interface. This method works for both Exchange Online and on-premises environments.

Sign in to Outlook on the web using your credentials. Once logged in, look for the three dots menu icon in the top navigation bar and click it.

From the dropdown menu, select Settings. This opens the basic settings panel. To access the full language configuration options, click View all Outlook settings at the bottom of the settings panel.

In the settings interface, navigate to General in the left sidebar, then click Language and time. Here you'll find the language dropdown menu where you can select your desired language from the available options.

Select your preferred language from the dropdown menu. Make sure to check the box labeled Rename default folders so their names match the specified language. This ensures that system folders like Inbox, Sent Items, and Drafts will be renamed to match your selected language.

Click Save to apply the changes. The language change takes effect immediately without requiring a restart of Outlook.

Pro tip: If your preferred language is already selected but folders aren't updating, select a different language first, save, then switch back to your preferred language and save again.

Verification: Check that the interface language has changed and that default folders now display in your selected language. Navigate through different sections of Outlook to confirm the change has been applied consistently.

02

Connect to Exchange Online via PowerShell

For bulk operations or when you need to change language settings for multiple users, PowerShell provides a more efficient approach. First, you need to establish a connection to Exchange Online.

Open PowerShell as an administrator. You can do this by right-clicking on the PowerShell icon and selecting "Run as administrator".

Connect to Exchange Online using the following command:

Connect-ExchangeOnline

This command will prompt you to sign in with your Microsoft 365 administrator credentials. Enter your credentials when prompted. The connection process may take a few moments to complete.

Once connected, you'll see a confirmation message indicating successful connection to Exchange Online. You can now run Exchange Online PowerShell cmdlets.

Warning: Ensure you have the necessary administrative permissions before attempting to connect. Global Administrator or Exchange Administrator roles are typically required for mailbox configuration changes.

Verification: Run the following command to confirm your connection is working:

Get-OrganizationConfig | Select-Object Name

This should return your organization's name, confirming the connection is active.

03

Change Language for a Single User with PowerShell

Once connected to Exchange Online, you can change the mailbox language for individual users using the Set-MailboxRegionalConfiguration cmdlet.

Use the following command structure to change language settings for a single user:

Set-MailboxRegionalConfiguration -Identity "user@domain.com" -Language "language-code" -LocalizeDefaultFolderName -DateFormat "d-M-yyyy" -TimeFormat "HH:mm"

Here's a practical example changing a user's language to Dutch:

Set-MailboxRegionalConfiguration -Identity "anne.green@company.com" -Language "nl-NL" -LocalizeDefaultFolderName -DateFormat "d-M-yyyy" -TimeFormat "HH:mm"

The -LocalizeDefaultFolderName parameter ensures that default folders (Inbox, Sent Items, Drafts, etc.) are renamed to match the specified language. The -DateFormat and -TimeFormat parameters set the regional date and time display formats.

Common language codes include:

  • nl-NL for Dutch (Netherlands)
  • de-DE for German (Germany)
  • pt-BR for Portuguese (Brazil)
  • da-DK for Danish (Denmark)
  • ja-JP for Japanese (Japan)
  • fr-FR for French (France)
  • es-ES for Spanish (Spain)
Pro tip: You can use $null for DateFormat and TimeFormat parameters to use the default formats for the selected language: -DateFormat $null -TimeFormat $null

Verification: Check the configuration was applied correctly:

Get-MailboxRegionalConfiguration "anne.green@company.com"
04

Change Language for Multiple Users with PowerShell

When you need to change language settings for multiple users or your entire organization, PowerShell provides efficient bulk operations.

To change the language for all mailboxes in your organization, use this command:

Get-Mailbox -ResultSize Unlimited | Set-MailboxRegionalConfiguration -Language "nl-NL" -LocalizeDefaultFolderName -DateFormat "d-M-yyyy" -TimeFormat "HH:mm"

This command retrieves all mailboxes and applies the language change to each one. The -ResultSize Unlimited parameter ensures all mailboxes are included, not just the default 1000.

For more targeted bulk operations, you can filter specific users. For example, to change language only for users in a specific department:

Get-Mailbox -Filter "Department -eq 'Sales'" | Set-MailboxRegionalConfiguration -Language "de-DE" -LocalizeDefaultFolderName

If you have a CSV file with specific users to update, you can process them in batch:

$users = Import-CSV "C:\temp\users.csv" -Encoding UTF8
Foreach($user in $users) {
    Set-MailboxRegionalConfiguration -Identity $user.Email -Language "de-DE" -DateFormat $null -TimeFormat $null -LocalizeDefaultFolderName
}

Your CSV file should have a column named "Email" containing the user email addresses.

Warning: Bulk operations affect many users simultaneously. Test with a small group first and ensure you have proper backups before running organization-wide changes.

Verification: Check a sample of updated mailboxes to confirm the changes:

Get-Mailbox -ResultSize 5 | Get-MailboxRegionalConfiguration | Select-Object Identity, Language
05

Configure Language Settings for Exchange On-Premises

For Exchange on-premises environments, the process is similar but uses the Exchange Management Shell instead of connecting to Exchange Online.

Open the Exchange Management Shell as an administrator. You can find this in the Microsoft Exchange Server program group in your Start menu.

The Exchange Management Shell automatically loads the necessary Exchange cmdlets and connects to your local Exchange server. No additional connection command is required.

Use the same Set-MailboxRegionalConfiguration cmdlet for on-premises environments:

Set-MailboxRegionalConfiguration -Identity "DOMAIN\username" -Language "nl-NL" -LocalizeDefaultFolderName -DateFormat "d-M-yyyy" -TimeFormat "HH:mm"

Note that for on-premises Exchange, you can use either the email address or the domain\username format for the Identity parameter.

For bulk operations on-premises, the commands are identical to Exchange Online:

Get-Mailbox -Server "ExchangeServer01" | Set-MailboxRegionalConfiguration -Language "de-DE" -LocalizeDefaultFolderName

You can specify a particular Exchange server using the -Server parameter if you have multiple servers in your environment.

Pro tip: For on-premises environments, you can also use Active Directory attributes to filter users, such as -Filter "Office -eq 'London'" to target users by location.

Verification: Confirm the changes using the same verification command:

Get-MailboxRegionalConfiguration "DOMAIN\username"
06

Troubleshoot Common Language Change Issues

Sometimes language changes don't appear immediately or folder names don't update as expected. Here are the most common issues and their solutions.

If the language change isn't visible in Outlook after making the change, the user doesn't need to restart Outlook as changes should apply immediately. However, if the change doesn't appear, you can force an update using Outlook command line parameters.

Open Command Prompt or PowerShell and run:

outlook.exe /resetfolders

Or specifically for folder names:

outlook.exe /resetfoldernames

These commands force Outlook to refresh the folder structure and apply the new language settings.

If folder names still aren't updating after using PowerShell with the -LocalizeDefaultFolderName parameter, verify that this parameter was included in your command. Without it, only the interface language changes, but folder names remain in their original language.

For users who had their preferred language already selected but folders weren't localized, try this workaround through the web interface: select a different language, save the settings, then switch back to the preferred language and save again. This forces a complete refresh of the language settings.

If you encounter permission errors when running PowerShell commands, ensure your account has the necessary Exchange administrative roles. For Exchange Online, you need Exchange Administrator or Global Administrator permissions. For on-premises, you need Exchange Organization Management or Recipient Management permissions.

Warning: The command line parameters /resetfolders and /resetfoldernames will reset custom folder arrangements. Users should be warned that any custom folder organization may be lost.

Verification: After troubleshooting, verify the language settings are correctly applied:

Get-MailboxRegionalConfiguration "user@domain.com" | Format-List

This displays all regional configuration details including Language, DateFormat, TimeFormat, and TimeZone.

Frequently Asked Questions

How long does it take for mailbox language changes to take effect in Outlook?+
Language changes in Microsoft Outlook take effect immediately without requiring a restart. However, if changes don't appear right away, you can force an update by running 'outlook.exe /resetfolders' or 'outlook.exe /resetfoldernames' from the command line. In some cases, users may need to refresh their Outlook web interface or close and reopen the desktop application to see the changes fully applied.
Can I change mailbox language for multiple users at once using PowerShell?+
Yes, you can change mailbox language for multiple users simultaneously using PowerShell. Use 'Get-Mailbox -ResultSize Unlimited | Set-MailboxRegionalConfiguration -Language "language-code" -LocalizeDefaultFolderName' to change all users, or filter specific groups with commands like 'Get-Mailbox -Filter "Department -eq 'Sales'"'. You can also process users from a CSV file for targeted bulk operations.
What language codes should I use for Set-MailboxRegionalConfiguration?+
Use Microsoft .NET Framework CultureInfo class format for language codes. Common examples include 'nl-NL' for Dutch Netherlands, 'de-DE' for German Germany, 'pt-BR' for Portuguese Brazil, 'da-DK' for Danish Denmark, 'ja-JP' for Japanese Japan, 'fr-FR' for French France, and 'es-ES' for Spanish Spain. Always use the full culture code format with both language and region identifiers.
Why aren't my Outlook folder names changing after setting a new language?+
Folder names don't change automatically unless you include the '-LocalizeDefaultFolderName' parameter in your PowerShell command. If you're using the web interface, ensure you check the box 'Rename default folders so their names match the specified language'. If folders still don't update, try selecting a different language first, saving, then switching back to your preferred language and saving again.
Do I need special permissions to change mailbox language settings in Exchange?+
For changing your own mailbox language, you only need access to Outlook on the web with your regular user credentials. For changing other users' settings via PowerShell, you need Exchange Administrator or Global Administrator permissions in Exchange Online, or Exchange Organization Management or Recipient Management permissions in on-premises Exchange. Administrative access to PowerShell or Exchange Management Shell is also required.

Discussion

Share your thoughts and insights

Sign in to join the discussion