External Identity User Flows: Disabling Sign-up in a "Sign-up and Sign-in" User Flow does not Take Effect when demoing via the "Run User Flow" interface

Lance Tallman 40 Reputation points
2024-03-08T17:22:16.98+00:00

Overview:

Our team recently created a "Microsoft Entra ID for Customers" resource which we are attempting to configure for our use case. For said use case, only customers with pre-created accounts should be able to access our application. As such, we need to disable the "No account? Create one" button that is inherent to the "Sign-up and Sign-in" User Flow. Notably, no UI control exists to do this within the Microsoft Entra admin center.

Steps Taken:

After looking through the existing Entra ID documentation, we stumbled upon the following article which seemed to perfectly encapsulate the problem we needed to solve and prescribed a solution to it:

https://learn.microsoft.com/en-us/entra/external-id/customers/how-to-user-flow-sign-up-sign-in-customers#disable-sign-up-in-a-sign-up-and-sign-in-user-flow

We followed the specified steps to obtain the ID of our User Flow and gave our Application the necessary API permissions to accept the request. After a time, we were able to successfully make the PATCH request specified in the above documentation. After receiving a 204 (success) response, we navigated back to the Microsoft Entra admin center > External Identities > User flows > Our User Flow and clicked the "Run user flow" button. Much to our dismay, the "No account? Create one" button was still displayed.

To triple-check that we didn't make a mistake, we followed the documentation below to view the JSON representation of our created User Flow via a GET request. In the response JSON, we confirmed that the isSignUpAllowed property was correctly set to false:

"onInteractiveAuthFlowStart": {
                "@odata.type": "#microsoft.graph.onInteractiveAuthFlowStartExternalUsersSelfServiceSignUp",
                "isSignUpAllowed": false
            },

https://learn.microsoft.com/en-us/graph/api/identitycontainer-list-authenticationeventsflows?view=graph-rest-beta&tabs=http#example-4-list-user-flow-associated-with-specific-application-id

Problem & Assistance Needed:

Having performed the steps above, our understanding is that the "No account? Create one" button should be disabled since the "isSignUpAllowed" property is set to false for our User Flow. Given that it's still appearing in the User Flow "run flow" preview, is this a bug/known issue? Is this a problem specific to just the User Flow preview? Is there a different "type" of User Flow we can create that doesn't enable sign-up (it doesn't look like it)? Is there something we're missing or something else we can do?

Thanks so much for any help, guidance, or direction!

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,907 questions
0 comments No comments
{count} votes

Accepted answer
  1. Shweta Mathur 29,776 Reputation points Microsoft Employee
    2024-03-11T10:22:07.65+00:00

    Hi @Lance Tallman ,

    Thanks for reaching out.

    Your understanding and steps are correct here.

    I tried the steps as mentioned by you which helped me to disable the signup button.

    Step 1: I created the new user flow "DisableSignUp"

    User's image

    Step 2: Retrieved the user flow id as below:User's image

    send the patch request to disable the sign-up flow:

    User's image

    After that I run the user flow using "Run User Flow" from the portal directly and cannot see "No account? Create one"

    User's image

    Please confirm that you are using correct user flow id to disable the signup flow.

    Hope this will help.

    Thanks,

    Shweta

    Please remember to "Accept Answer" if answer helped you.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.