Azure Tenant Rename Impact on SharePoint Synchronization

Question

Azure Tenant Rename Impact on SharePoint Synchronization

Bindu M S 40

our goal is to change our tenant name in Azure. In principle, this would be possible with global admin rights, but we wanted to ask first what risks or consequences this might entail and what we should keep in mind before renaming it. Additionally, we have SharePoint synchronizations. Will the local Explorer path change for existing synchronizations, or only for new ones, since the tenant name is stored in the path?

0 comments

Answer accepted by question author

Liora D 15,800 Microsoft External Staff Moderator

Dear @Bindu M S,

I hope you’re having a good day.

Thank you for your question, this is a very important scenario to evaluate carefully before making any changes.

I understand that you are planning to rename your Azure/Microsoft 365 tenant and want to understand the potential impact, especially on SharePoint synchronization and local Explorer paths.

1. Impact on SharePoint synchronization: Yes, the local Explorer path will change after a tenant rename, but not automatically for existing syncs.

Existing synchronizations: After the tenant is renamed, current OneDrive/SharePoint sync connections will typically break or become out of sync because they still point to the old tenant URL. In practice, users usually need to stop syncing and set up sync again, and the new path will be created based on the new tenant name.
New synchronizations: Any new sync established after the rename will use the new tenant name automatically in the local path. (Before: C:\Users\User\oldname – Documents > After: C:\Users\User\newname – Documents)

2. Other important impacts to consider

Renaming a tenant is not just a visual change, it affects multiple services across Microsoft 365:

SharePoint & OneDrive URLs change (oldname.sharepoint.com > newname.sharepoint.com)

a, Existing links and integrations

Microsoft provides redirection for old URLs, but not all scenarios are guaranteed to work seamlessly, especially for:

Power Automate flows
Power Apps
Third-party integrations
Scripts or systems using hardcoded URLs

b, User disruption

Users may experience temporary issues such as:

Sync errors
Need to reauthenticate or reconnect
Reconfiguration of OneDrive/Teams file access

c, Apps and connected services: Any app relying on the old tenant domain should be reviewed and validated after the change

3. To minimize impact, it’s strongly recommended to:

Inform users in advance about expected changes (especially sync disruption)
Prepare guidance for re-syncing OneDrive/SharePoint
Review critical integrations and flows
Test in a controlled scenario if possible

You can review Microsoft’s official guidance here: Change your SharePoint domain name - SharePoint in Microsoft 365 | Microsoft Learn

(This article provides guidance on changing the SharePoint domain name for organizations using Microsoft 365, particularly during rebranding or mergers. The article details the process using PowerShell and outlines the implications of such a change on SharePoint and OneDrive URLs)

I hope this gives you a clear picture before proceeding.

If you have any updates or would like help validating specific scenarios in your environment, please feel free to reach out, I’ll be happy to assist further.

Warm regards,

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-23T14:41:06.3833333+00:00

Hi Bindu M S,

I just wanted to follow up to see how things are going with the information I shared above. I truly hope it was helpful and brought you closer to resolving the issue.

If you’ve had a chance to review it and have any updates, questions, or if you ran into any difficulties along the way, please don’t hesitate to let me know. I’m more than happy to assist further if needed.

It would be great to hear back from you!

Warm regards,

Liora.
Bindu M S 40 Reputation points

2026-05-26T07:44:49.1+00:00

However, we have a follow-up question:

If we simply change the tenant name in the Azure Portal under “Microsoft Entra ID” -> “Overview” -> ‘Properties’ -> “Name,” will that have as many implications?

Specifically regarding the “URL”—will this name change also alter the current URL to SharePoint (currently: “bmkgroupde.onmicrosoft.com”)?

Or does changing this domain require modifying another menu item, and could this change be made later independently?

If the two changes can be made independently of each other and we only want to change the name for now, would the synchronizations then also need to be stopped and re-established?

Because the URL remains the same; only the display in OneDrive would actually still be the old one
Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-26T15:14:10.19+00:00

Hi Bindu,

Thank you for your follow-up, this is a very good question, and your thinking here is absolutely on the right track.

If you change the Name under Microsoft Entra ID > Properties, this is only a display (cosmetic) change. It does not modify the underlying tenant domain or service URLs.

So, to answer your questions clearly: Changing this Name will not affect your SharePoint or OneDrive URLs.

Your current domain such as bmkgroupde.onmicrosoft.com and the related SharePoint URL will remain exactly the same.

This change is independent from a tenant/domain rename (such as changing the SharePoint domain name). Those are separate operations and can be done later if needed.

Because the URL and tenant domain remain unchanged, your existing SharePoint/OneDrive synchronizations will continue to work normally. There is no need to stop or re-establish sync connections in this scenario.

You are also correct in your assumption: users may still see the old name reflected in some local OneDrive/Explorer paths, since those were created earlier, but this is only a display detail and does not affect functionality.

If your goal is to update the tenant name for visibility or branding purposes only, you can safely proceed with this change without impacting SharePoint URLs or synchronization.

If you later decide to change the SharePoint domain itself, that would be a separate operation and should be planned carefully, as it has a broader impact (as discussed earlier).
Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-27T10:53:51.82+00:00

Hi Bindu,

Just wanted to check in and see if everything is clear now regarding your scenario.

If you still have any questions or need help as you proceed with the change, please feel free to reach out, I’d be more than happy to assist further.

Thank you again, and I wish you all the best with your tenant update!
Bindu M S 40 Reputation points

2026-05-27T11:58:06.6366667+00:00

Thank you so much i have no questions
Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-27T14:04:51.89+00:00

Hi Bindu,

Thank you very much for your confirmation, I’m glad everything is clear now

1 additional answer

Your answer

Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-23T14:41:06.3833333+00:00

Hi Bindu M S,

I just wanted to follow up to see how things are going with the information I shared above. I truly hope it was helpful and brought you closer to resolving the issue.

If you’ve had a chance to review it and have any updates, questions, or if you ran into any difficulties along the way, please don’t hesitate to let me know. I’m more than happy to assist further if needed.

It would be great to hear back from you!

Warm regards,

Liora.
Bindu M S 40 Reputation points

2026-05-26T07:44:49.1+00:00

However, we have a follow-up question:

If we simply change the tenant name in the Azure Portal under “Microsoft Entra ID” -> “Overview” -> ‘Properties’ -> “Name,” will that have as many implications?

Specifically regarding the “URL”—will this name change also alter the current URL to SharePoint (currently: “bmkgroupde.onmicrosoft.com”)?

Or does changing this domain require modifying another menu item, and could this change be made later independently?

If the two changes can be made independently of each other and we only want to change the name for now, would the synchronizations then also need to be stopped and re-established?

Because the URL remains the same; only the display in OneDrive would actually still be the old one
Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-26T15:14:10.19+00:00

Hi Bindu,

Thank you for your follow-up, this is a very good question, and your thinking here is absolutely on the right track.

If you change the Name under Microsoft Entra ID > Properties, this is only a display (cosmetic) change. It does not modify the underlying tenant domain or service URLs.

So, to answer your questions clearly: Changing this Name will not affect your SharePoint or OneDrive URLs.

Your current domain such as bmkgroupde.onmicrosoft.com and the related SharePoint URL will remain exactly the same.

This change is independent from a tenant/domain rename (such as changing the SharePoint domain name). Those are separate operations and can be done later if needed.

Because the URL and tenant domain remain unchanged, your existing SharePoint/OneDrive synchronizations will continue to work normally. There is no need to stop or re-establish sync connections in this scenario.

You are also correct in your assumption: users may still see the old name reflected in some local OneDrive/Explorer paths, since those were created earlier, but this is only a display detail and does not affect functionality.

If your goal is to update the tenant name for visibility or branding purposes only, you can safely proceed with this change without impacting SharePoint URLs or synchronization.

If you later decide to change the SharePoint domain itself, that would be a separate operation and should be planned carefully, as it has a broader impact (as discussed earlier).
Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-27T10:53:51.82+00:00

Hi Bindu,

Just wanted to check in and see if everything is clear now regarding your scenario.

If you still have any questions or need help as you proceed with the change, please feel free to reach out, I’d be more than happy to assist further.

Thank you again, and I wish you all the best with your tenant update!
Bindu M S 40 Reputation points

2026-05-27T11:58:06.6366667+00:00

Thank you so much i have no questions
Liora D 15,800 Reputation points Microsoft External Staff Moderator

2026-05-27T14:04:51.89+00:00

Hi Bindu,

Thank you very much for your confirmation, I’m glad everything is clear now

Answer 1

Changing the tenant (SharePoint) domain name mainly affects SharePoint and OneDrive URLs and has several important limitations and side effects to consider.

