Fixes #12870 - Add note about fallback to en language (#12872)

* Add note about fallback to `en` language

* Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: sdwheeler

reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md

@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Utility
-ms.date: 01/19/2023
+ms.date: 03/20/2026
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/import-localizeddata?view=powershell-7.5&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Import-LocalizedData
@@ -379,6 +379,11 @@ parameter.
   user messages into the value of the **BindingVariable** parameter in the command. Then, when you
   display a message from the hashtable in the variable, the localized message is displayed.
 
+  Beginning in PowerShell 7.5.5, the cmdlet falls back to `en-US` and then `en` for any
+  `<language>-<Region>` when you don't use the **UICulture** parameter. Therefore, if the command
+  can't find localized data for the current culture (`$PSUICulture`), the search falls back to
+  `en-US` and then to `en`.
+
   For more information, see
   [about_Script_Internationalization](../Microsoft.Powershell.Core/About/about_Script_Internationalization.md).
 

reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md

@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Utility
-ms.date: 01/19/2023
+ms.date: 03/20/2026
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/import-localizeddata?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Import-LocalizedData
@@ -379,6 +379,11 @@ parameter.
   user messages into the value of the **BindingVariable** parameter in the command. Then, when you
   display a message from the hashtable in the variable, the localized message is displayed.
 
+  Beginning in PowerShell 7.5.5, the cmdlet falls back to `en-US` and then `en` for any
+  `<language>-<Region>` when you don't use the **UICulture** parameter. Therefore, if the command
+  can't find localized data for the current culture (`$PSUICulture`), the search falls back to
+  `en-US` and then to `en`.
+
   For more information, see
   [about_Script_Internationalization](../Microsoft.Powershell.Core/About/about_Script_Internationalization.md).
 

reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-76.md

@@ -1,7 +1,7 @@
 ---
 title: What's New in PowerShell 7.6
 description: New features and changes released in PowerShell 7.6
-ms.date: 02/20/2026
+ms.date: 03/20/2026
 ---
 
 # What's New in PowerShell 7.6
@@ -89,6 +89,8 @@ PowerShell 7.6 includes the following updated modules:
 
 ## Cmdlet improvements
 
+- Add implicit localization fallback to `Import-LocalizedData` ([#19896][19896]) (Thanks
+  @chrisdent-de!)
 - Add `-Delimiter` parameter to `Get-Clipboard` ([#26572][26572]) (Thanks @MartinGC94!)
 - Fix Out-GridView by replacing use of obsolete BinaryFormatter with custom implementation
   ([#25497][25497]) (Thanks @mawosoft!)
@@ -214,6 +216,7 @@ This release includes the following experimental features:
 [18955]: https://github.com/PowerShell/PowerShell/pull/18955
 [19440]: https://github.com/PowerShell/PowerShell/pull/19440
 [19830]: https://github.com/PowerShell/PowerShell/pull/19830
+[19896]: https://github.com/PowerShell/PowerShell/pull/19896
 [20017]: https://github.com/PowerShell/PowerShell/pull/20017
 [20330]: https://github.com/PowerShell/PowerShell/pull/20330
 [20340]: https://github.com/PowerShell/PowerShell/pull/20340