Reconnect of outlook.com account in Outlook 2016 does not work or at least not correctly

Hello Holger,

We would like to know the additional information to better assist you with connecting an email account in Outlook.com concern. Are you trying to connect a personal or a business email account? What is the exact error that you get when attempting to connect the email that you used in Outlook 2016 to Outlook.com?

We are looking forward to your response.

Regards.

How do i know wether i have a personal or a business account. I didn't know that outlook.com offers different account types other than free and ad-free. At the moment i still use the free version.

• When i add the account, it looks like everything is working fine, i get the Message "Herzlichen Glückwunsch! Das E-Mail-Konto wurde erfolgreich konfiguriert und kann jetzt verwendet werden." (Congratulations!The e-mail account has been successfully configured and can now be used.).
• Then i get the message "Outlook muss neu gestartet werden, damit die aktuellen Änderungen übernommen werden." (Outlook must be restarted to accept the current changes.)
• After restarting i get the Message "Der Name stimmt mit keinem Namen in der Adressliste überein." (The name does not match any name in the address list.)
• When Outlook then has opened there was a "Private Ordner" (private folder) which was in no way accessible. A corresponding account doesn't exist.
  
• After restarting again the folder wasn't there anymore.

The errors where different, before i added the autodiscovery entries to my domain, but i think that was "Ok" because Outlook could not know anything about the outlook.com account without autodiscovery.

btw i created a subdomain "autodiscover.mydomain.tld" with the CNAME entry "autodiscover.outlook.com" which resolves the following way:

• autodiscover.mydomain.tld is an alias for autodiscover.outlook.com.
  • autodiscover.outlook.com is an alias for autodiscover.geo.outlook.com.
    • autodiscover.geo.outlook.com is an alias for autodiscover.outlook.com.g.outlook.com.
      • autodiscover.outlook.com.g.outlook.com is an alias for autodiscover-emeaeast.outlook.com.
        • autodiscover-emeaeast.outlook.com has address 40.96.15.216
        • autodiscover-emeaeast.outlook.com has address 132.245.74.104
        • autodiscover-emeaeast.outlook.com has address 132.245.193.136
        • autodiscover-emeaeast.outlook.com has address 40.101.0.168
        • autodiscover-emeaeast.outlook.com has address 40.96.21.232
        • autodiscover-emeaeast.outlook.com has address 40.101.18.40
        • autodiscover-emeaeast.outlook.com has address 40.101.9.208
        • autodiscover-emeaeast.outlook.com has address 132.245.240.184
        • autodiscover-emeaeast.outlook.com has address 132.245.229.136
        • autodiscover-emeaeast.outlook.com has address 40.101.4.200
        • autodiscover-emeaeast.outlook.com has IPv6 address 2603:1026:300::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:2d8b::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:53af::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2603:1026:203:2b::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:8829::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:8414::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:5323::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2603:1026:200:3d::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:8014::8
        • autodiscover-emeaeast.outlook.com has IPv6 address 2a01:111:f400:303e::8

Very intressting, I have the same problem with my private domain as well.

Hope we can have an serious answer here.

The email domain might be given by company to access your email. Did someone provide you the email address or did you create it personally? If you are using an email address that is give by the company, you need to contact your IT or administrator to know what server is needed.

Regards.

Hello Martin,

You mentioned that you are having issue on a private domain, we would suggest you to call your IT or administrator for better assistance.

Regards.

Thank you, sorry for slow response...

When I signed up for my office 365 home account, I used my private adress: ( myname @ mydomain .com )
I used this adress to  config outlook app in computer using mailserver dub-m.hotmail.com. 

When MS changed config this autum to use Exchange servers I can't setup Outlook app using my private adress any longer. 

The app connect to the server ok when I use my outlook.com alias. But result is that I can't send mail using my private adress.

However, I can connect to webbmail using my private mail but I prefer to use the app in my computer.

I think the problem is that autodiscover in the app try to connect to autodiscover. mydomain... instead of connecting to autodiscover. outlook...  

Best Regards

/martin

If your webmail still works that is a good sign.

Check that your DNS Autodiscover record for your *private* domain, for which the email addresses are hosted on free Outlook.com, points to Outlook.com correctly.

My Autodiscover record says:

• NAME: autodiscover.privatedomain.com
• TYPE: CNAME
• RECORD: autodiscover.outlook.com
• CLASS: IN
• TTL: 3600

It might take 1 - 24 hours before you can set up Outlook to use access your private mailbox again (depends on how fast your DNS updates)

If it still doesn't work, leave your Autodiscover record alone because the problem it took a few days before my connectivity problem automagically went away (Microsoft made a backend fix).

I had a similar issue with email addresses in two private domains that used free Outlook.com as the email host, but this is now fixed. These private domains were added to Outlook.com before the private domain service for free mailboxes was withdrawn. The forthcoming Outlook.com Premium service will allow this again, or you can use on of the fee-case Office 365 offerings.

Thank you! I will try that.

(Only sad that Microsoft didn't inform about this when they made that big change..)

/martin

I really would like to hear what is the difference between a personal domain and a domain given by company in conjunction with using outlook.com?

I got reply from support and i have bad news: non-outlook.com-domains will not work with outlook.com anymore. At least they don't work in a useable way. Support told me that external domains only work through pop/imap in this so much better outlook.com - it is so much better that i have to leave outlook.com now, as the main (only?) reason to use outlook.com has gone and for pop/imap everything else is better than outlook.com. I needed my domain/email provider all the time as a backup for outlook.com, as outlook.com deletes eMail without my permission. I don't sort my spam, as it is in most cases simply spam but especially outlook.com put a lot of important eMails into Junk-E-Mail and deletes it after (only) two weeks. So it is very important to not trust/rely on microsoft and have a backup solution by the hand.

premium.outlook.com as ThumperNut mentioned is even less an alternative! As it is my own domain i handle all the eMail-adresses of my family and personally i use custom eMail-adresses for nearly every registration in this way *** Email address is removed for privacy ***. This makes it easy to track down spamming and it's more secure if any service is hacked. With outlook.com's greatness i would have to setup every eMail seperately and i can only use 5 eMail-addresses - that is for sure not an option but it's a bad joke for a self called "premium" service.

But it looks like this is the latest product philosophy to try to force people to use microsoft services. In my case they have already lost a lot office 365 subscriptions, because it doesn't install together with the "normal" Visio licenses. They couldn't force me to use Visio 365 additionally to my existing Visio licenses (too pervert in my eyes) but they forced me to try LibreOffice and guess what we replaced even Visio. This way there is a lot of money free for support cases and if i think about it - with microsoft products the most support cases were because of licensing terror.
Now they lose my personal eMail accounts and as i am involved in technical decisions in my company and due to the bad experiences with microsoft and much better experiences with alternative products lately, "bye Microsoft" will be the way to go