Administration

SharePoint Site Collection Administration: Complete Guide

Master SharePoint site collection administration. Covers site creation, quota management, feature activation, permissions, PowerShell management, and health monitoring.

SharePoint Support TeamFebruary 5, 202619 min read
SharePoint Site Collection Administration: Complete Guide - Administration guide by SharePoint Support
SharePoint Site Collection Administration: Complete Guide - Expert Administration guidance from SharePoint Support

SharePoint Site Collection Administration: The Complete Guide

A site collection is the fundamental administrative unit in SharePoint Online. Every SharePoint site is part of a site collection, and understanding how site collections work is foundational to effective SharePoint administration. In modern SharePoint Online, the terms site and site collection are largely interchangeable for most operations, though administrators need to understand the underlying architecture.

SharePoint architecture diagram showing hub sites, team sites, and content structure
Enterprise SharePoint architecture with hub sites and connected team sites

This guide covers site collection creation, management, permissions, quotas, features, monitoring, and decommissioning from an administrator's perspective.

---

Site Collection Architecture

What Is a Site Collection?

A site collection is a group of SharePoint sites that share common features, including a top-level site and any number of sub-sites beneath it. In modern SharePoint Online, each site creation through the admin center or Teams creates a new site collection automatically. The site collection boundary defines the scope for permissions inheritance, content types, site columns, navigation, and storage quotas.

Modern vs Classic Site Collections

Modern SharePoint has two primary site collection types. Communication sites are designed for broadcasting information to a broad audience. They feature modern page layouts, news capabilities, and are typically used for intranets, department portals, and project showcases. Team sites are designed for collaboration within a group. They are connected to Microsoft 365 Groups and optionally to Microsoft Teams. They feature shared document libraries, lists, and a collaborative workspace.

Classic site collection templates (Team Site Classic, Publishing Portal, Enterprise Wiki) are deprecated. All new site collections should use modern templates.

---

Creating Site Collections

Via SharePoint Admin Center

  • Open the SharePoint Admin Center at admin.microsoft.com
  • Navigate to Sites then Active sites
  • Click Create
  • Choose Team site or Communication site
  • Configure the site name, URL, primary administrator, language, and time zone
  • Set storage quota and external sharing settings
  • Click Finish

Via PowerShell

```powershell

# Create a modern communication site

New-SPOSite -Url "https://contoso.sharepoint.com/sites/CompanyNews" -Title "Company News" -Owner [email protected] -Template "SITEPAGEPUBLISHING#0" -StorageQuota 10240 -TimeZoneId 13

# Create a team site connected to Microsoft 365 Group

New-PnPSite -Type TeamSite -Title "Project Alpha" -Alias "projectalpha" -Description "Project Alpha collaboration site"

# Create a communication site

New-PnPSite -Type CommunicationSite -Title "HR Portal" -Url "https://contoso.sharepoint.com/sites/HRPortal" -SiteDesign Topic

```

Naming Conventions

Establish a consistent naming convention before creating sites. Recommended patterns include department sites using the format Department-Function (HR-Benefits, IT-HelpDesk), project sites using Project-Name (Project-Alpha, Project-Merger2026), and event sites using Event-Year (Conference-2026, Retreat-2026).

Enforce naming policies through Microsoft 365 Group naming policies that apply prefixes, suffixes, or blocked words automatically.

---

Managing Site Collection Permissions

Site Collection Administrators

Site collection administrators have full control over the site collection and all content within it. They can access all sites, libraries, and items regardless of individual permissions. Assign at least two site collection administrators to every site to prevent orphaned sites when an administrator leaves the organization.

```powershell

# Add a site collection administrator

Set-SPOUser -Site https://contoso.sharepoint.com/sites/HR -LoginName [email protected] -IsSiteCollectionAdmin $true

# List all site collection administrators

Get-SPOUser -Site https://contoso.sharepoint.com/sites/HR | Where-Object { $_.IsSiteCollectionAdmin -eq $true }

```

Permission Levels

SharePoint provides default permission levels that map to common roles. Full Control grants complete access to all site content and settings. Design allows viewing, adding, updating, deleting, approving, and customizing pages. Edit allows adding, editing, and deleting list items and documents. Contribute allows adding, editing, and deleting items. Read allows viewing pages and items. View Only allows viewing pages, items, and documents but the user cannot download documents.

Permission Inheritance

By default, sub-sites, libraries, and items inherit permissions from their parent. Break inheritance only when necessary, as broken inheritance creates management overhead and potential security gaps. Every instance of broken inheritance must be documented and reviewed periodically.

---

Storage Quota Management

Setting Quotas

Every site collection should have an explicit storage quota rather than relying on the 25 TB default. Set quotas based on the expected content volume and growth rate for each site.

```powershell

# Set storage quota (in MB) and warning level

Set-SPOSite -Identity https://contoso.sharepoint.com/sites/Marketing -StorageQuota 10240 -StorageQuotaWarningLevel 8192

```

Monitoring Usage

Check storage consumption regularly using the Admin Center dashboard or PowerShell reporting. Identify sites approaching their quota and take action before users are blocked from uploading content.

Automatic vs Manual Quota Management

