logo
search
Version History Issues

How to Manage OneDrive for Business Versioning by Folder

Ayan MasoodAyan Masood Oct 10, 2026 869 views

Question details

The user wants to find a way to manage or turn off versioning for an individual folder in OneDrive for Business.

How to Manage OneDrive for Business Versioning by Folder
Product
OneDrive for Business
Device & OS
not provided
Scenario
Attempting to control file version history and storage settings for specific folders rather than applying a global rule to the entire document library.
Observed behavior
OneDrive for Business does not natively support disabling or configuring versioning at the folder level; it enforces versioning configuration strictly at the document-library level.
Before you start

Ensure you have the necessary administrator or owner permissions for your SharePoint environment and OneDrive account, as the workarounds require creating libraries or running Power Automate scripts.

Solution 1Recommended

Create a Separate Document Library

Because versioning is controlled at the library level, the most reliable workaround is to isolate the target folder's contents into a new SharePoint document library with custom versioning settings.

This method involves migrating the files you wish to exclude from standard versioning into a dedicated SharePoint library. Once isolated, you can use PnP PowerShell to modify versioning rules for that specific library without affecting your main OneDrive files.

1
Create a new library

Navigate to your SharePoint site, click on 'New' in the top menu, and select 'Document library' to create a dedicated space for your files.

2
Move the folder contents

In your OneDrive for Business, select the folder you want to manage, choose the 'Move to' option, and transfer the files into the newly created document library.

3
Configure versioning settings

Use PnP PowerShell commands to connect to your SharePoint site and disable or modify the versioning settings exclusively for this new document library.

Create a Separate Document Library
PowerShell Requirement: Disabling versioning completely on modern SharePoint libraries often requires administrative scripting via PnP PowerShell, as the web interface natively enforces minimum version limits.
Free Microsoft Office alternative

Try WPS Office for a Streamlined Document Experience

Dealing with complex administrative restrictions in OneDrive and SharePoint can be frustrating for individual users. If you are looking for an intuitive, lightweight, and user-friendly office suite, WPS Office provides excellent document creation and version tracking capabilities without the steep learning curve.

  1. 1. Download and Install: Download WPS Office from the official website and follow the installation prompts to set it up on your device.
  2. 2. Open your Document: Launch WPS Office and open your existing Microsoft Office files or create a new document seamlessly.
  3. 3. Access Version History: Navigate to Menu > File > Backup and Version to easily view, manage, and restore earlier versions of your work.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Built-in WPS Cloud allows straightforward version history management and file syncing.Free and lightweight suite with a familiar, tabbed user interface.Easily view, restore, or manage previous document versions directly from the editor.
microsoft office alternative - wps office

Frequently Asked Questions

Can I disable versioning for a single folder in OneDrive for Business?

No, OneDrive for Business and SharePoint configure versioning exclusively at the document library level. Individual folders cannot have custom versioning rules natively.

Will deleting older file versions free up my OneDrive storage?

Yes, older versions of large files consume your overall storage quota. Deleting unnecessary versions manually or via automated scripts will help free up storage space.

Does SharePoint allow completely disabling version history?

By default, modern SharePoint and OneDrive libraries require versioning to be enabled (usually enforcing a minimum of 100 versions) to prevent data loss. Complete disabling usually requires specialized PnP PowerShell commands by an administrator.