Summary / Problem

When SharePoint document management is enabled for a Dataverse entity, the default document location is permanently locked to the location created by the initial setup wizard. Administrators have no supported way to change this default for newly created records, without using additional 3rd party software - which likely impacts the entire SharePoint site, rather than just the impacted document library/entity.

Business Impact

Many organisations use third‑party solutions to replicate Dataverse security permissions to SharePoint, as this is not supported out of the box. Over time, this creates a large number of uniquely secured folders in a single document library.

This can cause the SharePoint unique permissions threshold to be exceeded, leading to performance and privacy issues. The recommended mitigation—changing the default document location on an entity to a new SharePoint location—is not possible today due to the locked default document location.

Proposed Enhancement

Provide a supported capability to change an entity’s default SharePoint document location.

This would:

• Allow documents for new records to be stored in the new document location/library, without breaking the relative links of existing records to the 'old' document location.
• Allow permission replicator tool to continue to operate as the unique permissions on the new location is reset to zero.
• Allow for changing business requirements and architecture over time.