SharePoint Online offers two quota management modes. Automatic mode lets SharePoint manage quotas dynamically from the tenant pool. Manual mode lets administrators set specific quotas per site. We recommend manual mode for enterprises because it provides predictable capacity planning and prevents any single site from consuming excessive storage.

---

Feature Management

Site Collection Features

Site collection features enable specific functionality. Manage features through Site Settings or PowerShell.

```powershell

# List all features on a site

Get-PnPFeature -Scope Site

# Enable a feature

Enable-PnPFeature -Identity "feature-guid-here" -Scope Site

# Disable a feature

Disable-PnPFeature -Identity "feature-guid-here" -Scope Site

```

Common features to manage include Content Type Syndication Hub for publishing content types across the tenant, SharePoint Server Publishing for classic publishing features, and Site Policy for lifecycle management.

---

Site Collection Health Monitoring

Regular Health Checks

Perform monthly health checks on all active site collections. Check storage consumption against quota, review site collection administrators for accuracy, verify external sharing settings, audit broken permission inheritance, review custom scripts and solutions, and check for stale content older than 24 months.

Automated Monitoring

Create Power Automate flows that run weekly health checks and report issues to a SharePoint list or Teams channel.

```powershell

# Health check script - run monthly

$sites = Get-SPOSite -Limit All

foreach ($site in $sites) {

$percentUsed = if ($site.StorageQuota -gt 0) { [math]::Round(($site.StorageUsageCurrent / $site.StorageQuota) * 100, 1) } else { 0 }

$admins = (Get-SPOUser -Site $site.Url | Where-Object { $_.IsSiteCollectionAdmin }).Count

if ($percentUsed -gt 80 -or $admins -lt 2) {

Write-Warning "ATTENTION: $($site.Url) - Storage: $percentUsed% - Admins: $admins"

}

}

```

---

Site Collection Lifecycle Management

Site Policies

Configure site lifecycle policies to manage inactive sites. Microsoft 365 inactive site policies can detect sites with no activity for a specified period and notify site owners to confirm the site is still needed. Sites that are not confirmed can be automatically deleted.

Archiving Sites

For sites that must be retained but are no longer active, consider locking the site to read-only mode using Set-SPOSite with the LockState parameter, moving the site to Microsoft 365 Archive for cold storage, or reducing the storage quota to free pool capacity.

```powershell

# Lock a site to read-only

Set-SPOSite -Identity https://contoso.sharepoint.com/sites/OldProject -LockState ReadOnly

# Fully lock (no access)

Set-SPOSite -Identity https://contoso.sharepoint.com/sites/OldProject -LockState NoAccess

```

Deleting Site Collections

Deleted site collections go to the site collection recycle bin for 93 days. During this period, they can be restored with all content, permissions, and settings intact. After 93 days, the deletion is permanent.

```powershell

# Delete a site collection

Remove-SPOSite -Identity https://contoso.sharepoint.com/sites/OldProject -Confirm:$false

# Restore from recycle bin

Restore-SPODeletedSite -Identity https://contoso.sharepoint.com/sites/OldProject

```

---

PowerShell Administration Toolkit

Essential Commands

Every SharePoint administrator should have these PowerShell commands in their toolkit.

```powershell

# Connect to SharePoint Online

Connect-SPOService -Url https://contoso-admin.sharepoint.com

# Get all site collections with key properties

Get-SPOSite -Limit All -Detailed | Select-Object Url, Title, StorageUsageCurrent, StorageQuota, LastContentModifiedDate, SharingCapability | Export-Csv "SiteInventory.csv"

# Bulk update sharing settings

Get-SPOSite -Limit All | Where-Object { $_.SharingCapability -eq "ExternalUserAndGuestSharing" } | Set-SPOSite -SharingCapability ExistingExternalUserSharingOnly

```

---

Frequently Asked Questions

What is the difference between a site and a site collection in modern SharePoint?

In practical terms, every modern SharePoint site is its own site collection. The distinction mattered more in classic SharePoint where sub-sites were common. In modern SharePoint, think of sites and site collections as the same thing for most administrative purposes.

How many site collections can a tenant have?

There is no hard limit on the number of site collections. Microsoft supports tenants with hundreds of thousands of site collections. Performance and manageability are the practical constraints.

Can I move a site collection to a different URL?

Yes, using the site swap and site rename features in SharePoint Online. Use Start-SPOSiteRename in PowerShell to change a site URL.

---

For help managing your SharePoint site collections at scale, [contact our administration team](/contact) for a governance assessment. We build management frameworks for organizations with hundreds of sites that keep SharePoint organized and secure. Explore our [SharePoint administration services](/services) to learn more.

Share this article:

Written by Errin O'Connor

Founder, CEO & Chief AI Architect | Microsoft Press Bestselling Author | 25+ Years Microsoft Ecosystem

Errin O'Connor is a Microsoft Press bestselling author of 4 books covering SharePoint, Power BI, Azure, and large-scale migrations. He leads our SharePoint consulting practice with expertise spanning 500+ enterprise migrations and compliance implementations across HIPAA, SOC 2, and FedRAMP environments.

Need Expert Help?

Our SharePoint consultants are ready to help you implement these strategies in your organization.