Allow Office 2016 for Mac to pass your enterprise login credentials from the OS of the Mac to Outlook 2016 for Mac client.
I would like to know more about the inability to pass your enterprise login credentials from the OS of the Mac to the Outlook 2016 for Mac client. Specifically, can this be done? If so, how? If not, why not? This functionality exists for Windows and the related version of Office 2016 for Windows. When using this combination of software my enterprise login credentials are passed thru to Outlook. When I change my password the updated password is automatically passed thru to Outlook for Windows. When I change my password on my Mac the Outlook for Mac client prompts me to update my credentials. After updating my credentials once they can be saved for future login attempts, but I would like the Outlook for Mac client to function like the Outlook for Windows client where I do not have to supply an updated password.
Adam Martin commented
This would make Outlook for Mac SO much better if it could be implemented. As mentioned, the current process for Mac users is clunky. To make matters even worse our scenario, because our exchange server is set up on O365, the username field is DomainUserID@company.com rather than just DomainUserID or Company\DomainUserID. This is something we've heavily documented for end users but it makes it very difficult because when it comes time to change your password every 90 days in our case, the Outlook pop up to enter the new password comes up and shows DomainUserID@company.com and the user thinks wait, that's not my email and then enters email@example.com and Outlook is then essentially borked!
Luis Trevino commented
Looking into Certificate base authentication. We are using Certificates on our iPhones to avoid users from updating their password every 90 days. They only have to update the password on their desktop every 90 days.
Matthew Stott commented
If your Exchange server is configured to use Kerberos then you can set the Authentication Method to Kerberos and it will work. It is a complex setup and many IT shops may not have implemented it on Exchange. Check with your Exchange Admins.