Can SharePoint storage be allocated between sites in Microsoft 365 Business Premium?
Yes. SharePoint storage in Microsoft 365 Business Premium is held in a shared tenant pool, and a SharePoint administrator can manage individual site storage limits so available capacity is directed towards sites that need it, provided the tenant’s total storage allowance is not exceeded.
SharePoint site allocation is managed through storage limits and usage controls, rather than by moving a fixed block of storage from one site to another. An administrator can decide how much each site is allowed to use, while the files, permissions and site content remain in their existing locations.
Two storage-management methods are available:
- Automatic management: SharePoint adjusts site storage limits according to the tenant’s available capacity and site usage. This reduces the need to maintain separate quotas manually.
- Manual management: An administrator sets a storage limit for individual sites. This is useful when certain sites, such as document repositories for projects or departments, need tighter controls or a defined maximum.
A manually configured limit acts as a ceiling, not as a reservation. Setting a high limit for one site does not remove that amount from the other sites immediately, because capacity is consumed as content is uploaded. However, actual usage across the tenant still has to remain within the available SharePoint allowance. A quota therefore helps control individual sites, but it does not create additional storage.
How an administrator changes a site limit
In the SharePoint admin centre, an administrator can open Active sites, select the relevant site and edit its storage setting. Depending on the tenant configuration, the administrator can leave the site under automatic management or enter a manual limit. The exact labels can change as the Microsoft 365 administration interface develops, but the process is based on selecting the site and changing its storage configuration.
Changing a limit does not move files between sites and does not alter site membership or permissions. If a site is given more headroom, users can continue adding content until the new limit or the tenant’s overall capacity becomes the constraint. If the limit is reduced below the site’s current usage, the site may be considered over its quota and could be prevented from accepting further content until space is freed or the limit is increased.
What should be considered before allocating limits?
- Review current usage rather than allocating identical limits to every site.
- Allow for expected growth in active document libraries, project workspaces and shared departmental files.
- Check whether file versions, recycle-bin content and duplicated documents are contributing to consumption.
- Set ownership for sites so that an administrator knows who should review warnings and remove obsolete content.
- Keep high-growth sites under closer review, particularly where large media files, design files or extensive document histories are stored.
Storage allocation also needs to be distinguished from access control. Giving a site a larger quota does not give its users access to another site, and reducing a quota does not remove files or change sharing permissions. Those are separate administration decisions.
If the tenant is approaching its overall allowance, changing individual site limits only manages where capacity is used; it does not solve the underlying shortage. The practical options are to remove or relocate content in line with retention requirements, reduce unnecessary versioned data, improve document-management rules or obtain additional SharePoint capacity where appropriate. Before deleting anything, the organisation should confirm its legal, regulatory and internal retention obligations.
SharePoint storage limits apply to individual sites, even when those sites are connected through Microsoft 365 features. A site’s relationship with other sites does not create a separate shared sub-pool or combine their quotas.
- A communication site retains its own storage limit.
- A team site connected to a Microsoft Team is managed as its own SharePoint site.
- Sites associated with a hub site remain separate for storage purposes; hub navigation and search do not merge their capacity.
- Separate channel sites, where used, should be reviewed independently because their content may not appear in the main team site’s storage usage.
This distinction matters when planning limits. An organisation may group sites by department, project or hub for navigation, but storage decisions still need to be based on each site’s actual content and expected growth. A site structure can therefore support collaboration without changing how SharePoint capacity is assigned or monitored.