Modern authentication copy limitations

When you use modern authentication to connect to Microsoft 365, some SharePoint features and copy scenarios aren’t supported.

These limitations are due to limited access to legacy APIs that cannot be used with Modern authentication.

This article lists everything that’s currently unsupported to help you plan your migration.

The top navigation bar visible in SharePoint team sites is not migrated when using modern authentication.

Navigation links labeled "Shared with me" in a list's tab are not migrated to the destination site with Modern authentication.

Classic web part pages and Basic pages cannot be migrated when using modern authentication.

If a page cannot be created at the destination, web parts associated with that page can’t be copied.

When a copy is reverted to normal mode, the version history of your document sets is not preserved with Modern authentication.

Files larger than 250 MB cannot be copied if the copy falls back to normal mode and the destination library uses list validation with Modern authentication.

Apps from the SharePoint Marketplace can’t be installed during a copy with Modern authentication.

Specifically, the Nintex app can’t be installed at the destination with Modern authentication.

RSS feed activation will always default to enabled at the destination and can’t be changed to match the source setting if the source is disabled with Modern authentication.

You will receive a warning in your migration report if your RSS feed setting does not match the source.

Aggregated (merged) calendars can’t be migrated or updated and will result in an error in your migration report with Modern authentication.

List items aren’t migrated when the list contains columns with CSOM-reserved names, such as ComplianceInfo or Properties, with Modern authentication.

The Show user and Allow multiple responses list settings are not preserved with Modern authentication.

If item scheduling is enabled at the destination, it remains enabled after a merge migration even if it is disabled at the source with Modern authentication.

The list setting Launch forms in a dialog is always disabled at the destination with Modern authentication.

The list setting, Site Assets Library, is always set to No at the destination with Modern authentication.

The Opening documents in the browser list setting is always set to Use the server default at the destination, unless the source and destination lists have a matching different setting when the migration is launched with Modern authentication.

The Custom Send to Destination list setting cannot be modified at the destination to match the source with Modern authentication.

The RSS list settings cannot be modified at the destination to match the source. Since this cannot be detected by the app, no warnings are displayed with Modern authentication.

Classic web parts that rely on an indexed column with a primary and secondary column are created at the destination, but will not load with Modern authentication. Since this cannot be detected by the app, no warnings are displayed.

Managed metadata columns cannot be copied with Modern authentication.

List rating settings can’t be changed at the destination with Modern authentication when they don't match the source.

Classic web parts placed in the Content zone of a Wiki page or a publishing page with a page layout can be added, but remain hidden, even in edit mode, at the destination when copied with Modern authentication.

SharePoint 2010 workflows can’t be migrated with Modern authentication.

Managed metadata fields will not function correctly in Document Information Panels at the destination when copied with Modern authentication.

Document set settings and Document Information Panel settings for a list content type are also not preserved with Modern authentication.

Fields of a list that does not have the Manage content type feature may not be copied in the correct order to the destination when using Modern authentication.

Some files that depend on a template, such as View, get detached from the template at the destination and cannot be reverted to the template when copied in Normal mode with Modern authentication.

If a page is detached from a layout during copy in Normal mode with Modern authentication, it may cause an error.

Item version history that includes minor and major versions might not be preserved when copied in normal mode with Modern authentication.

Classic audience targeting is not preserved with Modern authentication.

Nintex Forms and Workflows can’t be copied with modern authentication.

BDC fields and lists are not supported with Modern authentication, and their values are not copied.