When I try to connect to Microsoft Exchange as a Query data source, it tells me that my credentials are invalid, when in fact they are not. I have also double and triple-checked that my account is not locked out or otherwise disabled, and my emails are coming to Outlook just fine.

Any pointers or tips to helping me trace down what's blocking me would be greatly appreciated.

PS. I think this worked in the previous version of PowerQuery, but I don't know where to find that download now. I'd use it instead of anyone can tell me where to get it.

Hi Shawn,

Thanks for reporting this issue. We're following up via Frown so I'm marking this thread as complete here.

Regards,
M.

• Marked as answer by Miguel.LlopisMicrosoft employee, Owner Wednesday, February 19, 2014 6:49 PM

Thanks so much for your responsiveness, I never would have expected same-day (or in this case, same-hour) response!

Hello,

running into the same issue, could you please post how you managed to solve this?

Thanks

We are still investigating the original issue, if you are reporting a new issue, please report it via "send a frown" feature in Power Query to pqfb@Microsoft.com so we can follow up with more debugging.

Thanks

It's several months later, is there any update on this issue? We are experiencing the same issue with 2007 Exchange all patched up.

Same here, and I sent that frown ages ago. Could we just dispense with autodiscovery? I know what I have to fill out, and the magic under the hood is quite obviously not working.

Which version are you on?  I haven't had any issues since my reply above, I'm also using Excel 2013 now.

I had the same issue and I submitted a frown. Immediately after that I started playing with Outlook configurations and somehow it worked.  Go to Outlook Account Settings, Change, More Settings > tab Connection. Try using Negotiate instead of NTML. 

Hi there, has been a while but do you recall how you overcame this issue in more detail?

Hi Miguel,

Have addressed this with you on the Power Bi Blog and Exchange connector issues.

This is connected with the queries on this thread which appears unresolved.

I have no doubt there is a simple fix for this