SharePoint Site Collections: Architecture Best Practices Guide

SharePoint Site Collections: Architecture and Best Practices

Site collections are the fundamental building blocks of SharePoint Online architecture. Every piece of content, every permission assignment, and every governance boundary in SharePoint exists within a site collection. Understanding site collection architecture is essential for administrators and architects designing scalable SharePoint environments.

This guide covers site collection fundamentals, architecture patterns, governance boundaries, and management best practices for organizations of all sizes.

---

Site Collection Fundamentals

What Is a Site Collection?

A site collection is a top-level container in SharePoint that groups a set of related sites under a common administrative boundary. In modern SharePoint Online, every site you create through the admin center, Teams, or self-service provisioning is its own site collection. The legacy pattern of creating sub-sites within a single site collection is deprecated.

Key properties of a site collection:

• URL namespace: Each site collection has a unique URL (for example, contoso.sharepoint.com/sites/HR)
• Storage quota: Drawn from the tenant storage pool, configurable per site collection
• Permission boundary: The top-level permission scope; permissions inherit downward
• Content type scope: Site columns and content types defined at the site collection level are available to all libraries within it
• Feature scope: Site collection features enable functionality across all sites within the collection
• Recycle bin: Each site collection has its own first-stage and second-stage recycle bins

Modern vs Legacy Architecture

Legacy pattern (deprecated): One large site collection with many sub-sites organized hierarchically. For example, a single Intranet site collection containing sub-sites for every department, each with further sub-sites for teams.

Modern pattern (recommended): Many flat site collections, each representing a single purpose, connected through hub sites. Each department gets its own site collection associated with a departmental hub site.

The modern pattern is superior because it provides independent permission management per site, independent storage quotas and lifecycle management, the ability to move sites between hubs without data migration, better performance because each site collection is smaller, and alignment with Microsoft's investment direction.

---

Site Collection Types

Communication Sites

Communication sites are designed for broadcasting information to a broad audience. They provide modern page layouts with sections and web parts, news publishing capabilities, a clean read-only experience for most visitors, and no Microsoft 365 Group connection by default.

Use communication sites for: department portals, company intranets, project showcases, knowledge bases, policy libraries, and event sites.

Team Sites

Team sites are designed for collaboration within a group. They are connected to a Microsoft 365 Group, optionally connected to Microsoft Teams, include a shared document library, calendar, and notebook, and provide member-level editing for all group members.

Use team sites for: project workspaces, department collaboration, committee sites, and any scenario where a group of people actively creates and edits content together.

Channel Sites

When a private or shared channel is created in Microsoft Teams, SharePoint automatically provisions a channel site. These are specialized team sites with their own independent permissions aligned to channel membership, a separate storage quota from the parent team site, and limited administrative customization options.

---

Architecture Planning

Hub Site Strategy

Hub sites are the primary mechanism for organizing related site collections into logical groups. Plan your hub architecture before creating site collections.

Common hub patterns:

• Departmental hubs: HR Hub, Finance Hub, IT Hub, each with associated department sites
• Regional hubs: Americas Hub, EMEA Hub, APAC Hub for geographically distributed organizations
• Function hubs: Policies Hub, Training Hub, Projects Hub for cross-departmental functions

Each hub can have child hubs, creating a maximum two-level hub hierarchy. Associated sites can be reassigned to different hubs at any time without data migration.

Naming Conventions

Establish a naming convention before creating site collections. The URL is permanent (or difficult to change), so get it right.

Recommended patterns:

```

Department sites: /sites/HR, /sites/Finance, /sites/Legal

Project sites: /sites/Project-Alpha, /sites/Project-Mercury

Team sites: /sites/Team-Engineering, /sites/Team-Design

Event sites: /sites/Conference-2026, /sites/Summit-Q4

```

Avoid generic names like /sites/Documents or /sites/Team1. Include enough context in the URL for administrators to identify the site's purpose without opening it.

Capacity Planning

Plan site collection capacity based on expected content volume and growth. Set initial quotas conservatively and increase as needed. Monitor storage consumption monthly and adjust quotas before users hit limits.

Sizing guidelines:

• Low-activity sites (policies, reference): 1 to 5 GB
• Standard collaboration sites: 5 to 25 GB
• Active project sites: 25 to 100 GB
• High-volume repositories: 100 to 500 GB
• Large media sites: 500 GB to 1 TB (consider alternative storage for media files)

---

Managing Site Collections at Scale

Inventory and Reporting

Maintain a current inventory of all site collections. Automated reporting through PowerShell provides the most comprehensive view.

