Export (0) Print
Expand All

SharePoint Online Domain Migration Policy


Topic Last Modified: 2014-04-02

The information in this guide describes the requirements, policies and process that govern how Microsoft and subscribers to SharePoint Online Dedicated plans validate and fulfill the prerequisites when they migrate SharePoint Online users to a new domain. Domain migration is the process of moving users from one domain to another without compromising security or losing existing user permissions.

There are various scenarios that necessitate domain migrations. Here are two examples:

  • Company acquisitions and divestitures where users with the acquired company must be migrated to the parent company’s domain.

  • A migration from another directory service to Active Directory.

These and other situations can require domain name changes or domain consolidations or separations.

When a user is migrated across domains, the domain name, user name, and Security Identifiers (SID) change, and SharePoint must be updated to avoid a mismatch in the SharePoint database. If this is not done, the Portal, Team, and My Site access control list (ACL) will not be accurate, making the site inaccessible to the user.

For detailed information about domain migration, see:

The most important component of a successful and timely domain migration is a comprehensive migration plan. Customers must create a plan to remediate the known failure modes identified for SharePoint Online domain migrations. The SharePoint Online Domain Migration Planning Template is provided for this purpose.

Using this guide and the associated planning template, your organization can identify and capture all the known facts related to a domain migration and perform the tasks required for successful completion of the migration, including submission of the required configuration requests (CRs).

In addition to planning and remediation, you must perform the following tasks, all of which are described later in this guide:

  • Submit the appropriate CRs at the appropriate points in the process.

  • Create a document library.

  • Create and upload .csv files to the appropriate document library.

  • View and verify migration results.

  • Submit a monthly migration status update.

After your organization has completed and submitted a domain migration plan, Microsoft:

  • Reviews the high-level domain migration plan and provides feedback to ensure there are no scheduling conflicts between the required activities.

  • Reviews the domain migration plan and verifies that your organization has a remediation plan for the known failure modes.

  • Deploys the Domain Migration Tool (DMT) in Microsoft test environments for complete execution of the plan as part of release verification.

The benefits of following this domain migration process include:

  • Microsoft planning experience. Microsoft has experience in evaluating how different migrations scenarios are managed and can suggest input early in the migration process.

  • Structured process. Microsoft aims to bring structure to the complex domain migration process and provides remediation to the known failure modes.

The policies and process described in this guide do not cover overall migration for your organization. The scope is limited to remediation of user profiles and permissions for domain migrations. Active Directory information captured and covered here is limited to what is required for user profile and permission remediation. For instance, no Active Directory migration remediation steps are included. Instructions apply only to domain migrations for SharePoint Online.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft