Microsoft Entra External ID: Can the built-in "No account? Create one" link in a sign-in user flow be redirected to a custom registration URL?

Question

Microsoft Entra External ID: Can the built-in "No account? Create one" link in a sign-in user flow be redirected to a custom registration URL?

Lipikasree B 0

I'm using Microsoft Entra External ID with a built-in sign-in/sign-up user flow.

On the Microsoft-hosted sign-in page, there is a built-in "No account? Create one" link that opens the default sign-up experience.

In my application, I already have a custom registration page and would like users who click "Create one" to be redirected to that page instead of the default sign-up page.

I have reviewed the available user flow and branding settings but couldn't find an option to configure the destination of this link.

My questions are:

Is there any supported way to change the destination of the built-in "Create one" link to a custom URL?

If not, is this behavior fixed by design for built-in user flows?

If there is an alternative approach (for example, custom page layouts, custom policies, or another supported configuration), could you provide the recommended method?

I'm specifically looking for a supported solution rather than a JavaScript or DOM-manipulation workaround.

Thank you.

0 comments

1 answer

Your answer

Answer 1

No. In built-in Microsoft Entra External ID user flows, there is no supported setting to change the built-in "No account? Create one" link so it redirects to a custom registration URL.

This behavior is fixed for the Microsoft-hosted experience in built-in user flows:

A user flow defines the sign-up and sign-in steps that customers follow.
The Microsoft-hosted page uses that user flow to present the built-in sign-up experience.
The available configuration in built-in user flows is for things such as identity providers, collected attributes, branding, and custom URL domains for the hosted endpoints.
The provided documentation does not describe any supported option to override the Create one link target.

A closely related Microsoft Q&A answer states there is no direct link to the sign-up form that bypasses the built-in sign-in view in this model. That aligns with the built-in flow being controlled by the user flow rather than by a configurable custom destination.

Supported alternatives from the available guidance:

Use the built-in sign-up/sign-in user flow as designed
- Keep the Microsoft-hosted sign-in page and let Create one open the default sign-up experience defined by the user flow.
Build a custom sign-in experience in the app
- Microsoft Entra External ID supports native authentication, which allows the sign-in UI to be built directly into the application.
- This gives full control over the sign-in experience, but it requires more development effort and shared security responsibility.
Use browser-delegated authentication with a separate app-controlled registration entry point
- Present separate Sign in and Register actions in the application UI.
- The sign-in action can use the Microsoft-hosted user flow.
- The registration action can use the application’s own registration experience.
- The context does not provide a supported built-in configuration that rewires the hosted Create one link itself.
Extend the flow with custom logic, not link redirection
- If extra workflow is needed during sign-up or sign-in, use custom authentication extensions to run custom logic through REST APIs during the flow.
- This is for workflow customization, not for changing the built-in link destination.

If the requirement is specifically to have the hosted Create one link open a custom URL, the supported answer is that built-in user flows do not provide that capability.