Why is SignUpSignInPolicyId one property in the library?!?!?

[drewid]

Why in the world is SignUpSignInPolicyId one property?!?!? Cannot reasonably conceive of why these are not split out. If someone wants the same policy for both of them then they can have it in both fields. This kills basic functionality.

It boggles the mind that these are not separated as they commonly would require separate logic!

For example, in many/most real use cases, it would be common to expect for minimal information on signup and more on sign in to capture more as a very basic example.

MSAL is supposed to be production ready for wide-scale adoption and NOT just demo ready.

Please update this in the next version.

This is unfortunate and makes me want to throw my hands in the air and give up. It is small things like this that are killing adoption.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: a55fe7a2-c34c-d3bd-5ea4-716aa340fc8d
• Version Independent ID: a55fe7a2-c34c-d3bd-5ea4-716aa340fc8d
• Content: MicrosoftIdentityOptions.SignUpSignInPolicyId Property (Microsoft.Identity.Web) - Microsoft Authentication Library for .NET
• Content Source: dotnet/xml/Microsoft.Identity.Web/MicrosoftIdentityOptions.xml
• Service: msal
• GitHub Login: @dotnet-bot
• Microsoft Alias: dmwendia