starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #5148] [Feature Request]: Standard - Set automatic version history limits for the organization #2465

New issue

Closed

opened 2026-03-02 13:52:35 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:52:35 +03:00

Owner

Originally created by @RasmusFNielsen on GitHub (Jan 2, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5148

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

Currently, SharePoint Online defaults to a hard limit of 500 versions per document library. This setting is outdated and does not align with Microsoft’s own recommendation to use automatic version history management. The hard limit creates unnecessary administrative overhead and can lead to inefficient storage usage over time. Organizations must manually adjust this setting.

Proposed Solution
Set the default configuration for new SharePoint Online sites to:
Set-SPOTenant -EnableAutoExpirationVersionTrim $true

This enables automatic version expiration for newly created sites, which intelligently manages version history based on age and relevance rather than a fixed number.

Benefits for MSPs

Reduced Operational Overhead: MSPs no longer need to manually configure version limits for every new site.
Consistency Across Tenants: Ensures best-practice settings are applied by default, reducing misconfigurations.
Improved Storage Management: Automatic trimming optimizes storage usage without sacrificing compliance or user experience.

Value or Importance

Future-Proofing: Aligns with Microsoft’s recommended approach for version management.
Cost Efficiency: Helps control storage growth, reducing potential costs for additional storage.
Better User Experience: Users retain relevant versions without arbitrary limits, improving collaboration and reducing frustration.

PowerShell Commands (Optional)

https://learn.microsoft.com/en-us/sharepoint/set-default-org-version-limits

Originally created by @RasmusFNielsen on GitHub (Jan 2, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5148 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement Currently, SharePoint Online defaults to a hard limit of 500 versions per document library. This setting is outdated and does not align with Microsoft’s own recommendation to use automatic version history management. The hard limit creates unnecessary administrative overhead and can lead to inefficient storage usage over time. Organizations must manually adjust this setting. **Proposed Solution** Set the default configuration for new SharePoint Online sites to: `Set-SPOTenant -EnableAutoExpirationVersionTrim $true` This enables automatic version expiration for newly created sites, which intelligently manages version history based on age and relevance rather than a fixed number. ### Benefits for MSPs - **Reduced Operational Overhead:** MSPs no longer need to manually configure version limits for every new site. - **Consistency Across Tenants:** Ensures best-practice settings are applied by default, reducing misconfigurations. - **Improved Storage Management:** Automatic trimming optimizes storage usage without sacrificing compliance or user experience. ### Value or Importance - **Future-Proofing:** Aligns with Microsoft’s recommended approach for version management. - **Cost Efficiency:** Helps control storage growth, reducing potential costs for additional storage. - **Better User Experience:** Users retain relevant versions without arbitrary limits, improving collaboration and reducing frustration. ### PowerShell Commands (Optional) https://learn.microsoft.com/en-us/sharepoint/set-default-org-version-limits

kerem

2026-03-02 13:52:35 +03:00

closed this issue
added the
enhancement

no-priority

no-activity

not-assigned
labels

kerem commented

2026-03-02 13:52:36 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 12, 2026):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Jan 12, 2026): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

kerem commented

2026-03-02 13:52:36 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 18, 2026):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Jan 18, 2026): This issue was closed because it has been stalled for 14 days with no activity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2465

No description provided.

Rows
Columns