When making an O365 Tenant connection using Metalogix Content Matrix, the SharePoint Administration URL must be used in order for the connection to be completed; that is:
If an incorrect URL, such as a specific site or Site Collection URL is used, then the connection will not be completed and the following connection error will display:
NOTE: If you want to connect to a specific site or site collection, use an Object Model (OM) connection.
Modern team sites in SharePoint Online are team sites integrated with Office 365 groups for improved collaboration.When a modern team site is created, SharePoint Online automatically creates the O365 group and group email address. Because of differences between modern team sites and "old-style" team sites (including the permissions required to connect to them via Content Matrix), when the tenant connection is made, the Limit Site Collection dialog will allow you to "opt out" of loading them.
Permissions Requirements for Connecting to Modern Team Sites
When connecting to an SPO modern team site, the migrating account must be a Site Collection Administrator/Group Owner.
If you attempt to make a site-level connection to a private modern team site for which you do not have sufficient permissions, one of the following messages displays, depending on the Authentication Type you chose:
·for Web Browser Authentication:
NOTE: This message also displays if you have successfully made a tenant connection using Web Browser Authentication then attempt to load a site for which you have insufficient permissions. See also "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication.
·for other Authentication Types:
NOTE: You may also receive a variation on the message, such as The remote server returned an error: (403) Forbidden.
If you made a tenant-level connection that includes modern team sitesor you have successfully connected to a public modern team siteand the migrating account does not have sufficient permissions, when you click on the node in Explorer View, the message Connected user does not have admin permissions on the site displays.
To grant site collection administrator privileges to the migrating account, right-click and choose Set Connected User as Site Collection Admin.
If, going forward, you want Content Matrix to automatically grant account site collection administrator privileges if the migrating account has insufficient permissions, from the Console ribbon Settings tab, make sure the Show Teams Access Permissions option is disabled. (The option will also become disabled if you check Do not show this message again on the Auto Grant Permission confirmation dialog).
License Agreement for Migrating Modern Team Site Owners and Members
Because Content Matrix uses the Microsoft Graph API to migrate modern team site owners and members, which allows Microsoft to collect personal data, the first time a SharePoint connection is made that includes modern team sites, a License Agreement dialog displays. You must agree to the license agreement's terms and conditions in order to migrate modern team site owners and members. If you decline, you will be able to migrate the contents of modern team sites, but not owners and members.
One-time Login for Application Creation
Content Matrix uses the Microsoft Graph API to migrate modern team site owners and members. Therefore, the first time you make a connection that includes modern team sites, you will be prompted to log into your organization's Microsoft Azure accountusing Azure Tenant Administrator credentialsto create the Metalogix Content Matrix Client application. This will allow Content Matrix to migrate site owners and members for any future connections made for that tenant.
Metalogix Content Matrix currently has limited support for the Azure Migration Pipeline.
By default Metalogix Content Matrix will try to use the Shared SPO Containers when migrating to an SharePoint Online tenant, provided that the Azure Pipeline and Azure Encryption options are both enabled. Using the Shared Azure Containers does not require any additional configuration. However, you still have the option of manually configuring Metalogix Content Matrix to use a specific set of Azure containers instead. For detailed information on additional system and configuration requirements for using the pipeline, please see the Metalogix Content Matrix Performance Optimization Guide PDF document included in the installation ZIP file.
The following is a list of objects that can be migrated using the Azure Pipeline/SPO Containers:
EXCEPTION: If the scope contains unsupported lists, the lists themselves will migrate over the CSOM connection, but the migration of alerts for these lists will fail, as CSOM connections do not support the migration of alerts.
·Discussion boards, including versioning for discussion topics and replies (as opposed to non-Azure migrations, which do not migrate discussion topic versions).
NOTE: Featured Discussion and Best Reply metadata is currently not supported.
·Managed metadata (also known as taxonomy fields) in lists and libraries
If using a SharePoint 2010 Database connection as the source, then before migrating lists and libraries containing managed metadata using Azure, all affected metadata must already be migrated to the target (using a non-database connection) and the source and target GUIDs of all affected metadata must already be mapped. For information about mapping GUIDs, see GUID Mapping.
·Surveys with single or multiple responses
In order to perform any of the supported migration actions using the Azure Pipeline, the applicable options must be checked on the Copy Options Dialog > List Content Options tab.
Migration using the Azure Pipeline currently does not support:
·SharePoint 2007 Publishing Images libraries (which migrate as Asset Libraries over CSOM unless part of an override)
§when using a Remote Object Model (MEWS) connection - greater than 450 MB
§when using a Local Object Model connection - greater than 2047 MB (2 GB)
NOTE: Metalogix Content Matrix uses the value specified for the key SupportFileSizeInMBUsingMigrationPipeline in the configuration variable file EnvironmentSettings.xml to determine the maximum file size to migrate using Azure. The value of this key is 400 by default (to accommodate the maximum file size for a MEWS connection) but may be increased to 2047 (for migrations using a Local Object Model connection). Keep in mind, however, that if the value of this variable exceeds the maximum supported size for the connection type, the migration is likely to fail.
The following is a list of actions that are currently supported by the Azure pipeline:
·Paste Site Collection
·Paste Site as Sub Site
·Paste All Site Content
·Paste List as Folder
·Paste List Content > All List Items and Folders (to an empty document library only, Full Copy mode only)
·Paste Folder Content > All List Items and Folders
·Paste Site Objects > Alerts*
·Paste List Objects > Alerts*
* If the scope contains unsupported lists, the migration of alerts for the unsupported lists will fail.