```powershell

# Comprehensive site collection inventory

Get-SPOSite -Limit All -Detailed | Select-Object @{N='Url';E={$_.Url}}, @{N='Title';E={$_.Title}}, @{N='Template';E={$_.Template}}, @{N='Owner';E={$_.Owner}}, @{N='StorageUsedGB';E={[math]::Round($_.StorageUsageCurrent/1024,2)}}, @{N='QuotaGB';E={[math]::Round($_.StorageQuota/1024,2)}}, @{N='Sharing';E={$_.SharingCapability}}, @{N='LastModified';E={$_.LastContentModifiedDate}}, @{N='HubSiteId';E={$_.HubSiteId}} | Export-Csv "SiteCollectionInventory.csv" -NoTypeInformation

```

Lifecycle Management

Every site collection should have a defined lifecycle. Creation follows the governance-approved provisioning process. Active use includes regular content updates and user activity. Review occurs after a period of inactivity (typically 180 days), with the owner confirming the site is still needed. Archive transitions inactive sites to read-only or cold storage. Deletion permanently removes sites that are no longer needed and have passed retention requirements.

Configure Microsoft 365 inactive site policies to automate the review and archive stages.

Permission Auditing

Audit site collection permissions quarterly. Check for site collections with external sharing enabled that should not have it, orphaned site collections where the owner has left the organization, site collections with broken permission inheritance at the library or item level, and guest accounts with access to sensitive sites.

```powershell

# Audit external sharing across all site collections

Get-SPOSite -Limit All | Where-Object { $_.SharingCapability -ne "Disabled" } | Select-Object Url, Title, SharingCapability | Export-Csv "ExternalSharingAudit.csv" -NoTypeInformation

```

---

Site Collection Features and Settings

Key Features to Configure

After creating a site collection, configure these features. Content Type Hub publishing syndicates enterprise content types to the site. Custom Script controls whether users can add custom scripts and web parts. Site Collection App Catalog enables site-specific SPFx solution deployment. Retention policies apply Microsoft Purview retention rules to the site's content.

External Sharing Configuration

Set external sharing at the site collection level based on content sensitivity. Sites containing regulated data (HIPAA, SOX, GDPR) should have sharing disabled or restricted to authenticated external users only. Collaboration sites may allow broader sharing with appropriate link expiration and access controls.

Sensitivity Labels

Apply Microsoft Purview sensitivity labels to site collections to enforce privacy settings (public or private), external sharing restrictions, conditional access policies, and default sharing link types. Labels provide a policy-driven approach to governance that scales better than manual configuration.

---

Troubleshooting Site Collection Issues

Site Collection Not Accessible

Check the lock state (ReadOnly, NoAccess), verify the user's permissions, confirm the Microsoft 365 Group has not been deleted (for team sites), and verify the site has not exceeded its storage quota.

Performance Issues

Site collections with performance problems typically have list views exceeding the 5,000-item threshold, deeply nested folder structures, excessive web parts on the home page, or large custom scripts running on page load. Address these by creating indexed columns for large lists, flattening folder structures, reducing web part count, and auditing custom scripts.

---

Frequently Asked Questions

How many site collections can a tenant have?

Microsoft does not publish a hard limit. Tenants with over 500,000 site collections exist. The practical limit is manageability rather than platform constraints.

Can I move a site collection to a different URL?

Yes, using the Start-SPOSiteRename PowerShell cmdlet. URL changes propagate to bookmarks and links with a redirect that lasts for a configurable period.

Should I use sub-sites or separate site collections?

Always use separate site collections connected through hub sites. Sub-sites are a legacy pattern that creates governance and performance problems at scale.

Can I merge two site collections?

There is no native merge capability. You must migrate content from one site collection to another using migration tools, then decommission the source site collection.

---

For help designing your SharePoint site collection architecture, [contact our team](/contact) for an architecture assessment. We design scalable SharePoint architectures for organizations with hundreds of sites across [regulated industries](/services) where governance boundaries directly impact compliance posture.

Site Collection Migration and Consolidation

Cross-Tenant Migration

For mergers and acquisitions, site collections may need to move between Microsoft 365 tenants. Use the Microsoft 365 cross-tenant migration feature or third-party tools like ShareGate for content migration with metadata preservation.

Site Collection Consolidation

When organizations restructure, site collections may need to be consolidated. The process involves creating a new target site collection with the desired structure, migrating content from multiple source site collections to the target, updating hub associations and navigation, redirecting old URLs to new locations, and decommissioning source site collections after a validation period.

Geo-Multi Location

For multinational organizations, SharePoint Multi-Geo allows site collections to be stored in specific geographic locations to meet data residency requirements. Configure satellite locations in the Microsoft 365 admin center and create sites in the appropriate geography.