Платформа и инфраструктура облачных вычислений для создания и развертывания приложений и служб, а также для и управления ими через глобальную сеть центров обработки данных, управляемых корпорацией Майкрософт.
Hello. Can anyone help us?
Этот браузер больше не поддерживается.
Выполните обновление до Microsoft Edge, чтобы воспользоваться новейшими функциями, обновлениями для системы безопасности и технической поддержкой.
Our Azure tenant was initially created with the portal language set to a non‑English locale. The environment has since been standardized to English, and all custom resources and policy assignments are now named in English.
However, compliance reports still show non‑ASCII characters tied to initial policy artifacts. We understand that built‑in Azure Policy definitions have fixed names that cannot be renamed. Still, the presence of non‑ASCII text in system metadata and display fields creates inconsistency in our audit outputs, which must be fully English‑standardized.
We are using built‑in policies such as:
Is there any mechanism to clear or reset non‑ASCII language artifacts from policy metadata or display fields after a tenant’s language context has changed?
Thanks for your help.
Платформа и инфраструктура облачных вычислений для создания и развертывания приложений и служб, а также для и управления ими через глобальную сеть центров обработки данных, управляемых корпорацией Майкрософт.
Hello. Can anyone help us?
Hello.
We engaged Microsoft Support regarding this issue. They confirmed that the built-in system policy definitions locked with the initial localized characters could not be renamed or updated directly from our end.
To resolve the inconsistency in our audit outputs, the following actions were taken:
The environment is now fully compliant with our English-only reporting standards, and the task is complete.