Hey Scott Buchanan, totally get where you’re coming from changing your Azure DevOps URL can feel a bit nerve-wracking, especially with the domain switch involved. Here’s the lowdown to help you move forward confidently:
- Changing the Custom Name vs. Switching Domain Unfortunately, these two aren’t a single-step process. When you update your custom name (the part before
.visualstudio.com
), that change doesn’t automatically update the preview for the new domain (https://dev.azure.com/XXX
). They’re somewhat independent settings. - What Happens When You Enable the New Domain? The confirmation message you’re seeing is standard. It’s warning you that enabling the new domain is a one-way action once switched, you can’t easily revert to the old
.visualstudio.com
URL. So yes, it’s not just a warning; it will commit the switch once confirmed. - Recommended Approach
- First, change your custom organization name and make sure everything works fine on the old domain.
- Then, when you’re ready and sure, enable the new domain (
dev.azure.com/XXX
). Accept the confirmation knowing it’s a permanent move. - Make sure to notify your team/users about this change because URLs will update.
- Backup & Communication Before you commit, backup any critical links, update your documentation, and inform your stakeholders. This reduces surprises and smooths the transition.
You’re not being chicken it’s smart to be cautious! But the process does require two steps, and the confirmation message means you’re about to finalize the switch. If you’ve tested the new custom name and are ready, go ahead with enabling the new domain.
Hope this helps! If you want, I can also share official MS docs or a checklist to guide you through.