AzureAD PowerShell module Authentication Bug? RRS feed

  • General discussion

  • For anyone who uses the AzureAD PowerShell module, I would like your feedback if you can duplicate the same experience I am having, or clarify why this might be (or not be) normal.

    First, I store some valid credentials into a variable.  $creds = Get-Credential

    I then pass this variable into the connect cmdlet.  Connect-AzureAD -Credential $creds
    And it all works fine.  I can perform work - all is well.

    I disconnect.  Disconnect-AzureAD
    Again, all is good.  I can no longer execute commands against my environment.  Nothing above is problematic yet.

    In this same PowerShell session/window/instance, I can pass my same username with either a bad password or no password ($null) back into my connect cmdlet as shown above, and AzureAD will connect.  I can use a new variable with my same username and bad password, and AzureAD will still connect.

    I believe that it should not connect because the credentials being given are not valid, and AzureAD is not doing something right.  I'm all good on getting connected.  It's this glitch/bug in authentication that has me concerned.  I've already submitted a bug report via Feedback Hub, but I'm not sure if there is another recommendation for reporting this.

    Friday, April 26, 2019 3:26 AM