Tenant Rename Leaves Old SharePoint URLs: Root Cause and Fix

When you rename your Microsoft 365 tenant, you expect all services to reflect the new domain. But SharePoint Online keeps the original tenant name in site collection URLs, document library paths, and sharing links. This mismatch causes broken links, failed file access, and confusion for users who see the old URL in their browser. The problem is by design: SharePoint does not support automatic URL renaming for existing sites. This article explains why the old URLs persist and gives you the exact steps to create a new tenant, migrate content, and redirect users to the correct addresses.

Why SharePoint Keeps the Old Tenant Name in URLs

The Microsoft 365 tenant rename feature, available in the admin center, changes the initial domain (for example, contoso.onmicrosoft.com becomes newcontoso.onmicrosoft.com) and updates the default SharePoint domain. However, the rename does not modify the URL of any existing SharePoint site collection. A site created under the old tenant name keeps that name in its URL forever. The reason is technical: SharePoint site collections are bound to a specific URL at creation time. Changing that URL requires rebuilding the site collection, which the rename tool does not do.

Additionally, SharePoint Online uses the tenant name in document library paths, file version history, and sharing links. These links are stored in databases and cached by clients. A rename operation cannot update all these references without risking data loss or downtime. Microsoft chose to leave existing URLs intact to guarantee stability for active sites.

The result is a split experience. Exchange and Teams display the new domain, but SharePoint continues to show the old tenant name in every URL. Users who click a bookmarked link or a shared file link see the old address and may get a 404 error if the original site still exists but the link is cached incorrectly. The only clean fix is to create a new tenant with the desired name and migrate your SharePoint content there.

Steps to Fix the Old SharePoint URL After a Tenant Rename

These steps assume you have already completed the tenant rename in the Microsoft 365 admin center. You will create a new tenant, migrate your SharePoint sites and files, and set up URL redirects so users land on the correct addresses.

Method 1: Create a New Tenant and Migrate SharePoint Content

1. Create a new Microsoft 365 tenant with the desired domain
   Go to the Microsoft 365 admin center and sign up for a new tenant. Use the exact domain name you want for SharePoint URLs. For example, if you want contoso.sharepoint.com, the tenant must be contoso.onmicrosoft.com. Complete the setup and verify domain ownership.
2. Enable SharePoint in the new tenant
   In the new tenant, go to the SharePoint admin center and create a root site collection. This action activates SharePoint Online for the new tenant. Note the new root URL, such as https://contoso.sharepoint.com.
3. Migrate site collections from the old tenant
   Use the SharePoint Migration Tool (SPMT) or a third-party tool like Sharegate or Metalogix. In SPMT, select the source site collection URL from the old tenant (for example, https://oldcontoso.sharepoint.com/sites/projectx) and the destination URL in the new tenant (https://contoso.sharepoint.com/sites/projectx). Start the migration. SPMT copies all files, lists, permissions, and metadata.
4. Migrate OneDrive for Business libraries
   Each user’s OneDrive library is tied to the tenant name. In the old tenant, ask users to download their files or use the OneDrive sync client. In the new tenant, users sign in and upload their files. For large libraries, use the SharePoint Migration Tool with the OneDrive source option.
5. Update DNS records and custom domains
   If you use custom domains (for example, share.contoso.com), update the CNAME record in your DNS provider to point to the new SharePoint tenant URL. This change can take up to 48 hours to propagate.

Method 2: Set Up URL Redirects from Old SharePoint to New SharePoint

1. Create a redirect site collection in the old tenant
   In the old SharePoint admin center, create a new site collection that will serve as the redirect hub. Name it “Redirect” and use a simple URL like https://oldcontoso.sharepoint.com/sites/redirect.
2. Install a redirect web part or use a page redirect
   On the redirect site, create a page for each migrated site. Use the “Link” web part with a URL that points to the new site. Alternatively, use a script editor web part with JavaScript that checks the current URL and redirects to the matching new URL. For example, if the user visits https://oldcontoso.sharepoint.com/sites/projectx, the script redirects to https://contoso.sharepoint.com/sites/projectx.
3. Update bookmarks and shared links
   Notify all users to update their bookmarks and replace shared links with the new URLs. Provide a list mapping old site names to new site names. This step is manual but necessary because the old tenant will eventually be decommissioned.
4. Test the redirects
   Open an incognito browser window and navigate to an old site URL. Confirm that the page redirects to the new site within two seconds. If the redirect fails, check the script or web part configuration.

If SharePoint Still Shows the Old Tenant Name After the Fix

Old SharePoint site still appears in search results

Search results may cache old site URLs for up to 30 days. In the old SharePoint admin center, go to Search > Result Sources and remove the source that points to the old tenant. Alternatively, users can clear their browser cache and re-index the new sites by requesting a site re-index in the new site collection settings.

Shared file links still point to the old tenant

Links that were shared before the migration remain valid only if the old site still exists. After the old tenant is decommissioned, those links break. To avoid this, use the “Check permission” feature on the new site to see who has access and send them a new sharing link. For critical files, consider using a link-shortener service that updates the destination URL centrally.

OneDrive sync client shows the old tenant name

The OneDrive sync client stores the tenant URL in its configuration. After migration, users must stop syncing the old library and start syncing the new library. In the OneDrive settings, click “Stop sync” for the old library, then go to the new OneDrive library in a browser and click “Sync” to reconnect.

Item	Old Tenant URL	New Tenant URL
Root SharePoint site	https://oldcontoso.sharepoint.com	https://contoso.sharepoint.com
Team site	https://oldcontoso.sharepoint.com/sites/sales	https://contoso.sharepoint.com/sites/sales
Document library path	https://oldcontoso.sharepoint.com/sites/sales/Shared%20Documents	https://contoso.sharepoint.com/sites/sales/Shared%20Documents
OneDrive root	https://oldcontoso-my.sharepoint.com	https://contoso-my.sharepoint.com
Sharing link example	https://oldcontoso.sharepoint.com/:w:/r/sites/sales/_layouts/15/Doc.aspx?sourcedoc=%7Babc%7D	https://contoso.sharepoint.com/:w:/r/sites/sales/_layouts/15/Doc.aspx?sourcedoc=%7Babc%7D

The only way to get rid of the old tenant name in SharePoint URLs is to create a new tenant and migrate your content. The tenant rename tool does not touch existing SharePoint site URLs. After migration, set up redirects from the old sites to the new sites so users do not encounter broken links. Use the SharePoint Migration Tool to automate the bulk of the work and test all redirects before decommissioning the old tenant. For OneDrive, instruct users to stop syncing the old library and sync the new one. Once the old tenant is removed, all old URLs will return a 404 error, so complete the migration before that happens.