Permission Inheritance Breaks After Moving Files: OneDrive for Business Fix

When you move files within OneDrive for Business or between OneDrive and SharePoint, permission inheritance can break unexpectedly. This means files that previously inherited permissions from a parent folder may suddenly have unique permissions, causing access issues for users who should have access. The root cause is that OneDrive and SharePoint treat moved files as new items, severing the inheritance link to the source folder. This article explains why this happens and provides the exact steps to restore permission inheritance after moving files.

Why Moving Files Breaks Permission Inheritance

SharePoint and OneDrive for Business use a permission inheritance model. By default, files and subfolders inherit permissions from their parent folder. When you move a file using the Move to or Copy to command, SharePoint treats the moved file as a new item in the target location. This action automatically breaks inheritance, giving the file unique permissions that may not match the target folder’s permissions.

The same behavior occurs when you drag and drop files in OneDrive or SharePoint. The file’s permission set is not preserved; instead, it gets reset to inherit from the new parent. However, if the file had unique permissions before the move, those unique permissions are lost and replaced with the target folder’s inheritance. This inconsistency leads to access denied errors for users who previously had access.

This behavior is by design. Microsoft prioritizes security: moving a file to a new location should not carry over old permissions that might grant unintended access. But for administrators managing document libraries with complex permission structures, this creates extra work to reapply permissions after every file move.

Steps to Restore Permission Inheritance After Moving Files

Follow these steps to restore inheritance on files that have broken permission inheritance after being moved. These instructions apply to SharePoint Online and OneDrive for Business accessed through a browser.

1. Open the file or folder in a browser
   Navigate to the SharePoint site or OneDrive folder where the moved file now resides. Select the file or folder that has broken inheritance.
2. Access the Manage Access panel
   Click the three dots (ellipsis) next to the file name, then select Manage access. Alternatively, select the file and click the Manage access icon in the toolbar.
3. Review current permissions
   In the Manage access pane, look for the message “This item has unique permissions.” This confirms that inheritance is broken.
4. Open Advanced permissions settings
   Click the three dots in the Manage access pane, then select Advanced settings. This opens the Permissions page for the item.
5. Restore inheritance
   On the Permissions tab, click the ribbon button labeled Inherit Permissions. A confirmation dialog appears. Click OK to restore inheritance. The item will now inherit permissions from its parent folder.
6. Verify inheritance is restored
   Return to the Manage access pane. The message should now say “This item inherits permissions from its parent folder.”

If you need to restore inheritance on multiple files at once, use SharePoint Online Management Shell with the Set-PnPFileInheritance cmdlet. Run PowerShell as an administrator and connect to your tenant. Then use the command Set-PnPFileInheritance -Identity "https://tenant.sharepoint.com/sites/site/library/folder/file.docx" -Inherit to restore inheritance on a specific file. For bulk operations, loop through a CSV list of file URLs.

If Permission Inheritance Still Breaks After the Main Fix

Sometimes the Inherit Permissions button is grayed out, or inheritance breaks again after a subsequent move. Here are common failure patterns and their fixes.

Inherit Permissions Button Is Grayed Out

This happens when the item is checked out or has an approval status that blocks permission changes. Check in the file if it is checked out. If the file is in a library with content approval, ensure the file is in an approved state. You may need to approve the file as a site owner before you can restore inheritance.

Inheritance Breaks Again After Another Move

Every move operation breaks inheritance on the moved item. The only way to prevent this is to copy the file instead of moving it, then delete the original. A copy retains inheritance from the target folder because it is created as a new item that immediately inherits. However, copying does not preserve metadata or version history. Plan your file organization to minimize moves.

Users Still Get Access Denied After Restoring Inheritance

Restoring inheritance gives the file the same permissions as its parent folder. If users still cannot access the file, check the parent folder’s permissions. The parent may have broken inheritance as well. Navigate to the parent folder and repeat the inheritance restoration steps. Also verify that the user or group is listed in the parent folder’s permissions.

Permission Inheritance Behavior: Move vs Copy vs Upload

Action	Inheritance Status After Action	Permissions Carried Over?
Move within same library	Breaks inheritance, inherits from new parent	No
Move to different library	Breaks inheritance, inherits from target folder	No
Copy to same or different library	Inherits from target folder immediately	No
Upload new file	Inherits from upload folder immediately	N/A
Drag and drop (browser)	Same as Move	No

The key takeaway: Move and drag-and-drop break inheritance. Copy and upload preserve inheritance from the target location. If you need to keep permission inheritance intact, use Copy instead of Move, then manually delete the source file after verifying the copy works.

OneDrive for Business sync client does not provide a direct way to restore inheritance. You must use the browser interface or PowerShell to manage permission inheritance. Unlinking and re-linking OneDrive can force a permission refresh on synced files, but it does not fix broken inheritance. Use the browser steps above first.

For tenant-wide automation, consider creating a SharePoint workflow or Power Automate flow that runs daily and restores inheritance on all items in a specific library that have unique permissions. Use the REST API endpoint _api/web/lists/getbytitle('Documents')/items to query items and reset inheritance programmatically.

Now you can identify when permission inheritance breaks after moving files and restore it using the Inherit Permissions button in SharePoint. For bulk fixes, use the Set-PnPFileInheritance PowerShell cmdlet. To avoid this issue in the future, use Copy instead of Move when you want to preserve inheritance, and plan your folder structure to minimize file moves.