Hey everyone! Tomorrow night, I'm making the leap to migrate our Azure tenant to a new domain name. This is my first time handling something like this, and honestly, the pressure is on me since I don't have anyone in my organization I can bounce ideas off of. We're fully cloud-based in Azure, not hybrid. From what I understand, all I need to do is go into the M365 portal and set our new domain name as primary. But I'm really anxious about what happens after that—specifically, will Single Sign-On (SSO) transition seamlessly? Will User Principal Names (UPNs) be affected? Do I need to update users' email addresses, or will that happen automatically? I would really appreciate any guidance from anyone who's been through this before. Thanks in advance!
4 Answers
Don't stress too much about it! Starting is the hardest part, and there’s not much here that can go wrong initially. First, you need to get the new domain from a registrar you trust and add it to your tenant. This includes verifying DNS records to show Microsoft you own the domain. After that, assign the new domain to your users' accounts, and you're off to a good start!
Once your new domain is set up, think about whether you want it to be the primary user account name. Keeping the old domain might actually provide a bit of security, if nothing else. Then you’ll want to configure your MX, SPF, DKIM, and DMARC records so everything regarding email can flow correctly. Setting domain aliases for your users can help them receive emails from both domains, and don’t forget to update your SharePoint site’s name when you're ready!
Congrats on taking this on, I understand it can be daunting! I've dealt with domain changes in MS365 before, and it actually goes pretty smoothly. After you add the new domain, just make sure to update the DNS records and let your users know to expect a little downtime with email as the changes take effect. From what I've seen, once users switch over to the new domain, Microsoft automatically sets the old one as an alias, making things easier.
As for SSO, I’m not certain how that will change, but I’d love to hear if someone else has insights on that!
Just a heads up, you'll likely need a script to add the new email alias and update the user principal names (UPNs) to set the new domain as primary. This might also involve tweaking email signatures and branding for consistency. Don’t forget to check your SPF, DKIM, and DMARC settings on your new domain, and be sure to update the from addresses on any sending devices, like printers. If you get some of this ready in advance, it could make things smoother. Just not sure about the SSO part, though!
Oh, and make sure to take care of the SharePoint specifics too. You can follow Microsoft's guide for that here: [Change your SharePoint domain name](https://learn.microsoft.com/en-us/sharepoint/change-your-sharepoint-domain-name). It's more involved, so don’t skip it!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures