FIX: Cannot localize the default folders by Bas Wijdenes

“The localization operation of the default folders of mailbox failed:Cannot localize the default folders.” the basics.

This post actually dates from November 3, 2015. I have made such adjustments that I have re-published the post.

It may happen that when you change the default folder names in Outlook or OWA, you get an error message:

“The localization operation of the default folders of mailbox “SERVER.prod.outlook.com /Microsoft Exchange Hosted Organizations/TENANTNAME/USERNAME” failed:Cannot localize the default folders.”

Cannot localize the default folders
The localization operation of the default folders of mailbox failed:Cannot localize the default folders.” Cannot localize the default folders.”

The message does not really have a clear error message what is going wrong, besides that it cannot localize the default folders.

A colleague of mine got this error message and after searching for a time we found out that this has to do with the default language settings. This is because you try to change a folder name to a name that does not match the default language.

For example, it may happen that a user imports folders from a .pst file that correspond to the default folder names. As a result, Outlook cannot localize the local default folders aka “failed:Cannot localize the default folders“.

Below I have two solutions. If you are a system administrator and have access to the Office 365 environment and know how powerShell works, you can try option one.

If you are an end user, you can go directly to option two.


Option 1 – The Sysadmin solution for “Cannot localize the default folders”.

As I mentioned above, you can only use option one if you have access to the Office 365 environment, and know how to log in to Exchange Online via PowerShell. I can give you that second part, but for the rest you have to do it yourself.

Make sure you have installed the Exchange Online PowerShell module.

Run this script to log in to PowerShell:

$cred365 = get-credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $cred365 -Authentication Basic -AllowRedirection

Import-PSSession $Session

Import-Module MSOnline

Run the following script now, but adjust the <ALIAS> to the user’s email address. Same applies to:

  • <Language_code_to_switch_to>
  • <your_preferred_DateFormat>
set-MailboxRegionalConfiguration -id <alias> -LocalizeDefaultFolderName:$true -Language <Language_code_to_switch_to> -DateFormat <your_preferred_DateFormat>
See if that has solved your problem and otherwise continue with option 2.

Option 2 – Lets fix it as an end user.

Fix 2: If you are an end-user, use Outlook Web App to reset the default folder names:

  1. Log on to Outlook Web App by using your credential.
  2. Click Options, and then click See All Options.
  3. Click Settings, and then click Regional.
  4. On the Regional Settings page, change the language, select the date and time format that you want to use, and then select the Rename default folders so their names match the specified language option.
  5. Click Save, and then exit Outlook Web App.
  6. Restart Outlook.

Default folders which may cause that conflict are: Inbox, Sent Items, Drafts, Junk Email, RSS Subscriptions and Deleted Items.


Summary

If you have found another solution, can you indicate this below? I’ll adjust the blog post and I’ll tag your social media if you want.

Do you have other feedback or ideas? Then you can also let me know below.

Published by

Bas Wijdenes

My name is Bas Wijdenes and I work full-time as a Services Engineer. In my spare time I write about the error messages that I encounter during my work. Furthermore, I am currently occupied with Office 365, Azure infrastructure, and PowerShell for automating daily tasks.

Leave a Reply

Your email address will not be published. Required fields are marked *