Forum Discussion
Tom Murray
Aug 15, 2017Copper Contributor
Azure AD W10 and Outlook
Hi All, We have Azure AD joined machines, coniditional access and with Windows hello enabled, all our applications work with AAD Proxy single signon. Currently outlook (office365) is our biggest...
Lane HOY
Jun 01, 2018Copper Contributor
I am experiencing the same issue, really having a hard time as the popup to logon comes back every few minutes and even removing azuread/ does not allow successful logon...
LilleLars
Nov 20, 2018Copper Contributor
did anyone find a final solution
?
- Helios CommsNov 23, 2018Iron ContributorLooking for a solution as well. My client would like to use MFA so modern authentication is a step towards that as it means they don't have to mess around with application passwords (non-starter to be honest). I've been given permission to try modern authentication over the weekend and immediately hit this azuread prefix problem on my test VM and test accounts.
Signing in as a different user and removing azuread at the start does work but it's totally unreasonable to expect the users to do this.
Interestingly my own personal VM that I use for this client didn't have the same problem but it's running the monthly targeted version of Outlook (v1811) whereas my test VM (and clients) are running semi-annual channel (v1803).
I'm just switching channel on my test VM to v1811 to see if the problem goes away.- Helios CommsNov 23, 2018Iron Contributor
BTW - I documented the process on answers before I found this topic:
https://answers.microsoft.com/en-us/msoffice/forum/all/users-unable-to-open-outlook-2016-after-enabling/e380a49e-ee77-4f6f-965a-1f77f730925c- Helios CommsNov 23, 2018Iron ContributorYes, it's a bug/problem in Office 2016 v1811 - the current semi-annual release. Upgrade the VM to v1803 (monthly targeted) and Outlook loads flawlessly.
Am about to restore the VM and try semi-annual targeted...