-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix error message for failed domain login to include the correct credential type #6936
Comments
@slavizh Can you verify which actual domain name you used for this, and whether you were using an msa account, or a work or school account? |
@markcowl I cannot specify the exact domain as I do not want to reveal information for a customer. I do not think the actual domain matters as long as the scenario described above is achieved. I've used Azure AD account (work). I haven't tried if the above scenario appears for MSA as well. Make sure that command Clear-AzureRmContext is executed before trying this scenario as if previous contexts are present you will not see the error. |
@slavizh The reason I ask is to determine if this is a real domain name with Azure assets that the user has access to. The actual domain name doesn't matter. |
@markcowl Yes, it is a real domain. |
@maddieclayton This looks like a logic error when determining the paramneter set - these parameters shoudl result in an interactive login, but instead are resulting in an attempt at SPN login. |
DescriptionThe message returned when domain lookup fails should look at the accoutn type, rether than assuming it is an SPN
Cost: 1 |
This has been fixed and will be available in the upcoming release (2018-11-06) |
Hi,
|
Description
When you want to be asked for credentials interactively the Connect-AzureRmAccount with domain provided does not work.
Script/Steps for Reproduction
Doing something like this works:
Module Version
Environment Data
Debug Output
This is easily reproducible so no debug is needed.
The text was updated successfully, but these errors were encountered: