A SharePoint tenant rename changes every site URL at the service level, but it does not touch a single character of embedded content. Every absolute URL in a site page, hyperlink column, email template, or web part still points to the old subdomain. The rename is silent about those; it is your job to find and replace them.
This guide covers what breaks, what does not, and how to replace all affected URLs across a tenant without editing each page by hand.
What Changes When You Rename a SharePoint Tenant
A tenant rename changes the subdomain portion of your Microsoft 365 URLs. If your old tenant name was contoso, the rename to contoso-corp changes the following:
| URL type | Old format | New format | Auto-updated? |
|---|---|---|---|
| SharePoint site collection URL | contoso.sharepoint.com/sites/hr | contoso-corp.sharepoint.com/sites/hr | Yes - by Microsoft |
| OneDrive for Business URL | contoso-my.sharepoint.com/personal/... | contoso-corp-my.sharepoint.com/personal/... | Yes - by Microsoft |
| Absolute hyperlink in a site page | https://contoso.sharepoint.com/sites/... | Still shows contoso - broken | No |
| Hyperlink column value in a list | https://contoso.sharepoint.com/... | Still shows contoso - broken | No |
| Quick Launch or global navigation link | Configured per site | May break depending on how the link was added | Partial - verify manually |
| Relative URL (/sites/hr/Shared Documents/...) | No domain in the URL | Continues to work | N/A - never broke |
The pattern is consistent: anything Microsoft controls at the service layer (site collection URLs, redirect handling) updates automatically. Anything stored as text inside a page or list item does not.
Where Broken URLs Hide After a Rename
Site page body content
Modern SharePoint site pages store their content as structured JSON in the page body. Text web parts, quick links web parts, and image web parts can all contain absolute URLs pointing to files, pages, or sites. When a page editor types a link or drags a file reference into a web part, the stored value is an absolute URL - tenant subdomain included.
News posts are also site pages and have the same problem. A tenant with three years of intranet news where articles link to each other by absolute URL has hundreds or thousands of embedded references to update.
Hyperlink columns in lists and libraries
SharePoint's Hyperlink and Picture columns store URLs as plain text in each list item. If those values reference the old tenant subdomain, every link in those columns stops working after the rename. They are not visible in the SharePoint admin center; you need a list-level content export or a search tool that scans list item field values.
Document content
Word documents, PowerPoint files, and Excel workbooks stored in SharePoint libraries may contain hyperlinks to other SharePoint pages or documents. A tenant rename breaks those links inside the Office files themselves. Replace Master can search for and replace the old URL string within the text of site pages and list columns, but links embedded inside Office document bodies require opening each file directly. Scope how many documents are affected before deciding whether to update them individually or accept the broken links until the next document revision cycle.
How to Find All Affected URLs Across the Tenant
Before replacing anything, scope the problem. A tenant-wide search for the old subdomain string tells you exactly how many pages and list items contain references that need updating.
- Export a site inventory. You need a list of every site collection in the tenant as a starting point. Report Master exports this as a flat Excel file with site URLs, last activity dates, and site type. Use it to decide which sites to prioritise and which to deprioritise (inactive sites can often be addressed after the main run).
-
Search for the old tenant domain string using Replace Master. Replace Master's find-across-tenant function scans site pages, news posts, and hyperlink column values across all selected sites and returns a match list. Search for the old subdomain string (for example,
contoso.sharepoint.com) without specifying a replacement value first. The match count tells you the scope before you commit to any changes. - Review the match list before replacing. Some absolute URLs in page bodies may be intentional references to external services, archived sites, or public SharePoint pages that you do not control. Reviewing the list before replacement avoids accidentally overwriting those.
Running the URL Replacement in Bulk
Once you have confirmed what needs updating, Replace Master handles the replacement across site pages and list columns in a single operation.
-
Set the search string to your old tenant subdomain. For example:
https://contoso.sharepoint.com. Do not include a trailing slash, as some stored URLs include it and some do not. The partial-match replacement handles both. -
Set the replacement string to your new tenant subdomain. For example:
https://contoso-corp.sharepoint.com. Replace Master replaces the matched string in-place while leaving everything else in the page or field value unchanged. - Select the scope. Choose whether to process all sites or a subset. For large tenants, process high-traffic sites first (the intranet home, HR and IT sites, project sites with active navigation) and confirm the replacements work correctly before processing the remaining long tail.
- Run on site pages first, then list columns. Site pages affect navigation and user-visible links; fixing those first reduces the visible impact of the broken URLs. List hyperlink columns affect power users and specific business processes; those can follow once page navigation is confirmed clean.
- Verify a sample of pages after the run. Open five to ten site pages at random after the replacement completes and confirm the links within them resolve to the new URLs. Also check the SharePoint search index by searching for the old subdomain string after 24 to 48 hours; if the index has re-crawled, any remaining absolute references in indexed content will surface.
For the full guide on what Replace Master can search and replace across a tenant, see how to find and fix broken SharePoint URLs. For a broader comparison of URL replacement options including PowerShell alternatives, see SharePoint URL replacement tools compared.
What Does Not Need Replacing
Knowing what to skip saves time. Several URL types that look like they might break do not actually break after a rename:
- Relative URLs. Any link stored as
/sites/marketing/...rather thanhttps://contoso.sharepoint.com/sites/marketing/...continues to resolve correctly after the rename. Relative URLs have no tenant subdomain to update. - Managed metadata term links. Terms in the SharePoint term store that reference SharePoint URLs may or may not be affected depending on how they were added. Microsoft's rename documentation covers term store behaviour separately.
- SharePoint navigation configured through the SharePoint admin center. Tenant-level navigation settings in the admin center are updated as part of the rename process. Site-level navigation configured manually may need verification.
- Azure Active Directory or Entra ID app registration redirect URIs. If any custom apps are registered with SharePoint URLs as redirect URIs, update those registrations separately in the Entra ID admin center - that falls outside Replace Master's scope.
Frequently Asked Questions
Does Microsoft automatically update embedded URLs when I rename my SharePoint tenant?
No. Microsoft updates site collection URLs and OneDrive URLs at the service level, but does not rewrite absolute URLs embedded in site page content, hyperlink column values, or navigation links. Those require a separate update step after the rename propagates.
Do relative URLs break after a tenant rename?
No. Relative URLs contain no tenant domain, so they continue to resolve correctly after the rename without any changes. Only absolute URLs that contain the old tenant subdomain need to be updated.
How long does a tenant rename take to propagate?
Microsoft states that tenant renames can take up to 24 hours to fully propagate across all SharePoint and OneDrive services. During propagation, redirects from the old URL to the new one remain active. Wait until propagation is confirmed complete before running URL replacements, to avoid replacing a URL that is still actively redirecting.