Outlook 2016 authentication prompt with email address as username

alexjdale
Valued Contributor III

Someone just brought this to my attention today: Outlook 2016, when it needs to prompt for user credentials to authenticate (if I delete my Exchange keychain entry for example), automatically fills in the user's email address in the "user name" field rather than their username. This will cause authentication to fail for on-prem Exchange if the user simply enters their password. They need to edit the field to be their username.

Has anyone else seen this? I assume this is how O365 authenticates and this is a bug based on that. We'll need to train users to do this themselves when they have a password change or other prompt.

16 REPLIES 16

corbinmharris
Contributor

Yes, we are seeing this as well. However it is not happening to all our Office 2016 (15.13.1) users.

kstrick
Contributor III

happening to us. didn't happen pre-15.13, but 15.13 and 15.14 seems to happen.

joecurrin
New Contributor III

I can consistently recreate this issue whenever the password is changed or invalid...hello bug report.

alexjdale
Valued Contributor III

Our MS contact has said this is by design, and they are pushing orgs to start using UPN-format logons. Nice change to throw at us under the radar...

They also said that it should only be an issue where the username and UPN don't match (if the email address is not the username@domain, but something different). Mine matches but still fails so I presume there may be an environment config required.

corbinmharris
Contributor

@alexjdale , can you expand on UPN-format logons? Our users have a proxy address set in AD for their primary email address - SMTP:someone@3c.com, however their account name is someone@3cinterative.com

Thanks!
Corbin

kstrick
Contributor III

If this is intended behavior,
then they need to give us an option to adjust it.
(turn off autodiscovery?)

alexjdale
Valued Contributor III

User Principal Name format: https://msdn.microsoft.com/en-us/library/windows/desktop/aa380525(v=vs.85).aspx

m_entholzner
Contributor III

happens here as well. I have a bug report open with MS too, but no response yet...

chrisbju
New Contributor III

Same here.

kstrick
Contributor III

I posted it to "Office for Mac Techincal Preview" Yammer forum a few days ago, and one of the Program Manager's reproduced the issue and is investigating, so hoping that means it's actually on their radar now.

corbinmharris
Contributor

Office 2016 for Windows is due out later this month. We do have a few Windoze users, so it will be interesting to find out if this is an issue with the Windows version of O2016.

Corbin

Bhughes
Contributor

same issue here. Would be nice to have a bug fix for sure!

bvrooman
Valued Contributor

This is especially problematic for us - our email addresses are first.last@company.com, and our UPN logon is employeenumber@department.company.com. Nobody understands that last part, so asking people to remember to re-enter it is just moot.

I found a possible workaround by modifying @talkingmoose's Outlook setup script to also request the user's password and configuring the whole thing at first run, but it doesn't help password changes.

naomiv2672
New Contributor

I got the same Issue. will disabling credential Manager do it?

mpittcasd
Contributor

Has anyone found a permanent solution for this yet? I have a lot of users getting locked out because Outlook randomly asks for their password and they don't look to see that the user name has changed to their email address. Our email addresses don't match our UPN and probably never will, and telling Outlook to remember the login information in the Keychain (which I am hesitant to do after rampant keychain issues in the past) only seems to work temporarily.

jconte
Contributor II

I don't believe you will find a solution for this as we had the same issue. We had to make all of our UPNs match the email addresses in AD.
We still get prompts every month when the user changes the password but it takes the new one and it moves on without issue. If I recall, the issue is with Modern Auth and Mac because it only work with IE, Windows.