This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
What DNS entries do I need make to get M365 Family to verify my domain? It looks like I would need a unique id for my instance, but I am unsure how to get it.
Thus, What DNS entries do I need make to get M365 Family to verify my non-godaddy domain?
David
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Jos,
Do you have the "_domainconnect"? Take a look at Ed's Blog. He has done a great job describing the details of the setup.
David
I know the instructions on Ed's blog worked as I tested them a few weeks ago.
However, when I try and use the process today the "domainconnect" no longer seems to pop up and so I can't capture the info from the URL.
Has anyone else seen this behaviour?
This worked for me just now. I get the domainconnect pop up as follows:
I was interested to see if I could replace my Legacy G.Suite mail system with Microsoft's. Following all the steps worked with mail arriving in my outlook.com mailbox.
However, only being able to use a single address is a huge limitation so I reverted to Google's. I need catchall messages and other aliases under the same domain. Why don't Microsoft do this properly?
Aliases and catch-alls are the one thing I miss the most that our old email did but this new microsoft stuff doesn't. Imagine a sales lead or client sends you something important but oops, got one character wrong in the email address before the "@" sign. With catch-all it still went through to our catch all account and we could resolved the issue or act on the email.
This isn't really a good answer to why Microsoft doesn't do this but I think it's valid...quite frankly Microsoft sucks, is too big for their own britches and totally out of touch with what their users really want. It's almost like they don't try hard enough on a lot of their products and just want to ride the gravy train. Meanwhile competitors and new vendors are catering to what Microsoft lacks. They need to be brought down a few pegs IMO. I think a lot of it had to do with when they thought it was a good idea to get rid of all those employees. Think of all the talent and ideas that went bye bye from that bonehead move.
This worked for me just now. I get the domainconnect pop up as follows:
- Outlook.com's settings
- View all outlook settings
- Premium
- Features
- Under Personalised email address click Get started
- Click Get a domain
- Pop up browser window with GoDaddy logo appears - get your mxRecordValue from the URL
I was interested to see if I could replace my Legacy G.Suite mail system with Microsoft's. Following all the steps worked with mail arriving in my outlook.com mailbox.
However, only being able to use a single address is a huge limitation so I reverted to Google's. I need catchall messages and other aliases under the same domain. Why don't Microsoft do this properly?
The site is different now in how to check for a godaddy domain. you cant see the url at all.