能否调整Azure ADB2C注册用户流中电子邮件地址属性的位置？

Absolutely—you can move the email address to the bottom of your registration form, but there's a catch with the standard user flow's visual editor that's causing your changes to revert. Let me break down why this happens and how to fix it properly:

Why your changes are reverting #

In the standard Azure AD B2C user flow's page layout editor, the email address is treated as a core identity attribute (since it’s tied directly to user authentication and sign-in). The visual editor has a built-in default behavior that forces this attribute to the top of the form, even if you manually reorder it and save. That’s why your adjustments keep reverting after you hit "save."

How to fix it (two approaches) #

1. Use Custom Policies (recommended for full control) #

Custom Policies are the flexible alternative to standard user flows, letting you fully customize every aspect of the registration form—including attribute order. Here’s what you need to do:

• Start with the Azure AD B2C starter pack policies (you can get these from the official B2C policy template library)
• Locate the self-asserted page content definition for your registration flow (usually named api.selfasserted or api.signuporsignin)
• In the <InputClaims> section of this definition, rearrange the ClaimTypeReferenceId entries to match your desired order:

  <InputClaims>
    <InputClaim ClaimTypeReferenceId="givenName" />
    <InputClaim ClaimTypeReferenceId="surname" />
    <InputClaim ClaimTypeReferenceId="jobTitle" />
    <InputClaim ClaimTypeReferenceId="email" />
  </InputClaims>
  

• Save your policy file, upload it to your Azure AD B2C tenant, and test the flow. The email address will now appear at the bottom of your registration form as expected.

2. Workaround for standard user flows (limited reliability) #

If you want to stick with standard user flows, there’s no official way to override the email address’s default position via the visual editor. Some users have reported inconsistent partial success by:

• Temporarily removing the email attribute, reordering the remaining fields, then re-adding email and immediately moving it down
• But this trick often reverts after saving, so it’s not a reliable long-term solution.

Key Notes #

• Standard user flows prioritize core identity attributes like email/username for authentication, which is why their positions are locked in the visual editor.
• Custom Policies give you full control over UI layout, attribute order, and user flow logic—they’re the go-to solution for any non-trivial customization.

内容的提问来源于stack exchange，提问作者johnnyjohnson