Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Mac Outlook 2011 won't maintain persistent connection to Office 365

Posted on 2013-05-21
Medium Priority
Last Modified: 2013-06-06

My  problem is with Outlook 2011 for Mac being unable to maintain a persistent connection with Office 365 Exchange.
I have two separate Macs and both experience the same problem.
When I launch Outlook it automatically connects to the Office 365 servers, syncs and remains connected for a few minutes.
Then an interrupt appears and requests a password.
When I type in the password it is rejected. I have tried countless times and always with the same result.
I can use the Office 365 portal and OWA just fine.
I can use my Windows 7 machine, my iPad, and my iPhone --- all with no problem.
The Outlook 2011 DOES actually connect for a few minutes.
The connect time varies from a minute or so to about 10 minutes.
The behavior is not connection dependent. I get the same result wired or wireless and from multiple locations.
I did NOT have this problem for the years I used the same Outlook setup with Apptix — but they were running Exchange 2007.
I use the same Outlook 2011 connect another email account to Apptix's 2007 Exchange server and I experience no connectivity problems.
I have searched MSFT HELP and scoured the Internet. It seems there are many connectivity issues around Office 365.
The system DOES connect so we know the credentials ARE correct.
Note that I use another Outlook email account that successfully maintains a persistent connection to Apptix's Exchange 2007 server.
Note that Windows 7 machines, iPads, iPhones, and OWA all successfully connect and remain connected.
Note that the other email account using Apptix hosted Exchange DOES maintain its connectivity.
Question by:glafollette
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
  • 2
  • +1
LVL 28

Expert Comment

ID: 39185268
Don't use Exchange 365. Take a look at this. It may not be the answer, but may be a way to check your setup.

LVL 13

Accepted Solution

Ugo Mena earned 2000 total points
ID: 39185323
I am going to assume that you are hosting your own DNS... in which case you need to set up your own Autodiscover CNAME record to keep Outlook 2011 connected to Office 365.

How the Autodiscover service works with Outlook for Mac 2011:

Use a CNAME Record to Enable Outlook to Connect:
LVL 13

Expert Comment

ID: 39185363
I had this issue and still have this issue.
Kinda strange, had this with a Full Mac environment and contacted MS about IT, because it happend after the migration to Exchange 2013 on their Side. Spoke to someone for over an hour. 3 days later problem was gone. Another customer has also a Mac and a office 365 that I can't manage and also here is the problem. i guess there is something on their side, because I hadn't changed a bit to the Full Mac environment :)
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 39185462
I'm not certain I understand what's needed on the CNAME -- see attached file showing the current settings at GoDaddy. Are you saying I must make a change there?
LVL 13

Expert Comment

by:Ugo Mena
ID: 39185530
Yes. You will need to add a couple of MX, TXT and CNAME records (depending on your office 365 services) to your GoDaddy DNS.

Here are the specific instructions for GoDaddy's DNS:


Author Comment

ID: 39185715

I just received this email from Microsoft Office 365 Support:

I just wanted to inform you that currently this a known issue and our resources are working on it to get it resolved. Also  You can further identify this issue by collecting logs on the system having the issue by following the directions here under “Turn on logging” :


In the logs you will see a EWS response with a status=401 similar to the text below:
2013-05-08 17:08:25.802,0xFFFFFFFF,Outlook Exchange Web Services,Info,EWS: Received response on connection=0x7d2ea278; status=401. If you want to discuss more about this issue please let me know your preferred call back time.

Does this change your mind regarding the CNAME record solution?
LVL 13

Expert Comment

by:Ugo Mena
ID: 39185729
No it does not. You still need to have the right DNS records  in place.
LVL 13

Expert Comment

ID: 39192752
Ultralites, the Windows, ... Machines all have a connection to the Exchange online, so the DNS records are fine. Otherwise they wouldn't connect.
At this moment MS has a lot of problems with the connect of office 365 with office for Mac. Support person told me they were looking into it because a lot of people are having this problem.
If they migrated the account to Exchange 2013, then you'll have it. All my clients that are still on the Exchange online 2010 don't have this issue, the ones migrated to 2013 all have it. Except 1, where MS fixed it in their side after a lot of phonecalls
LVL 13

Expert Comment

by:Ugo Mena
ID: 39192808
Thanks for your reply Xaelian. I guess everyone has different opinions on what exactly is working and not working on Mac Office 2011 Outlook using Office 365. What works on Windows is not a good indication of what will work on Mac.

We have been using Office 365 since it was called BPOS and I have found that one's mileage will vary greatly depending on the MS support person that gets your service request.

Based on the DNS records I can see (posted) and using std dig and host commands, I would still say the autodiscover.thelafollettes.net CNAME entry is not setup correctly.
So no DNS records are not fine.

From what I can tell, this is what should be there:
CNAME 1: autodiscover.thelaffolettes.net      canonical name = autodiscover.outlook.com.
CNAME 2: autodiscover.outlook.com      canonical name = autodiscover.outlook.com.glbdns.microsoft.com.

Our fully Mac network (Office 2011/Office 365/ Exchange 2013) was having the same problems when we upgraded to Office 2011 and did not have the correct autodiscover CNAME entries in our local DNS

With the correct CNAME entries Outlook 2011 stays connected as expected.

Author Closing Comment

ID: 39225670
Excellent solution .... not even MSFT knew this!! Now Office for Mac actually works with Exchange on Office 365. Thanks.
LVL 13

Expert Comment

by:Ugo Mena
ID: 39225779
Right on! Glad you stuck with me on this. :)

Featured Post

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes how to import Lotus Notes Contacts into Outlook 2016, 2013, 2010 and 2007 etc. with a few manual steps. You can easily export and migrate Lotus Notes contacts into Microsoft Outlook without having to use any third party tools.
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question