I'm in a bit of a tight spot here! Tomorrow night, we're migrating our Azure tenant to a new domain name, and it's all on me. Unfortunately, I can't test anything since we don't have a test environment. I'm looking for any advice or insights from anyone who's done this before. From what I've gathered, all I need to do is go to the M365 portal and set the new domain as primary. But I'm worried about what comes next: Will Single Sign-On (SSO) work? Will the User Principal Names (UPNs) change? Do I need to script out email address updates, or will they just change automatically? I really appreciate any help as I'm feeling a bit overwhelmed. Thanks a lot!
2 Answers
Don't sweat it too much; the first few steps are pretty straightforward and can't really go wrong. Just get your new domain from a trusted registrar, add it to your tenant (including verifying DNS), and assign it to your users' accounts. Once that’s done, decide if you want the new domain to be the primary user name as well. It can be a good idea to set up MX, SPF, DKIM, and DMARC for email. You can keep the old domain as an alias so your users can still receive emails sent to that address. And remember to set the default outgoing email as needed. Oh, and don’t forget about SharePoint; that also needs a name change! It’s all manageable step by step. Good luck!
Congrats on taking this on! I've gone through domain changes in MS365 too. Once you add the new domain, update your DNS records, and warn users of any potential downtime while the changes propagate, it should go pretty smoothly. Just make sure everyone transitions to the new domain in their user settings; Microsoft will handle the old domain as an alias automatically. Still unsure about how this will impact SSO—hopefully others can shed light on that!
Thanks for the encouragement!