Reputation: 8656
I'm using the Azure portal to create a SignUp policy.
But can't find a way to make certain fields mandatory. Is this possible?
Upvotes: 2
Views: 3086
Reputation: 161
I'm referring to Randy Minder answer,
the comments <!-- Required claims --> and <!-- Optional claims --> ,
they don't seem to work, if placed only (?) inside the Technical Profile. Also those are not mentioned in the linked documentation. So I was struggling, how to make a newly created extension_attribute not mandatory.
Then after "trial and error", i found this post: restrictions. Apparently, if you add a restriction pattern, the field becomes mandatory. That is implicit and not mentioned in the documentation. Also a default value doesn't change this behavior.
Upvotes: 0
Reputation: 2293
You can do this in the standard policy (i.e. without custom policies) by going in the Page UI Customization, and for each page, selecting whether you want attributes to be optional or required. This gives you the capability to make an attribute optional in one page (e.g. local account sign-up) but mandatory on another (e.g. social account sign-up).
See the image below.
Upvotes: 4
Reputation: 48482
You can solve this problem by making certain claims required or optional, as shown below.
You can learn more about here
Upvotes: -1