Mar 27 2017 11:37 AM
Has there been a change in regards to using Outlook to view/interact with SharePoint (O365) calendars?
All of our users are seeing 401's regardless of site permissions (Member to Site Collection Admin)
Set up is EXO and SPO. EXO is in a hybrid architecture. We are using Outlook 2016 CTR.
I get this Outlook not Exchange, just wanted to put out all the variables I can think of. :)
Thanks,
eRic
Mar 27 2017 02:19 PM
Mar 30 2017 04:00 PM
May 12 2017 06:31 AM
Hi Eric,
Were you able to resolve?
What version of Outlook are you running? Is it Office 2013 by chance?
We're seeing the same issue with Outlook 2013 connecting to SPOnline calendars. We also had issues with Word/Excel/OneNote accessing documents in SPOnline. Users would receive a login prompt that they could not get past.
However this was resolved by enabling modern authentication.
May 12 2017 06:33 AM
Jan 10 2019 01:05 PM
For anybody else that happens to run into the 2013 -> SharePoint Online issue, these files must be updated to this minimum version for ADAL to work:
File name | Install path on your computer | Where to get the update | Version |
MSO.DLL | C:\Program Files\Common Files\Microsoft Shared\OFFICE15\MSO.DLL | 15.0.4753.1001 | |
CSI.DLL | C:\Program Files\Common Files\Microsoft Shared\OFFICE15\Csi.dll | 15.0.4753.1000 | |
Groove.exe | C:\Program Files\Microsoft Office\Office15\GROOVE.EXE | 15.0.4763.1000 | |
Outlook.exe | C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE | 15.0.4753.1002 | |
ADAL.DLL | C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ADAL.DLL | 1.0.2016.624 | |
Iexplore.exe | C:\Program Files\Internet Explorer | Not applicable |
It's mentioned as part of the MFA requirements, but I haven't seen it mentioned anywhere as part of the ADAL requirements or as a solution to the Office 2013 credential prompting issue that you'll find yourself running into if you don't have a completely up-to-date 2013 MSI install.
I'd also recommend clearing the HKCU\Software\Microsoft\Office\15.0\Common\Identity key and Identities subkey, and adding back EnableADAL and Version as DWORDs with a value of 1 to enable ADAL.
If there's not a GUID_ADAL key under HKCU\Software\Microsoft\Office\15.0\Common\Identity\Identities after you make an Office->SharePoint connection, then it's not working and ADAL isn't being used.
Hopefully this is helpful to someone else so they don't have to track down the problem.