Note This article applies only to those SharePoint Online sites that have a URL that contains .microsoftonline.com. These are sites that were created before Office 365 and that were migrated to Office 365.
We support self-rename and we encourage you to use the self-rename option so that you can control exactly when this change happens. If you decide not to self-rename each site, we will rename them for you, beginning January 1, 2017.
How will the rename occur?We now support self-rename. We encourage you to use the self-rename option so that you can control exactly when this change happens. For more information about how to perform a self-rename, see the information in the following section. Beginning January 1, 2017, we're going to be renaming any SharePoint Online site collection URLs of *.microsoftonline.com, to *.SharePoint.com that have not used the self-rename option.
Self-renameTo rename the BPOS site yourself, follow these steps:
- Download and install the latest version of the SharePoint Online Management Shell. For more information, see the following Microsoft website:
- In the SharePoint Online Management Shell, use the following commands to rename the site. Note the following when you run these commands:
The command should run quickly but can take a bit longer for large sites. In that case, the site’s state should be ‘Renaming’ while the migration is in progress.
- Replace <yourdomain> with the domain that you use for your organization.
- The first URL should be the URL for the SharePoint admin center.
- The second URL should be the URL for the existing BPOS site that you want to rename.
- The third URL is the target URL. It must start with the domain name that you use for your organization in Office 365 followed by a hyphen (-). You can customize the “portal1” string, but it should be under 10 characters long. We recommend "portalN", where N matches the number in the original BPOS URL.
$adminURL = 'https://<yourdomain>-admin.sharepoint.com'
$bposURL = 'https://<yourdomain>-1.sharepoint.microsoftonline.com'
$targetURL = 'https://<yourdomain>-portal1.sharepoint.com'
Connect-SPOService $adminURL # enter credentials when you're prompted
$site = Get-SPOSite $bposURL
Set-SPOSite $site -newUrl $targetURL
For more information about the Set-SPOSite cmdlet, see the following Microsoft website:
Benefits of the renameRenaming a site will address the issues that are covered in the following Microsoft website:
Common troubleshooting scenarios
|Existing bookmarks to the old-format URLs no longer work correctly.||Re-create your bookmarks to use the new-URL format. The old format URL site will not redirect to the new URL site. |
For advanced users or organizations, consider using a Group Policy to auto-create shortcuts for the new URLs. For more information, go to the following Microsoft website:
|Hyperlinks to old-format URLs that are located in Office documents and on existing SharePoint sites no longer work correctly.|
You receive the following error messages:
The webpage cannot be foundor
HTTP/1.1 200 OK Server: Microsoft-IIS/8.5
|Re-create your hyperlinks in Office documents and on SharePoint sites.|
|OneDrive for Business synchronization to sites that use the old-format URL with the sync application no longer work.||Stop syncing, and then resynchronize your content from the sites that use the new-format URL. For more information about how to do this, go to the following Microsoft websites: |
|Search returns results from sites that use the old URL.||Allow several days for indexing to catch up.|
|Navigation nodes in the Term Store may have to be adjusted.||If you've set up managed navigation by using term sets in the Term Store, the URLs that are used for navigation may have to be adjusted if you specified them as absolute URLs.|
|URLs in promoted results are broken.||If you've set up query rules with promoted results pointing to the URLs that are being changed, you may have to adjust them after the rename operation. |
For more information about this functionality, go to the following Microsoft website:
|Externally hosted apps must be reinstalled on the site.||Because they have references to the old URL, the only option is to reinstall the app.|
|For Project Online or BI sites, if you have custom Excel reports that run against SharePoint lists or Project Online data, the connection string no longer works.||Open the affected reports, and then correct the URL for each data connection that references the old URL. Out-of-box data connections will be fixed by the rename operation.|
|The *.microsoftonline.com URL may no longer be needed for any on-premises firewall configurations.||For more information, go to the following Microsoft website:|
|Any on-premises Active Directory Group Policy Objects applied to local computers that reference the old format URLs may become out of date. For example, the browser home page, browser security zone configurations, and so on.||Update your Active Directory Group Policy Objects where the old URL is referenced.|
|Any mapped network drives that reference the old format URLs will become out of date.||Update any outdated URLs by using the steps in following Microsoft Knowledge Base article:|
2616712 How to configure and to troubleshoot mapped network drives that connect to SharePoint Online sites in Office 365
|Send To connections for records management that reference the old URL format will become out of date.||Update your Send To connections by using the information at the following Microsoft website:|
What to expect before, during, and after migrationDuring the migration process, you will experience a read-only window on the affected sites that lasts only a few minutes.
Article ID: 3053838 - Last Review: 21 Dec 2016 - Revision: 1