All error messages not translatable even with a custom policy in Azure AD B2C?

Question

All error messages not translatable even with a custom policy in Azure AD B2C?

Veli-Jussi Raitila 451

I used this sample as a baseline to implement a phone sign-up/sign-in custom policy. The sample uses the Microsoft Entra ID multifactor authentication technical profile documented here to implement the sign-in part.

Localized error messages for said MFA technical profile are documented here. In order to authenticate, the user is sent a verification code during sign-in using SMS. However, this verification session/code can expire, in which case the user is presented with an error message which seems to be hard-coded in English. The documentation does mention e.g. the UserMessageIfWrongCodeEntered identifier for the error when the wrong code is entered. However, the there is no identifier for the expired session. What gives?

Anonymous

2025-01-24T11:09:29.14+00:00

Hi,
Thank you for posting your query on Microsoft Q&A.
I am Saiteja from Q&A will be assisting you with your query.
Based on the description: I understand that you would like to translate the language of the error message which you receive in Azure B2C. I would like to inform you that the element type and String ID errors with default errors are not customized. Since you would like to try the translation of the error messages which might be a possibility and request you to try the below information:
You can set up the list the supported languages in Trustframextensions:
You can go check for blocks of localization and your supported languages as follows:
<Localization Enabled="true">

<SupportedLanguages DefaultLanguage="en" MergeBehavior="ReplaceAll">

<SupportedLanguage>en</SupportedLanguage>

<SupportedLanguage>es</SupportedLanguage>

</SupportedLanguages>

</Localization>
Then you can add the required error messages using the following example:
<Localization Enabled="true">

<LocalizedResources Id="api.signuporsignin.en">

<LocalizedStrings>

<LocalizedString ElementType="ErrorMessage" StringId="ResourceOwnerFlowInvalidCredentials">Your password is incorrect.</LocalizedString>

<LocalizedString ElementType="ErrorMessage" StringId="UserMessageIfInvalidPassword">Your password is incorrect.</LocalizedString>

<LocalizedString ElementType="ErrorMessage" StringId="UserMessageIfPasswordExpired">Your password has expired.</LocalizedString>

</LocalizedStrings>

Now you can define the content definition as taking this as example:
<ContentDefinitions>

<ContentDefinition Id="api.signuporsignin">

<LocalizedResourcesReferences MergeBehavior="Prepend">

<LocalizedResourcesReference Language="en" LocalizedResourcesReferenceId="api.signuporsignin.en" />

<LocalizedResourcesReference Language="es" LocalizedResourcesReferenceId="api.signuporsignin.es" />

</LocalizedResourcesReferences>

</ContentDefinition>

<ContentDefinition Id="api.localaccountsignup">

<LocalizedResourcesReferences MergeBehavior="Prepend">

<LocalizedResourcesReference Language="en" LocalizedResourcesReferenceId="api.localaccountsignup.en" />

<LocalizedResourcesReference Language="es" LocalizedResourcesReferenceId="api.localaccountsignup.es" />

</LocalizedResourcesReferences>

</ContentDefinition>

</ContentDefinitions>

Here is the doc which can be used as reference. I hope this information is helpful. Please feel free to reach out if you have any further questions.
Veli-Jussi Raitila 451 Reputation points

2025-01-24T12:10:23.6466667+00:00

@Anonymous Excuse me, but that looks like typical LLM-generated garbage. The issue was with translating a specific error message (expiring verification session), which was not addressed at all.

What is the exact Localization string ID I should use - if it really is supposed to work?
Anonymous

2025-01-24T12:33:54.66+00:00

Hi @Veli-Jussi Raitila
Apologies for the inconvenience.
Could you please share me the exact error that you are seeing on the screen to verify the message and provide you an update accordingly.
Veli-Jussi Raitila 451 Reputation points

2025-01-24T13:50:09.83+00:00

It is this error message:

Both the built-in phone sign-up/sign-in flow and the custom policy sample from Microsoft seems to be using the Microsoft Entra ID multifactor authentication technical profile for this step. It is the one where the user is prompted for the verification code sent earlier using SMS.

In the links I provided in my original post, the documentation does not mention the Localization string ID for this particular error when the session has been expired.

For curiosity, there is also an inconsistency between the documentation and the sample code with regards to the error when invalid code is entered. It is a different error, though.
Simon Noiseux 0 Reputation points

2025-09-22T14:52:41.2666667+00:00

Hello @Veli-Jussi Raitila
Have you found a solution for your issue, i'm facing exactly the same and i was wondering if you have found out a workaround

Thank you
Veli-Jussi Raitila 451 Reputation points

2025-09-23T11:25:16.4566667+00:00

@Simon Noiseux Unfortunately no. Granted, I haven't checked whether the issue has been addressed in the latest policies, but I doubt it since Azure AD B2C always had an unfinished feel to it and is now effectively a dead product - and in process of being replaced by Microsoft Entra External ID.

Answer accepted by question author

0 additional answers

Your answer

Veli-Jussi Raitila 451 Reputation points

2025-01-24T12:10:23.6466667+00:00

@Anonymous Excuse me, but that looks like typical LLM-generated garbage. The issue was with translating a specific error message (expiring verification session), which was not addressed at all.

What is the exact Localization string ID I should use - if it really is supposed to work?
Anonymous

2025-01-24T12:33:54.66+00:00

Hi @Veli-Jussi Raitila
Apologies for the inconvenience.
Could you please share me the exact error that you are seeing on the screen to verify the message and provide you an update accordingly.
Veli-Jussi Raitila 451 Reputation points

2025-01-24T13:50:09.83+00:00

It is this error message:

Both the built-in phone sign-up/sign-in flow and the custom policy sample from Microsoft seems to be using the Microsoft Entra ID multifactor authentication technical profile for this step. It is the one where the user is prompted for the verification code sent earlier using SMS.

In the links I provided in my original post, the documentation does not mention the Localization string ID for this particular error when the session has been expired.

For curiosity, there is also an inconsistency between the documentation and the sample code with regards to the error when invalid code is entered. It is a different error, though.
Simon Noiseux 0 Reputation points

2025-09-22T14:52:41.2666667+00:00

Hello @Veli-Jussi Raitila
Have you found a solution for your issue, i'm facing exactly the same and i was wondering if you have found out a workaround

Thank you
Veli-Jussi Raitila 451 Reputation points

2025-09-23T11:25:16.4566667+00:00

@Simon Noiseux Unfortunately no. Granted, I haven't checked whether the issue has been addressed in the latest policies, but I doubt it since Azure AD B2C always had an unfinished feel to it and is now effectively a dead product - and in process of being replaced by Microsoft Entra External ID.

Answer 1

Hi @Veli-Jussi Raitila

Greetings of the day,

Based on the error message provided, we have found the error is from MFA services which are automated and cannot be translated. And unfortunately, there’s no out-of-box solution to modify these messages currently. This is the reason why you cannot find these messages in Localization IEF file. We are really sorry for the inconvenience. I would suggest you provide your ideas and feedback in the following link.

I hope this information is helpful. Please feel free to reach out if you have any further questions.

If the answer is helpful, please click "Accept Answer" and kindly "upvote it". If you have extra questions about this answer, please click "Comment".

Share via

All error messages not translatable even with a custom policy in Azure AD B2C?

0 additional answers

Your answer