Microsoft Viva Glint: Some language codes will retire from translation services [MC1041428]

Microsoft Viva Glint: Some language codes will retire from translation services [MC1041428]

Message ID: MC1041428

Effective with Release 83 (April 10, 2025), we will update some language localizations and codes in Microsoft Viva Glint to better reflect current standards and improve the user experience.

A subscription plan for Microsoft Viva Suite or Viva Glint are required for using Viva Glint.

[When this will happen:]

General Availability (Worldwide): This change will be implemented April 10, 2025.

[How this will affect your organization:]

This table lists the language codes that we will retire. Where applicable, potential replacements have been noted. These language codes will be available in the platform through August 31, 2025, but will no longer receive translation updates after Release 83 (April 10, 2025). After August 31, 2025, we will remove the retired codes from Viva Glint. If a retired language code is used after August 31, 2025, users will be defaulted to their organization’s default language.

Retiring language code Retiring language shown in the user experience Potential alternative language code Potential alternative language shown in the user experience
de_AT Austrian (German) de_DE German
zh_HK

Chinese (Hong Kong)

zh_TW

zh_CN
Chinese (Traditional)

Chinese (Simplified)
bn_BD Bengali bn_IN Bangla
cy_GB Welsh N/A N/A
fr_HT Haitian Creole N/A N/A
hy_AM Armenian N/A N/A
nso_ZA Northern Sotho N/A N/A
si_LK Sinhala N/A N/A
sw_KE Swahili N/A N/A
xh_ZA Xhosa N/A N/A

[What you need to do to prepare:]

Notify your Viva Glint admins of this upcoming change. If they wish to keep any custom translation content imported for the retiring language codes, they will need to do so before August 31, 2025. The admins may also want to update retiring language codes to a different code before August 31, 2025.

Learn more: Manage language translations in Viva Glint programs | Microsoft Learn

Source: Microsoft

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

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