Microsoft 365 Archive: Auto-Archive, Policies, and Storage Costs
Why Microsoft 365 Archive Trips Up So Many Admins
Here's a scenario I see constantly in enterprise IT environments: a SharePoint admin gets a ticket saying the tenant is hitting its storage quota ceiling, leadership wants the cost under control, and someone in a Teams channel mentions "just archive the old sites." Simple enough, right? Then the admin logs into the SharePoint admin center, can't find a toggle, gets an error about pay-as-you-go billing not being configured, and now has three more tickets instead of one.
Microsoft 365 Archive is genuinely one of the better solutions Microsoft has shipped for long-term SharePoint content retention , but it comes with a setup chain that's easy to break. The product lives across two admin centers (Microsoft 365 admin center and SharePoint admin center), requires an active Azure subscription tied to pay-as-you-go billing, and has a non-obvious separation between site-level archive and the newer file-level archive preview. When any link in that chain is missing, the UI just shows grayed-out controls with no helpful explanation.
What makes this worse is that Microsoft 365 Archive storage costs aren't visible in the same place as your regular Microsoft 365 storage consumption. Your archived SharePoint content moves out of your tenant's active storage quota and into a completely separate "cold storage tier" , which means the billing shows up in Azure, not in your M365 admin center dashboard. Admins who aren't watching their Azure cost alerts have gotten surprise invoices because of this.
The other big pain point: not every site type supports archiving. Publishing sites, legacy site templates, and sites associated with Teams that include private or shared channels all have varying degrees of support, and the error messages you get when you try to archive an unsupported site are vague at best. You'll see something like "The group connected site with channel sites associated can't be archived" in the SharePoint admin center with no clear next step.
I've also seen IT teams run into problems after Microsoft's March 2026 update, when older Office desktop apps that hadn't been updated lost the ability to properly handle file-level archived content. Users started reporting that files were failing to open without any useful error message, and the help desk didn't know why. Understanding the full scope of Microsoft 365 Archive limitations, before you flip the switch, is the difference between a smooth rollout and a support ticket avalanche.
This guide walks you through the complete setup, the common errors at each stage, how SharePoint archive storage pricing actually works, and what enterprise admins need to know about Teams integration and compliance scenarios. Browse all Microsoft fix guides →
The Quick Fix, Try This First
If you opened this guide because archiving is grayed out in your SharePoint admin center, the answer is almost always the same: pay-as-you-go billing hasn't been configured or linked. Microsoft 365 Archive requires an Azure subscription tied to your tenant before anything works. Here's how to check and fix that in under 10 minutes.
First, go to the Microsoft 365 admin center (admin.microsoft.com). In the left-hand navigation, go to Settings > Org settings. On the Org settings page, click the Pay-as-you-go services option, if you don't see this, you either don't have Global Administrator or SharePoint Administrator permissions, or the option hasn't appeared yet for your tenant region.
Once you're on Pay-as-you-go services, click the Settings tab. Under Storage services, you'll see an Archive entry. Click it. A side panel slides open showing the Microsoft 365 Archive configuration. At the top, check whether an Azure subscription is linked. If the subscription field is empty or shows "Not configured," that's your problem, you need to complete the pay-as-you-go billing setup in Azure first before the toggle becomes active.
If billing is configured and the toggle is still grayed out, sign out of the admin center completely and sign back in. There's a known propagation delay of up to 30 minutes after billing gets linked before the Archive toggle activates in the UI. Refreshing the page alone doesn't always clear it.
Once billing is in place and the toggle is active, flip it on for SharePoint site archive, hit Confirm on the confirmation panel, and then head over to the SharePoint admin center to start archiving specific sites. The option will now appear in site management, it wasn't there before because the feature wasn't enabled at the tenant level.
Microsoft 365 Archive billing flows through Azure, this isn't optional, and there's no workaround. If your organization already has an active Azure subscription tied to the same tenant, you're halfway there. If not, you'll need to create one first at portal.azure.com.
Log into the Azure portal with a Global Administrator account. Navigate to Subscriptions in the left-hand blade, then click + Add. Select the subscription type appropriate for your organization (most enterprises use Pay-As-You-Go or an Enterprise Agreement). Complete the billing profile setup, you'll need a valid payment method on file.
Once your subscription exists, create a resource group to keep Microsoft 365 Archive costs isolated and easy to track. In the Azure portal, go to Resource groups > + Create. Name it something like rg-m365-archive-prod and assign it to the same region as your Microsoft 365 tenant. Using a dedicated resource group means your Azure cost analysis can filter specifically on archive spend without noise from other services.
After the resource group is created, make a note of the Subscription ID, you'll need it in the next step when you configure pay-as-you-go billing in the Microsoft 365 admin center. If you skip the resource group creation, you can still proceed, but cost tracking becomes harder down the line, especially in larger organizations managing SharePoint archive storage costs across multiple departments.
When this step is done correctly, you should see your new subscription listed under Subscriptions in the Azure portal with a status of Active. Any other status (Disabled, Warned, Past Due) will block the next step.
This is the step that most setup guides gloss over, and it's where the majority of Microsoft 365 Archive configuration errors originate. The Microsoft 365 admin center needs to be explicitly linked to your Azure subscription before archive features become available.
In the Microsoft 365 admin center (admin.microsoft.com), navigate to Settings > Org settings > Pay-as-you-go services. On this page, you'll find a prompt to connect an Azure subscription. Click Link Azure subscription or the equivalent setup button, the exact label varies slightly depending on your tenant's region and M365 update ring.
You'll be prompted to select the Azure subscription and optionally a resource group. Select the subscription you created (or your existing one) and the resource group you set up in Step 1. Confirm the billing details. The system will validate the connection, this usually takes about 2–3 minutes.
If you see an error during this linking step that reads something like "Unable to complete the operation. Try again later," check the following: the account you're using must have both SharePoint Administrator or Global Administrator rights in M365 and at minimum Contributor access on the Azure subscription. A common mistake is having an account with full M365 admin access but only Reader rights in Azure, the billing link will silently fail or throw a generic error.
Once the link is established, the Pay-as-you-go services Settings tab will show your subscription as connected. From this point, services like Microsoft 365 Archive and Microsoft 365 Backup become available to enable. The connection you just made controls billing for both.
With billing linked, enabling Microsoft 365 Archive takes about 90 seconds, but there are two separate toggles and it's easy to only activate one of them. Here's exactly what to do.
In the Microsoft 365 admin center, go to Settings > Org settings > Pay-as-you-go services and click the Settings tab. Under Storage services, click Archive. The Microsoft 365 Archive side panel opens on the right.
You'll see two sections: SharePoint site archive and File archive (preview). The site archive toggle is what you need for archiving entire SharePoint sites. The file archive preview is for file-level granularity, more on that in Step 4. For now, toggle SharePoint site archive to On.
A confirmation panel appears. Click Confirm. The panel closes and the toggle should now show as enabled. Give the system 5–10 minutes before heading to the SharePoint admin center, there's a propagation delay and the archive option in the SharePoint admin center won't appear immediately.
If you're in a large tenant with regional data residency configured, verify that your SharePoint content locations align with your Azure subscription region. Mismatched regions can cause the archive toggle to appear enabled in the M365 admin center while actually failing silently when you try to archive individual sites. The SharePoint admin center will surface this as a site-specific error rather than a global one.
Once propagation is complete, the Archive action will appear in the SharePoint admin center when you select any eligible site. If it still doesn't appear after 30 minutes, try the sign-out/sign-in refresh mentioned in the Quick Fix section above.
Now for the actual archive action. Head to the SharePoint admin center (your-tenant-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx, or reach it via the Microsoft 365 admin center under Admin centers > SharePoint).
In the left navigation, click Sites > Active sites. Find the site you want to archive. You can use the search bar at the top to filter by site name or URL, useful if you're managing hundreds of sites. Click the site name to select it (don't open it, just select the checkbox or click the row to highlight it).
With the site selected, click the ... (more options) menu or look for the Archive button in the top action bar, its exact placement depends on your admin center version. Click Archive. A confirmation dialog will appear explaining that the site will become inaccessible to all users once archived. Confirm the action.
The site moves from Active sites to a transitional state and then appears under Archived sites within the SharePoint admin center. Archiving is designed to be ultra-fast regardless of site size, Microsoft built this explicitly for large sites. You won't need to wait hours for a large document library to be processed the way you might with third-party archiving tools.
Once archived, the site no longer counts against your tenant's active Microsoft 365 storage quota. Instead, it begins accruing charges under the Microsoft 365 Archive storage cost model, billed per gigabyte through the linked Azure subscription. Users who try to access the site URL will see an error page, not a "site deleted" message, but a clear indication the site is unavailable. You can confirm success by checking the site now appears in the Archived sites view in the SharePoint admin center.
Microsoft 365 Archive's file-level archiving capability, currently in preview, lets you archive individual files within a SharePoint site rather than the entire site. This is genuinely useful for sites that are still active but contain aging documents that don't need to be in hot storage.
To enable the file archive preview, return to the Microsoft 365 Archive panel in the M365 admin center (Settings > Org settings > Pay-as-you-go services > Settings > Archive). In the File archive (preview) section, toggle it to On. Once enabled, users with the right permissions on a SharePoint site can archive individual files directly from the SharePoint interface.
However, before you roll this out to end users, there are serious limitations you need to communicate. File-level archiving currently does not work correctly with Word Online, PowerPoint Online, Teams file tabs, OneDrive and SharePoint mobile apps, macOS with the OneDrive sync client, and older Windows versions (Windows 10 and earlier) using the OneDrive sync client. Office desktop apps that haven't received updates since before March 1, 2026 also fail to handle archived files correctly, they'll produce confusing error messages when users try to open them.
A file that gets reactivated from archive cannot be re-archived for 30 days, plan your lifecycle policies around this. Also, certain file types simply cannot be archived at the file level: OneNote notebooks, SharePoint pages, and SharePoint agent files are all excluded. The Site Assets library on any SharePoint site is also off-limits for file-level archive.
# PowerShell: Archive a specific file using PnP PowerShell (preview)
# Requires PnP.PowerShell module and appropriate permissions
Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/OldProjectSite" -Interactive
$file = Get-PnPFile -Url "/sites/OldProjectSite/Shared Documents/Q1-2023-Report.xlsx" -AsListItem
# File-level archive via Graph API or SharePoint REST API, use Set-PnPListItem or invoke REST directly
# Consult Microsoft Graph beta endpoints for file archive state management during previewWhen file-level archive is working correctly, archived files show a visual indicator in the SharePoint document library interface to signal they're in cold storage. If a user needs the file, they can reactivate it from its original location, and they should understand they'll need to wait for reactivation before the file opens normally.
Advanced Troubleshooting for Microsoft 365 Archive
The Teams Channel Site Error
One of the most common errors IT admins hit when trying to archive SharePoint sites is: "The group connected site with channel sites associated can't be archived." You'll see this when attempting to archive a SharePoint site that backs a Microsoft Teams workspace with private or shared channels. Each private or shared channel in Teams gets its own separate SharePoint site, and those channel sites use site templates that Microsoft 365 Archive doesn't support.
The behavior is different depending on how you attempt the archive. From the SharePoint admin center UI, the operation is blocked outright, you get the error and nothing moves. Through PowerShell or the Microsoft Graph API, the operation isn't explicitly blocked, but it only archives the main team site (the standard channels). The private and shared channel sites stay active. And you can't then go archive those channel sites manually either, because they use unsupported site templates. This is a known limitation, not a bug you can work around.
Unsupported Site Templates
Publishing sites and certain legacy SharePoint site templates also can't be archived. If you're trying to archive an old intranet built on the publishing site template, you'll need to migrate the content to a modern communication site first if you want archive functionality. The SharePoint admin center typically shows the template type in the site details, filter your active sites by template to identify which ones are ineligible before planning your archive rollout.
Using PowerShell for Bulk Archive Operations
For large-scale archive operations, the SharePoint admin center's UI becomes impractical. The Microsoft Graph API and PnP PowerShell both support site archiving programmatically. Here's a basic pattern for archiving multiple sites via PowerShell:
# Bulk archive inactive sites using PnP PowerShell
# Install: Install-Module PnP.PowerShell
Connect-PnPOnline -Url "https://contoso-admin.sharepoint.com" -Interactive
$sitesToArchive = @(
"https://contoso.sharepoint.com/sites/OldProject2022",
"https://contoso.sharepoint.com/sites/ClosedDepartment",
"https://contoso.sharepoint.com/sites/ArchivedTeam2021"
)
foreach ($siteUrl in $sitesToArchive) {
try {
# Set site to archived state via Set-PnPTenantSite or Graph API call
Write-Host "Archiving: $siteUrl"
# Note: Use Microsoft Graph PATCH /sites/{site-id} with archivalInfo property
# during preview period, check Microsoft Graph changelog for GA endpoints
}
catch {
Write-Warning "Failed to archive $siteUrl : $_"
}
}Compliance, eDiscovery, and Purview with Archived Content
One of the strongest selling points of Microsoft 365 Archive, versus third-party cold storage, is that archived content stays fully indexed for Microsoft Purview. Purview Content Search, eDiscovery, and compliance holds all work against archived content. The caveat: exporting archived content through eDiscovery takes longer than exporting active content. If you're running a legal hold and need to produce documents quickly, factor in that retrieval time. Your legal team should know about this before you archive anything under an active hold.
Full end-user search still surfaces archived content in SharePoint search results. However, the content is flagged as archived, and clicking through to access it directly will fail until it's reactivated.
Copilot and Archived Content
Microsoft 365 Copilot is explicitly not trained on archived content. This is documented behavior, not a side effect. If you're trying to use Microsoft 365 Archive specifically to keep Copilot responses focused and relevant, this is working as intended, archiving genuinely removes content from Copilot's context. If someone asks why Copilot can't find an old document, and that document is in an archived site, this is your answer.
Prevention & Best Practices for Microsoft 365 Archive
I've helped enough organizations roll out Microsoft 365 Archive to have a clear picture of what separates a clean deployment from a messy one. The technical setup is actually the easy part, the organizational hygiene around it matters more than people expect.
Build a site lifecycle policy before you flip any switches. Microsoft 365 Archive is most effective when it's part of a formal lifecycle program. Define what "inactive" means for your organization, is it 90 days with no new file uploads? No user visits in 6 months? No document modification in a year? Nail down the criteria, document them, and communicate them to site owners before anything gets archived. Sites that get archived without warning generate support tickets and erode trust in IT.
Understand Microsoft 365 Archive storage pricing before you scale. The cost model is pay-as-you-go, billed per gigabyte through Azure. For most organizations, the price per GB for archived content is lower than the standard M365 active storage overage rate, that's the whole point. But if you're archiving tens of terabytes, set Azure cost alerts on the resource group you dedicated to archive billing. Surprises on the Azure bill are avoidable with a $10 alert threshold set on day one.
Maintain a reactivation runbook. Archive site reactivation (moving a site back to active status from the cold storage tier) restores all metadata, permissions, and content, Microsoft designed this to be lossless. But reactivation isn't instant, and users who suddenly need access to an archived site at 4pm on a Friday will not find that acceptable. Have a documented process for reactivation requests, including who can approve them and expected turnaround time.
Test file-level archive in a non-production environment first. The preview limitations are real and not minor. Word Online and PowerPoint Online failing on archived files affects most end users. Deploy file-level archiving to a pilot group with clear user guidance before any broad rollout.
- Set Azure budget alerts on your archive resource group to catch unexpected Microsoft 365 Archive storage cost increases early, before the invoice arrives.
- Filter your SharePoint admin center Active sites by last modified date to build your first archive candidate list, sites untouched for 12+ months are low-risk starting points.
- Create a SharePoint communication site or Teams announcement before your first archive run, so users know the policy and who to contact if they need a site reactivated.
- Exclude any sites with active Microsoft Purview retention policies or legal holds from auto-archive workflows, confirm with your compliance team before archiving anything that might be in scope for litigation.
Frequently Asked Questions
How much does Microsoft 365 Archive actually cost per GB?
Microsoft 365 Archive uses a pay-as-you-go pricing model billed through your linked Azure subscription, you pay based on the number of gigabytes stored in the cold storage tier. The specific per-GB rate is listed on Microsoft's official pricing page and is designed to be lower than the standard Microsoft 365 active storage overage rate, making it economical for long-term retention of inactive SharePoint content. You can track exact spend in the Azure portal under your dedicated resource group. Note that reactivating content doesn't trigger a separate charge beyond the standard active storage consumption, but the reactivated content then counts against your active storage quota again.
Can I archive a Teams site that has private or shared channels?
This one's tricky. If you're using the SharePoint admin center UI, you'll get a hard block with the message "The group connected site with channel sites associated can't be archived." Through PowerShell or the Microsoft Graph API, the archive operation isn't blocked, but it only archives the main team site associated with standard channels. The private and shared channel sites (which each have their own SharePoint site behind them) stay active and cannot be archived directly because they use unsupported site templates. If your Teams workspace only uses standard channels, archiving works fully. The safest approach for Teams-connected sites with mixed channel types is to archive the content manually or migrate it before attempting site archiving.
Will Microsoft Copilot be able to search through my archived SharePoint content?
No, and this is intentional, documented behavior. When content is moved into the Microsoft 365 Archive cold storage tier, Copilot is explicitly excluded from being trained on or searching through that content. Microsoft positions this as a benefit: keeping archived content out of Copilot's context improves the relevancy of Copilot's responses by keeping it focused on your active, current content. If users report that Copilot can't find certain documents, and those documents are in archived sites, reactivating the site is the only way to make them available to Copilot again.
How long does it take to reactivate an archived SharePoint site?
Microsoft designed Microsoft 365 Archive reactivation to restore all site content, metadata, and permissions completely, it's a lossless operation. The time it takes varies by site size and tenant load, but in practice most reactivations complete within minutes to a few hours for standard-sized sites. Very large sites with extensive document libraries may take longer. Once reactivated, the site returns to your active storage quota and full user access is restored. One important caveat for file-level archive: a file that's been reactivated cannot be re-archived for 30 days after reactivation, plan your workflows around this cooldown period.
Can I archive individual files instead of the whole SharePoint site?
Yes, but it's in preview and comes with notable restrictions. File-level archive is available for SharePoint sites (not OneDrive) and requires the File archive preview to be enabled separately in the Microsoft 365 admin center under Pay-as-you-go services > Archive. Once enabled, users can archive specific files from within SharePoint document libraries. The known limitations are significant: Word Online, PowerPoint Online, Teams mobile, SharePoint mobile, macOS OneDrive sync clients, older Windows devices, and Office desktop apps that haven't been updated since before March 1, 2026 all have issues with archived files. Certain file types can't be archived at the file level at all, OneNote files, SharePoint pages, SharePoint agents, and anything in the Site Assets library are excluded.
What happens to SharePoint permissions and metadata when a site is archived?
All permissions and metadata are fully preserved when a site is archived with Microsoft 365 Archive, this is one of its key advantages over third-party cold storage solutions. Document libraries, folder structures, list data, custom metadata columns, and permission inheritance all stay intact inside the archive. When the site is reactivated, everything comes back exactly as it was when it was archived. The only thing users lose during the archive period is direct access to the content, the site is inaccessible to everyone, including site owners, while in the cold storage tier. Microsoft Purview compliance features, including Content Search and eDiscovery, can still reach archived content even while the site itself is inaccessible to regular users.