Not every ageing SharePoint site calls for the same exit strategy. The right approach depends on whether you need to retain content, how much PowerShell comfort your team has, and whether you are retiring one site or fifty.
| Approach | Effort | Content retained? | Storage freed? | Best for |
|---|---|---|---|---|
| M365 Archive | Low | Yes (read-only) | No (lower cost tier) | Compliance holds, uncertain content |
| Move Content + Delete | Medium-High | Selectively | Yes | Consolidating into an archive site |
| PowerShell Remove-SPOSite | Low (with script) | No (30-day recycle bin) | Yes (after 30 days) | Single site, PowerShell-comfortable admin |
| Space Master Bulk Delete | Low | No (30-day recycle bin) | Yes (after 30 days) | Multiple sites, no PowerShell required |
Option 1: Microsoft 365 Archive
Microsoft 365 Archive lets you archive an entire SharePoint site directly from the SharePoint admin centre. An archived site becomes read-only: its content is preserved and discoverable by administrators for compliance purposes, but regular users cannot access it. The site disappears from employees' SharePoint home and search results.
When to Use M365 Archive
Archive is the right choice when you are unsure whether the site's content is still needed, when the site may be subject to a legal hold, or when a compliance policy requires that records are kept but not actively used. It is also a useful holding pattern: you can archive a site, wait 60 to 90 days to confirm that no one has raised a retrieval request, and then make a final deletion decision with confidence.
Sites can be unarchived and reactivated at any time. This reversibility makes M365 Archive lower-risk than immediate deletion when stakeholder sign-off on content disposal has not yet been received.
Storage Cost and Licence Notes
Archived sites continue to count toward your tenant's total storage. The cost per gigabyte for archived storage is lower than for active SharePoint storage, but archiving does not free up your active quota. If quota recovery is your primary goal, deletion is the correct approach. If reducing storage spend while retaining content is the goal, archiving achieves that. See the Microsoft 365 Archive general availability announcement for background on this feature.
Option 2: Move Content First, Then Delete the Site
If the site contains documents that teams still reference occasionally but do not need in an active site, the move-then-delete pattern consolidates that content into a long-term archive location before the source site is removed. This is a common approach when retiring a completed project site but preserving its deliverables in a departmental archive library.
When This Approach Makes Sense
Move-then-delete works well when several retiring sites share the same document owner or department. You identify a single archive destination, migrate selected content from each retiring site using ShareMaster's Copy To or Move To tool, verify the content arrived correctly, and then delete the original sites. The archive destination becomes the permanent home for that content.
For migrating full document libraries between sites in the same Microsoft 365 tenant, Clone Master handles the transfer while preserving metadata, column values, and version history. Copy To and Move To handle file-level and folder-level transfers within a tenant without PowerShell. Both preserve document properties through the move.
The main cost of this approach is time. Reviewing what needs to be kept, running the migration, and verifying completeness takes longer than a one-click archive or delete. Reserve it for sites where content curation matters, not for bulk retirement of test or transient sites.
Option 3: PowerShell Site Deletion
The Remove-SPOSite cmdlet in the SharePoint Online Management Shell (or PnP PowerShell) permanently removes a site collection. A single command marks the site for deletion:
Remove-SPOSite -Identity "https://yourtenant.sharepoint.com/sites/OldProjectSite" -NoWait
The -NoWait flag queues the deletion without waiting for confirmation, which is useful when deleting multiple sites in sequence via a script.
What Happens to Site Content After Deletion
Deleted sites move to the SharePoint admin recycle bin - not the end-user recycle bin - and stay there for 30 days. A SharePoint administrator can restore any site from the admin centre within that window. After 30 days, the site and all its content are permanently removed and storage is released.
PowerShell is the right choice for a single retirement or when you have a list of sites to retire and are comfortable scripting a loop. It is less suitable when you need a clear UI audit trail showing which sites were retired and when, or when the task is assigned to someone without PowerShell experience.
Option 4: Bulk Delete with Space Master
ShareMaster's Space Master includes a Bulk Delete Sites tool that lets you select and delete multiple SharePoint site collections from a list interface, without writing PowerShell. You see a clear list of sites with their URLs and storage size, select the ones to retire, and initiate the deletion from within the app.
When to Choose Space Master for Site Cleanup
Bulk Delete Sites is the right choice when you need to retire five, twenty, or fifty sites at once and do not want to run a PowerShell script. It is also useful when the admin carrying out the cleanup is not comfortable in the command line, or when you need a repeatable cleanup workflow that non-technical project managers can hand off to IT without writing documentation for a script.
The deletion process follows the same 30-day admin recycle bin behaviour as PowerShell. Sites deleted through Space Master can be restored within that window from the SharePoint admin centre.
See everything included in Space Master, including the Version Trimmer, Image Reducer, and Empty Folder Remover that can reduce a site's storage footprint before you decide whether to keep or retire it.
When Should You Archive vs. Delete a SharePoint Site?
Archive when the site contains content that may be needed for future compliance or legal requests, when content owners have not confirmed all documents are retrievable elsewhere, or when the site has been active in the past year. Delete when content has been migrated or confirmed redundant, or when you need to recover storage immediately.
Archive the site when:
- The site may be subject to a legal hold or eDiscovery request
- Retention policies apply to content on the site
- Stakeholders have not yet signed off on content disposal
- You need a reversible first step before committing to deletion
- The site contains historical records your organisation must keep
Delete the site when:
- Content has been migrated to another location and verified complete
- The site was a test, sandbox, or training environment
- All content owners have confirmed nothing is required
- The site has been inactive for more than 12 months with no known compliance hold
- Storage recovery is the primary driver of the decommission
Decision Matrix
| Situation | Recommended Approach |
|---|---|
| Site may be needed for compliance or eDiscovery | M365 Archive |
| Consolidating content from multiple sites into one archive | Move Content + Delete |
| Single site, confident nothing is required, admin comfortable with PowerShell | PowerShell Remove-SPOSite |
| Retiring 5 or more sites at once, no PowerShell | Space Master Bulk Delete |
| Uncertain whether content is still needed | M365 Archive (review in 90 days) |
| Need to recover storage quota this month | Delete (PowerShell or Space Master) |
| Accidentally deleted a site within the last 30 days | Restore from SharePoint admin recycle bin |
Frequently Asked Questions
Can a deleted SharePoint site be restored?
Yes, within 30 days. When a site is deleted via the admin centre, PowerShell, or Space Master, it moves to the SharePoint admin recycle bin. A SharePoint administrator can restore it from there. After 30 days, the site is permanently removed.
Does archiving a SharePoint site free up storage quota?
No. Archiving keeps content counted against your tenant's total storage, but at a lower cost tier than active storage. To reduce your active storage quota, you need to delete the site or delete content within it.
What admin role is required to decommission a site?
SharePoint Administrator or Global Administrator. Site collection administrators can delete sites they own, but they cannot use the Microsoft 365 Archive feature or delete sites via the SharePoint admin centre unless they also hold the SharePoint Administrator role.
Before decommissioning sites, get a clear picture of which ones are actually inactive. Use ShareMaster's guide to identifying inactive SharePoint sites to build your retirement shortlist.