{"id":108765,"date":"2021-03-18T18:34:14","date_gmt":"2021-03-18T18:34:14","guid":{"rendered":"https:\/\/evertise.net\/?p=12403"},"modified":"2021-03-18T18:34:14","modified_gmt":"2021-03-18T18:34:14","slug":"an-overview-of-office-365-tenant-to-tenant-migrations","status":"publish","type":"post","link":"http:\/\/ipsnews.net\/business\/2021\/03\/18\/an-overview-of-office-365-tenant-to-tenant-migrations\/","title":{"rendered":"An Overview of Office 365 Tenant to Tenant Migrations"},"content":{"rendered":"

<\/span><\/p>\n

As more and more companies undertake Office 365 for their services, there is an expansion in demand for\u00a0<\/span>Office 365 Tenant to Tenant Migration<\/span><\/a>. In some situations, the basic Office 365 tenant is in a cloud-hosted platform on a Microsoft system. Yet most Office 365 tenants are on the same shared Microsoft platform, the data is entirely separated for each tenant. While this separation is existing, there still is the capacity to set up several levels of the federation and share between two different Office 365 tenants. Office 365 Tenant to Tenant Migration is very similar to when you\u00a0<\/span>Migrate SharePoint 2010 to SharePoint Online<\/span><\/a><\/p>\n

The important issue here is there are limitations on collaboration platforms among tenants; consider two people from separate tenants attempting to run the same document in SharePoint Online, <\/span>Microsoft Teams<\/span><\/a> or OneDrive for Business. Similarly, a company has no other option to try and maintain users, licenses, security policies, etc. in a couple of tenants as well as typically two different AD Forests.<\/span><\/p>\n

How to Fix this?<\/b><\/p>\n

Typically, a business can choose one of four things:<\/span><\/p>\n

    \n
  1. Merge Office 365 Tenants and AD Forests<\/b><\/li>\n<\/ol>\n