Azure AD B2C Custom policy - translations encoding issue

Mikhail Smal 26 Reputation points
2020-11-16T10:02:38.46+00:00

Hi. We have Azure AD B2C configured with custom policies including custom email verification. In our policy we have provided translations for a number of strings. E.g. "success_send_code_msg". Such message is injected into the sign up page via window.CONTENT variable. It seems the encoding is incorrect. This is how the message looks like:
"success_send_code_msg":"En verifikationskod har skickats till din mailadress. Kopiera koden till fältet nedan."
As you can see the letter ä is UTF encoded and appears exactly as ä in the UI.

Am I doing something wrong or is it a bug? Is there a workaround for that?
Thanks.

Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
2,678 questions
0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Marcus Engebretsen 21 Reputation points
    2021-02-04T17:21:33.837+00:00

    Works for me with

    <DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2</DataUri>

    0 comments No comments

  2. William Watterson 1 Reputation point
    2021-02-07T12:42:05.047+00:00

    Tried with <DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.2</DataUri>

    It works for most of the elements on the page - but get an issue with <a> tags eg:

    64943-image.png

    0 comments No comments

  3. Teun Dozeman 0 Reputation points
    2023-02-14T14:53:03.46+00:00

    I currently still to have problem with encoding and not sure why. I've updated the template versions to all the latest version, but for the German language the "ä" character on the register page after sending a verification code to E-mail. The next step shows encoding issues.

    User's image

    Anyone an idea how to resolve this.

    0 comments No comments