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(188.79999999999998, 73%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJO%3C/text%3E%3C/svg%3E)
Can you please allow support in case your co-pilot advices that you as support need to do something. I moved away a domain from one tenant to another and my outlook cannot find the new tenant and want to sign in continuously into the old tenant. Very frustrating that a lot of copilot and still engineers are around which do not fix things.
We moved our domain xx from an old Microsoft 365 tenant to a new tenant (xx). The domain was removed successfully from the old tenant. However, Azure AD authentication is still being routed to the old tenant with ID xx, causing sign-in failures with error AADSTS90072. Please perform an Azure AD backend domain orphaned-reference cleanup (hard domain release / routing reset) to remove stale domain metadata. This issue cannot be resolved from the admin portal or DNS — it requires backend cleanup.
Moved from: Microsoft 365 and Office | Other
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
FIXED with help of a system administrator providing a power shell script. Weeks busy with support from India without any working solution. Drama!
![](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(310.4, 15%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDV%3C/text%3E%3C/svg%3E)
Hello @Jelle Ossewaarde | VOICE4ALL,
Thank you so much for the update.
I sincerely apologize for the inconvenience you experienced while contacting Microsoft Support. However, I am very glad to hear that your issue has now been resolved.
If you need any further assistance or have additional questions, please feel free to let me know. I am always here to help.
![](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(147.20000000000002, 59%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Hello @Jelle Ossewaarde | VOICE4ALL,
Welcome to the Microsoft Q&A forum.
Thank you for sharing the details with us. Based on the information you provided, it appears that you are encountering the AADSTS90072 error when trying to sign in to Office 365 services, such as Outlook, OneDrive, or Teams after migrating your domain to a new tenant.
To better assist you, could you please provide a full screenshot of the error message? Also, please make sure you are accessing Outlook using an Incognito/InPrivate window to avoid any cached information interfering with the login process.
As the next steps may require sharing personal information, we have sent you a private message where you can safely provide the necessary details. Please check the private message by looking for the banner displayed above the question title, as shown in the screenshot below.
I look forward to hearing from you.
Hello @Jelle Ossewaarde | VOICE4ALL,
Have you had a chance to review my previous update in Private Message? Please feel free to let me know if you still have any concerns or need further assistance.
I look forward to hearing from you.
FIXED with help of a system administrator providing a power shell script.
It sounds like you're experiencing issues with Azure AD authentication after moving your domain from one Microsoft 365 tenant to another. Unfortunately, the problem you're facing, specifically the AADSTS90072 error, indicates that the Azure AD still has references to the old tenant, which can cause sign-in failures.
To resolve this issue, a backend cleanup is indeed required to remove stale domain metadata. This type of cleanup cannot be performed through the admin portal or DNS settings; it typically requires action from Microsoft support to reset the routing for the domain.
I recommend reaching out to Microsoft support directly for assistance with this backend cleanup. You can do this by going to the Microsoft 365 admin center, selecting Help & Support, and then following the prompts to contact technical support.
Additionally, ensure that all necessary configurations are correctly set up in the new tenant to avoid further issues with authentication.