{"id":2752,"date":"2023-02-04T12:00:48","date_gmt":"2023-02-04T12:00:48","guid":{"rendered":"https:\/\/modern-workplace.uk\/?p=2752"},"modified":"2023-03-07T11:39:15","modified_gmt":"2023-03-07T11:39:15","slug":"teams-virtual-sbc-closing-azure-network-ports-warnings-for-azureloadbalancer-and-virtualnetwork-2-2-2-2-3-2-3-2-2-2-2-2-3-2-2-3-2-3-2-2-2-3-2-2","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=2752","title":{"rendered":"Domain Reuse Headaches: why Purchasing a Domain Previously Used with Microsoft 365 is not a Good Idea"},"content":{"rendered":"\n
\n\n\n\n

I bought a domain for a work project from GoDaddy without knowing that the domain was previously used from another company and registered in their Microsoft 365 tenant. I am sure it is a scenario that will happen more and more often in the forthcoming years. <\/p>\n\n\n\n

All looks good until you go try to register the domain and you get the error you can see in the image below (note that I have access to the DNS, so the ownership verification for the domain goes well)<\/p>\n\n\n\n

“We have confirmed that you own azuretest.uk, but we can’t add it to your account because the domain is already added to a different Microsoft 365 organization: “companyname”.onmicrosoft.com. Sign in to the admin center as an admin for that organization, and remove the domain azuretest.uk. Try resetting the admin password if you can’t sign in. You should be able to add the domain azuretest.uk here after taking that step. If you can’t access “companyname”.onmicrosoft.com, please contact our support team for help.”<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Before accepting that I had to contact the Microsoft support team (that is usually painful) I tried to<\/p>\n\n\n\n

a) Verify the domain with different DNS records (hint: it makes no difference)<\/p>\n\n\n\n

b) Follow the steps outlined in Take over an unmanaged directory as administrator in Azure Active Directory<\/a> (I hit the same wall, as you can see in the image below, just in a different way)<\/p>\n\n\n\n

“This domain has been previously configured on “companyname”.onmicrosoft.com using an existing Azure AD or Office 365. To verify this domain name, you will first need to remove the domain name from the existing directory.”<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

So, I tried to call the support. After a long walk trough different menus (accept twice the registration twice, verify your phone number and so on) the support agent tries the same steps outlined in the “Take over” post and then the phone connection was interrupted (doh!)<\/p>\n\n\n\n

I have a support ticket open now and I will update this post when news happen \ud83d\ude42<\/p>\n\n\n\n

Update: the solution is outlined here Reclaiming a Domain: Unlocking a Domain Previously Used with Microsoft 365<\/a> <\/p>\n","protected":false},"excerpt":{"rendered":"

Did you buy an Internet domain only to find out it was previously used for Microsoft 365 by another company? You’re not alone! This is a common scenario that’s bound to happen more frequently in the future. Despite attempting to register the domain and verifying ownership, you may encounter an error message indicating that the domain is already added to a different Microsoft 365 organization. Attempting to follow the steps outlined in the Azure Active Directory’s “Take over” process may also lead to the same result. Even reaching out to Microsoft support may not resolve the issue immediately<\/p>\n","protected":false},"author":1,"featured_media":2753,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","twitterCardType":"","cardImageID":0,"cardImage":"","cardTitle":"","cardDesc":"","cardImageAlt":"","cardPlayer":"","cardPlayerWidth":0,"cardPlayerHeight":0,"cardPlayerStream":"","cardPlayerCodec":"","footnotes":""},"categories":[810,753,757],"tags":[762,759,77],"class_list":["post-2752","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-810","category-microsoft365","category-office-365","tag-microsoftteams","tag-microsoft-365","tag-office-365"],"_links":{"self":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2752","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2752"}],"version-history":[{"count":3,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2752\/revisions"}],"predecessor-version":[{"id":2808,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2752\/revisions\/2808"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/media\/2753"}],"wp:attachment":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2752"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2752"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}