Support for pre-providing username to connect-mggraph

[rrosand]

Is your feature request related to a problem? Please describe the problem.

Currently, with authentication via Web Account Manager with a user other than the one signed in to windows is as follows, when authenticating with a passkey:

1. run connect-mggraph in powershell
2. Select "Workplace or school account" in WAM
3. Select "sign-in options"
4. Select "Face, fingerprint, PIN or security key"
5. Select "choose a different passkey" (as it will attempt to sign in using windows hello for business)
6. Choose passkey.
7. Then do the rest of the passkey options.

This means that there are many unnecessary steps just to get to even being able to sign in.

Describe the solution you'd like.

I would like to have a switch on connect-mggraph, for passing the username that is intended to sign in with, so that Web Account Manager can go straight to asking for the prefered method for that aaccount (in our case passkey)

That would reduce these steps to:

1. Run "Connect-MgGraph -AccountID username@contoso.com
2. Sign in using passkey (or other system preferred method)

Additional context?

No response

[MIchaelMainer]

Thank you for bringing this to our attention. We are investigating the feasibility of making this change.

[ramsessanchez]

Hi @rrosand Passing a login hint to the identity auth flows should resolve to the scenario that you suggested above, where the login hint is used to make a determination as to what account the flow should default to. Unfortunately, after running a test build where the user can pass a 'loginHint' to our authentication module, there was no reduction in the authentication process. I believe that this is due to the current enablement of WAM and thus is preventing loginHint from working as intended. There is a possibility that our enforcement of WAM may be relaxed in the coming months as we continue to evaluate our auth flows and security measures, but for the time being we cannot implement these changes.