Dynamics Community Forum Thread Details

Can't get App for Outlook to work (OWA or Desktop)

As the subject says, I can't get App for Outlook to work, either in OWA or desktop Outlook. This happens whether I'm on our internal site (we're on prem), or external. I just keep getting the login prompt over and over.

ADFS/IFD itself works - I can go to our external URL from outside the network and login just fine. If I enter an incorrect login, I see it in the ADFS logs. However, I see no trace in the logs of the failed requests from the Outlook app.

We're fully updated on the CRM server - 8.2.1, IIRC? Outlook is 2016. Have tried OWA from multiple browsers on multiple machines/networks. Mail server is Office365. Mailboxes/server connections seem to be configured properly, as this same machine was able to work just fine with the older Outlook installed CRM connector application.

Just trying for myself right now, and I'm a system admin user, so privileges shouldn't be an issue. Followed all of the settings re: trusted sites and whatnot from https://technet.microsoft.com/en-us/library/dn946901.aspx. Ran the ADFS Client registration on the AD FS server with the command given under settings, etc... I saw a comment that it might be missing a slash, which it does kinda look like, so tried it with adding the slash between the server name and org name, still no go.

Any thoughts as to what else might be wrong, or how to further troubleshoot? Without anything coming up in the logs I'm a bit stuck re: where to move on this.

Just got off the phone with support - broke down and gave my credit card to get charged for the ticket... Good news is I'm not getting charged, bad news is that's because it's a known bug. They're already working on the hotfix.

Two bits of interest - 1. Even if your settings page gives you the internal URL to register for the app, you need to use the external URL (and therefore the external URL needs to resolve properly/authenticate properly in your internal environment - ours does, so that wasn't the issue, but I wasn't 100% certain I was doing things correctly when I tried that. And 2. the current workaround, if you can call it that, is to use OWA through Chrome, cancel out of the authentication pop-up, and then it'll give you a new full page to log into. It worked after that. O.o

Quick Links