Hi all

Having a big problem with this recently and need your help to understand if Microsoft has made a general change with Office 365 Family accounts with personalized domains, or if it is just my individual problem.

I’ve been running Outlook on my PC with a Office 365 Family account and personalized / custom domain @NotMyRealDomain.EMAIL using namesilo.com for DNS for 1.5 years.

Everything worked fine, although in my online (outlook.live.com) web-based mailbox under Settings->Premium–>Personalized Email Address, it has always said “We couldn’t connect the domain NotMyRealDomain.EMAIL to Outlook. Cancel setup and try again.” But as I said everything worked so I didn’t mess with this. (Now if I press “cancel setup” it warns me that this will disconnect my personalized domain and I wont be able to restore it due to MS discontinuing support for personalized domains in the Office Family plan. So I’m definitely not pressing that button.)

The problem is that my Outlook profile is corrupted (I think) and to debug the problem I need to create a new profile. But I cant.

When I try to create a new profile, it fails to add my mailbox using Autodiscover. I enter my email address RON@NotMyRealDomain.EMAIL and my password, it tries to setup outlook and eventually fails. Manual setup also fails. In some cases it complains the username RON@NotMyRealDomain.EMAIL is incorrect, in other cases it says it cannot contact the server. At the same time, I have no problems using this email address using the web-client.

This worked 3-4 months ago, and nothing changed except I updated my version of Office.
So I suspect that Microsoft changed something with how Outlook recognizes and/or configures mailboxes.

Can somebody who runs outlooks with a Family 365 account with a personalized domain (ideally not on godaddy) please try to create a new additional profile to see if you have the same issue?

If it works OK for you and if you are not running the latest version of Outlook (Outlook for Microsoft 365 Version 2404 Build 16.0.17531.20128 MSO 64-bit, the latest Current Channel version) can you try updating your Office to see if that causes the problem?

If indeed MS changed something it could be bad news…

thanks for your help!

​Hi allHaving a big problem with this recently and need your help to understand if Microsoft has made a general change with Office 365 Family accounts with personalized domains, or if it is just my individual problem.I’ve been running Outlook on my PC with a Office 365 Family account and personalized / custom domain @NotMyRealDomain.EMAIL using namesilo.com for DNS for 1.5 years.Everything worked fine, although in my online (outlook.live.com) web-based mailbox under Settings->Premium–>Personalized Email Address, it has always said “We couldn’t connect the domain NotMyRealDomain.EMAIL to Outlook. Cancel setup and try again.” But as I said everything worked so I didn’t mess with this. (Now if I press “cancel setup” it warns me that this will disconnect my personalized domain and I wont be able to restore it due to MS discontinuing support for personalized domains in the Office Family plan. So I’m definitely not pressing that button.)The problem is that my Outlook profile is corrupted (I think) and to debug the problem I need to create a new profile. But I cant.When I try to create a new profile, it fails to add my mailbox using Autodiscover. I enter my email address RON@NotMyRealDomain.EMAIL and my password, it tries to setup outlook and eventually fails. Manual setup also fails. In some cases it complains the username RON@NotMyRealDomain.EMAIL is incorrect, in other cases it says it cannot contact the server. At the same time, I have no problems using this email address using the web-client.This worked 3-4 months ago, and nothing changed except I updated my version of Office.So I suspect that Microsoft changed something with how Outlook recognizes and/or configures mailboxes.Can somebody who runs outlooks with a Family 365 account with a personalized domain (ideally not on godaddy) please try to create a new additional profile to see if you have the same issue?If it works OK for you and if you are not running the latest version of Outlook (Outlook for Microsoft 365 Version 2404 Build 16.0.17531.20128 MSO 64-bit, the latest Current Channel version) can you try updating your Office to see if that causes the problem?If indeed MS changed something it could be bad news…thanks for your help!  Read More

​