Exchange Connector in Power BI Desktop No Longer Working

[trickytree83]

Hi all,

Hopefully someone can help me here.

Prior to the May update we had set up the connection to Exchange successfully. It was working fine, but since last week it's stopped working. I've confirmed with our IT dept that we were listening on https for the autodiscover request, it would appear that was working since I was able to pull data. I've tested Power Query in Excel and that can still connect.

So I enabled the Trace logs within Power BI and found that Power BI is trying to contact the autodiscover service via http not https.

Could this be causing the problem?

Is there a way to change from http to https within Power BI?

Has this happened as a result of the May update? I'm not aware of anything else changing, and since it still works in Excel that leads me to believe our IT dept haven't changed anything either.

Thanks in advance.

[arify]

Hi,

When we make the autodiscover request, we don't set the uri. I doubt that that was the issue. If you change to the April version does it work again? There wasn't a change in the Exchange connector last month as far as I know. Can you send a frown including the trace files?

[arify]

Also, is it possible for you to try the Microsoft Account (OAuth) in the credential dialog instead of username/password? For this to be used your Exchange server must be on O365. If you don't know, I'd say it's worth a shot 🙂

[trickytree83 · Accepted solution]

Hi,

Thanks for the reply. Our Exchange Server isn't on O365 so I'm unable to try the OAuth method.

I've managed to get it working again by uninstalling the existing version, attempting to install the version from April which gave me Error 2753 after clicking Finish on the installer and wouldn't launch the desktop app. So I uninstalled the April version and reinstalled the latest version (since I need one that works) and the connector has begun to work again. I couldn't possibly tell what was causing the issue, I suspect it'll be in the frown I sent when the connector wasn't working.

[wynhopkins]

Same issue, still unresolved