Sign up for Office 365
Learn more about Office 365
We've successfully verified our domain and have confirmed MX record propagated, From Outlook Online, we can successfully send and recieve messages on out test account. Unfortunately, it doesn't appear that Autodiscover is functioning. When we perform an NSlookup, we recieve back:
To my understanding, this is a valid resolution, however when trying to connect Outlook 2007 from two seperate machines in different geographical loacations, both failed.
We're open to suggestions.
I have checked the DNS records of your domain. The TXT record and MX record are correct.
Have you used the steps in KB article http://support.microsoft.com/kb/2404385/en-us ? If not, please refer the steps in that KB article to fix the issue. If the issue persists, please provide the detailed error message appears when adding this Office 365 account in Outlook 2007.
0 out of 1 people found this post helpful.
None of the suggested items the first time around resolved the issue. The final solution was to open a service request from the Exchange Online Admin console and report the problem. The first solution was to switch the server to m.outlook.com which did work.... for about 24 hours. A second ticket was opened and at the point Microsoft pulled a rabbit out of their hat server side (I.E. Someone actually did something other than speculate) and the problem magically went away.
Obviously the source problem nor resolution of how the problem on their side was never given.
Thank you for your reply. I have tried all the steps in the article you referenced. As previously stated, the Outlook Autodiscover test using the www.testexchangeconnectivity.com tool came back successful. The Outlook Anywhere (RPC over HTTP) test failed. However, there is no guidance from MS on how to troubleshoot a failed RPC over HTTP result.
I tried the Oultook manual server config (as noted in the article you referenced), but this returns an error that the "Exchange server is not online or is unavailable". After brute forcing my way through the manual config and starting Outlook, Outlook prompts for a username and password, and the auth request does not go through using the same credentials that work for the OWA login. I made sure I was using the email address as the username and the correct password (many, many times). Again, these same credentials work if I login to OWA.
You can explore that option. If there is any progress, you can share with us in the forum.
We found out that we were signed up for a "kiosk" plan (Office 365 K1), which does not support connecing to Exchange from Outlook. I have changed our licenses to Exchange Online Plan 1 by calling Billing Support and everything is working great now.
I hit this issue today as well. In our case, MAPI was disabled during the mailbox move.
Certainly worth a look in the Exchange Admin Portal -> Mailbox Features section if anyone else sees this.