This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 14.000000000000002%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVJ%3C/text%3E%3C/svg%3E)
I have trouble using the localization feature for Azure AD B2C as some texts seem not to be translatable.
There's this weird "pledge" in the documentation here https://learn.microsoft.com/en-us/azure/active-directory-b2c/language-customization?pivots=b2c-user-flow#up-to-date-translations, which promises up-to-date translations from Microsoft. However, this is obviously not true. But more importantly, there are places where even providing one's own translations - at least for built-in flows - is not possible.
STEPS TO REPRODUCE
EXPECTED RESULTS
I am able to change/translate the error message.
ACTUAL RESULTS
No apparent ability to translate the error message. The default localized string
{
"ElementType": "Predicate",
"ElementId": "internationalOrNationalPhoneNumber",
"StringId": "HelpText",
"Override": true,
"Value": "The value entered needs to be a phone number."
}
used in local account sign-up and unified sign-up/sign-in does not seem to apply for phone sign-in/sign-up pages.
Other steps in the process where translations are missing and unclear how to fill them in:
No way to translate any of them, The first one would logically be:
{
"ElementType": "DisplayControl",
"ElementId": "phoneVerificationControl",
"StringId": "success_verify_code_msg",
"Override": true,
"Value": "The code has been verified. You can now continue."
}
However, this is not valid in the template for phone sign-up/sign-in. Is Azure AD B2C supposed to be this buggy?
Hi @Veli-Jussi Raitila , not all strings are customizable unfortunately. The strings that are not customizable are part of the built-in user flows and are not exposed for customization. The error message you mentioned, "The value entered needs to be a phone number," is one of those strings that cannot be customized.
"success_verify_code_msg" is a valid ID so it should work. Make sure your page layout version is >= 2.1.0 and that you meet the VerificationControl requirements.
Please let me know if you have any questions and I can help you further.
If this answer helps you please mark "Accept Answer" so other users can reference it.
Thank you,
James
I can somewhat understand if some strings are not customizable. However, in the link I provided, the documentation says:
Microsoft is committed to providing the most up-to-date translations for your use. Microsoft continuously improves translations and keeps them in compliance for you. Microsoft will identify bugs and changes in global terminology and make updates that will work seamlessly in your user flow.
Even if the strings cannot be changed, at least default translations should be provided for each supported language. In the examples I gave, this does not apply. It makes a rather bad impression for non-English speakers to have labels in a foreign language mixed with one's own - particularly with the built-in user flows Microsoft recommends using if otherwise sufficient.
And when a default translation exists, I find it nonsensical to not be able to customize it as the mechanism would be the same. Furthermore, some page layouts do have similar labels and are indeed translated - it is the ones used in phone sign-in/sign-up flow that are lacking.
Regarding "success_verify_code_msg". I have the latest page layout (2.1.32 for phone sign-up/sign-in), but the translation is not applied. It is indeed a valid ID, but still not accepted in the template. I do not understand the comment about the VerificationControl requirements as it is a standard flow. This is the error I get:
Validation errors found in upload overrides for api.phoneSignUp. Please ensure that your uploaded resource matches the template: The localized string with ElementType: DisplayControl, ElementId: phoneVerificationControl and StringId: success_verify_code_msg is not a valid override.