09-15-2020 03:08 AM
09-15-2020 03:08 AM
I have a legacy custom domain (e.g. email@example.com) which I initially linked to outlook.com via Outlook Premium several years ago prior to the service being depricated by Microsoft, and transferred into a Microsoft 365 Family subscription. The domain is not registered or hosted by GoDaddy and has continued to work flawlessly. I have been able to log into all Microsoft Services using (firstname.lastname@example.org) and setup email via Outlook desktop app and Android email clients.
I received an external guest invite to MS Teams through my custom domain address (e.g. email@example.com). It asked me to enter a new password and appears to have created an Azure AD domain for my custom domain, together with a user under Azure AD account for firstname.lastname@example.org.
Outlook and my Android email clients now want to connect to the Work & IT login for email@example.com rather than my personal microsoft account firstname.lastname@example.org. As I don't have email associated with Azure AD it doesn't work.
Email is still sending and receiving through to my outlook.com account via my custom domain, however the autodiscover DNS CNAME now isn't working so Outlook and other mail clients can't get the configuration information.
When I go into Manage Premium through outlook.com and select Personalized email address, it shows the error message We couldn't connect the domain mydomain.com to Outlook. Cancel setup and try again.
I don't want to cancel as I'm concerned that it may further mess up my custom domain, and I won't be able to use it via outlook.com without transferring it to GoDaddy. I also have a bunch of user alias set up with is a legacy feature that is no longer supported and I don't want to lose that.
I've changed my primary account alias in outlook.com back to my old hotmail login, and I can now at least connect via Outlook and other mail clients using the hotmail login.
Microsoft support have been pretty useless and have bounced me around all over the place. It's a struggle to get to chat to anyone.
Is there a way to fix what has been done or am I pretty much stuck with it now?
09-16-2020 02:25 AM
@kesawiyou could perform an admin takeover for the Azure AD tenant and remove the domain. The "internal admin" takeover should do it:
09-16-2020 04:02 PM
09-17-2020 01:46 AM
@kesawi, removing a domain does not remove the tenant. After removing a domain, user(s) can still use the @<yourtenant>.onmicrosoft.com domain.