Key impacts and risks of a SharePoint domain (tenant) rename

Scope of the change

Only SharePoint and OneDrive URLs are renamed, for example from contoso.sharepoint.com to fabrikam.sharepoint.com.
Exchange Online and email addresses are not affected.

Availability during the rename

When the rename operation begins, all sites in the tenant are queued for individual renames.
While a given site is being renamed, it is temporarily inaccessible on the old domain. Once renamed to the new domain, it becomes accessible again.
For tenants with more than 10,000 total sites (SharePoint, OneDrive, Teams, etc.), Advanced Tenant Rename must be used.

Redirect behavior

After the rename, a redirect is created at the previous SharePoint domain. This redirect expires 1 year after the rename.

Eligibility and blocking conditions The rename cannot proceed if any of the following apply:

Tenant uses Microsoft 365 Multi-Geo (current or past).
Tenant uses special/government clouds (GCC, GCC High, DoD, etc.).
Tenant still has a historical German cloud .de domain.
Tenant uses vanity SharePoint domains (for example teams.contoso.com instead of contoso.sharepoint.com).
Tenant still has old SharePoint public sites or BPOS sites.
Tenant still has alternate URLs configured.
There are locked sites/OneDrives (LockState = NoAccess) that need to be unlocked first.

Operational limitations during the rename Some operations do not take effect while the rename is in progress:

Purchase/update of licenses.
Creation/update of admin roles.
Purchase/update of storage.
Root site replacement (via admin center or Invoke-SPOSiteSwap) is blocked between scheduling and completion of the rename.

Feature-specific limitations Examples of items that may require manual fixes after the rename:

Hub site menu items with absolute URLs: URLs are not automatically changed; they must be edited.
Third-party apps and backup solutions: absolute URLs embedded in those apps are not updated; coordinate with vendors.
Isolated web parts and full-page apps: isolated components are not updated and stop working until solutions are republished in the tenant app catalog.
Teams wikis and personal wikis: embedded image URLs and personal wikis may require manual workarounds.
Point-in-time restoration: restoring a site to a time before the domain change is not possible.

Impact on OneDrive / SharePoint sync and local Explorer paths

OneDrive sync behavior

During the rename, OneDrive sync can fail for a user if their OneDrive site is being renamed at the time of a resync.
It is recommended that users stop syncing during the rename if possible.
If sync issues occur afterward, users should:
- Sign out and sign back in to OneDrive, and if needed
- Go to OneDrive > Settings > Account, select “Unlink this PC”, then re-link. This does not delete OneDrive data.

Local Explorer path and folder names

Only the domain name portion in URLs is changed. The relative path based on the user’s UPN is not changed.
The organization name displayed in Office apps (for example C:\Users\Sophia\OneDrive – Contoso) is not automatically changed by the domain rename.
- Users can disconnect and reconnect their account in the Office app if they want to update the displayed organization name.

This means for existing OneDrive/SharePoint synchronizations:

The underlying SharePoint/OneDrive URL that the sync client uses will be updated to the new domain.
The local folder path in Explorer (e.g., OneDrive – Contoso) does not automatically rename just because the domain changed; it is tied to the configured account name/organization, not only the domain.
New synchronizations created after the rename will use the new domain in their configuration; the local folder name may still show the old organization name unless the account is reconnected.

Client version requirements

OneDrive sync app must be at least version 17.3.6943.0625 and able to reach oneclient.sfx.ms and g.live.com for updates.
Recent versions of OneNote and SharePoint mobile apps are required to handle the rename smoothly.

Planning recommendations

Verify that none of the blocking conditions (Multi-Geo, government cloud, .de domain, vanity domain, BPOS/public sites, alternate URLs, locked sites) apply.
Communicate downtime expectations and sync guidance to users (pause sync where possible; plan for sign-out/sign-in or unlink/relink afterward).
Inventory and plan remediation for:
- Hard-coded SharePoint/OneDrive URLs in applications, scripts, backups, and documentation.
- Hub site menus, Teams wikis, isolated web parts, and third-party integrations.
If there are more than 10,000 sites or a need to prioritize critical sites, plan to use Advanced Tenant Rename and, if licensed, prioritize up to 4,000 key sites for early execution.

References:

Share via

Azure Tenant Rename Impact on SharePoint Synchronization

1 additional answer

Your answer