Github user ChrisMcVey commented on the issue:
https://github.com/apache/zeppelin/pull/986
Well... I'm back again. :)
Apparently, Office 365 requires that userPrincipalName be changed to the
user's routable email address in order for it to be used in any cloud
environments. Company-wide I have found that where I am currently working, no
sAMAccountNames match userPrincipalNames. Further, no usernames match the new
userPrincipalNames set for compliance with Office 365.
So, the current design of the provider will implicitly not work with AD
going forward.
https://blogs.technet.microsoft.com/askpfeplat/2013/09/01/office-365-single-sign-on-how-to-handle-different-userprincipalname-upn-values/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
