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...
Helios Comms
Nov 23, 2018Iron Contributor
Yes, 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...
Am about to restore the VM and try semi-annual targeted...
Helios Comms
Nov 23, 2018Iron Contributor
Rounding this off for tonight. The problem also does not occur in the semi-annual targeted channel (v1808) which was released in September. So that's when it was fixed. The semi-annual channel (v1803) was released in July and does have this fault.
The next semi-annual release (bringing it inline with v1808) is in January so not that long until this flaw is fixed in all our client systems.
So I'm snoozing the ticket to implement modern authentication for another three months.
The next semi-annual release (bringing it inline with v1808) is in January so not that long until this flaw is fixed in all our client systems.
So I'm snoozing the ticket to implement modern authentication for another three months.
- Stephen HoweDec 05, 2018Copper Contributor
Hi there
I seem to have the same issue - Surface Pro joined to Azure AD, this week Outlook and Skype stopped working. I have followed the steps to change the tenancy release schedule and I also opted the software into targeted. But no joy.
I have even uninstalled Office 2016, removed mail profile and retried - both SfB and Outlook fail to setup the account. Windows Security still prompts for the password and won't go away.
I have tried the email address as the username and Azuread\myo365email as the username also.