How to Fix Microsoft 365 Archive Setup & Site Errors
Why This Is Happening
You've been tasked with cleaning up your organization's SharePoint environment. Maybe storage is ballooning, Copilot is returning noisy results from five-year-old project sites, or your compliance team needs inactive data parked somewhere searchable but cheap. You go to set up Microsoft 365 Archive, and then , nothing works the way it should. The toggle is greyed out. The site won't archive. You get an error that says something about channel sites you've never seen before. Sound familiar?
I've walked through Microsoft 365 Archive deployments across dozens of Microsoft 365 tenants, and the same pain points keep showing up. Most of them come down to three root causes: billing isn't wired up correctly, the admin role doesn't have the right permissions, or the site you're trying to archive falls into one of the unsupported template categories that Microsoft's UI error messages barely explain.
Here's the thing about Microsoft 365 Archive's error messages, they're technically accurate but almost never helpful. "The group connected site with channel sites associated can't be archived" tells you what the problem is, but not why, and definitely not how to work around it. That's the gap this guide fills.
Microsoft 365 Archive moves inactive SharePoint content into a cold storage tier. Once a site lands there, it no longer eats into your tenant's active storage quota, it counts against Archive storage consumption instead, billed at a lower per-GB rate on a pay-as-you-go model. That's the value proposition. But the path to actually getting content archived involves an Azure subscription, pay-as-you-go billing configuration, SharePoint admin center access, and a solid understanding of which site types Microsoft 365 Archive actually supports. Miss any one of those, and you hit a wall.
Who runs into this? Mostly SharePoint Administrators and Global Administrators at mid-to-large organizations who are managing sites at scale, lifecycle management projects, compliance-driven retention, or Copilot optimization initiatives where old content polluting AI responses is the driver. If any of that sounds like your situation, you're in the right place.
One more thing worth calling out early: Microsoft 365 Archive's file-level archiving feature is still in preview as of April 2026. If you're seeing inconsistent behavior with individual file archiving, especially in Word Online, Teams mobile, or on macOS with the OneDrive sync client, that's expected behavior for a preview feature, not a bug in your setup. We'll cover all of that in detail below.
The Quick Fix, Try This First
Before diving into the full step-by-step, check this one thing: is pay-as-you-go billing actually enabled in your Microsoft 365 admin center? This is the single most common reason Microsoft 365 Archive setup fails or shows a greyed-out toggle. Without an active Azure subscription linked to your tenant through pay-as-you-go billing, the Archive feature literally cannot be turned on, the UI won't let you proceed.
Here's how to check in under two minutes:
- Sign in to the Microsoft 365 admin center at
admin.microsoft.comwith your SharePoint Administrator or Global Administrator account. - Go to Settings > Org settings.
- Select Pay-as-you-go services from the list.
- Click the Settings tab.
- Under Storage services, look for Archive. If the toggle is greyed out or the entire section is missing, your Azure subscription is either not linked or not configured correctly for pay-as-you-go billing.
If that's the issue, jump straight to Step 1 below, that covers the Azure subscription and billing setup from scratch. If the Archive option is visible and the toggle is available, your billing is fine. In that case, jump to Step 2 and work through the enabling sequence.
If Archive is enabled but specific sites still won't archive, the problem is almost certainly a site template incompatibility, specifically a Teams site with private or shared channels attached. Step 4 covers the exact error and the PowerShell workaround for that scenario.
Microsoft 365 Archive doesn't run on a flat monthly license, it's a consumption-based service billed per gigabyte of archived content. That means before you can flip a single toggle in the admin center, your tenant needs an active Azure subscription with pay-as-you-go billing configured. If your organization already uses Azure for other services, you may be able to use an existing subscription. If not, you'll need to create one.
To set up the Azure side, go to portal.azure.com and create a new subscription if needed. You'll also need a resource group, think of this as a logical container in Azure that groups billing and management for the Archive service. Name it something recognizable, like M365Archive-RG, and assign it to your subscription.
Once the Azure subscription and resource group exist, go back to the Microsoft 365 admin center:
- Navigate to Settings > Org settings > Pay-as-you-go services.
- Select Set up pay-as-you-go billing and follow the prompts to link your Azure subscription.
- You'll be asked to select the Azure subscription and resource group you just created.
After linking, give it five to ten minutes before expecting the Archive toggle to appear. Azure billing connections aren't instant. If after fifteen minutes the Archive option under Storage services still doesn't show, try signing out of the admin center and back in, sometimes the UI just needs a refresh to pick up the newly linked subscription.
When it works: the Pay-as-you-go services page will show a green connected status next to your Azure subscription, and the Archive option will be visible under the Settings tab.
With billing in place, enabling Microsoft 365 Archive itself takes less than two minutes. But the exact navigation path matters, a lot of people waste time hunting around the wrong admin portal because Microsoft 365 Archive spans both the Microsoft 365 admin center (for enabling the feature) and the SharePoint admin center (for actually archiving sites). These are two different portals.
In the Microsoft 365 admin center (admin.microsoft.com):
- Go to Settings > Org settings.
- Select Pay-as-you-go services.
- Click the Settings tab.
- Under Storage services, click Archive.
- In the Microsoft 365 Archive panel that slides out, locate the SharePoint site archive section.
- Toggle the status switch to On.
- An Enable SharePoint archiving confirmation panel will appear, click Confirm.
That's it. Microsoft 365 Archive is now enabled at the tenant level. By default, file-level archiving for users is also enabled at this point (though file-level archive is still in preview and comes with limitations we'll cover in Step 5).
What you should see: the toggle shows as active/on, and when you now navigate to the SharePoint admin center at admin.microsoft.com/sharepoint, you should see Archive-related options available in the Sites management section. If you don't see them immediately, a hard browser refresh (Ctrl+Shift+R) usually does the trick.
Now for the part that actually does the work. Once Microsoft 365 Archive is enabled, you manage individual site archiving from the SharePoint admin center, not the Microsoft 365 admin center. This trips people up constantly.
Navigate to admin.microsoft.com/sharepoint (or go to the SharePoint admin center directly). From there:
- In the left navigation, go to Sites > Active sites.
- Find the site you want to archive. You can search by name, URL, or filter by template type.
- Select the site by clicking its checkbox.
- In the command bar that appears, look for the Archive option (it may be under a "..." or additional options menu depending on your admin center version).
- Confirm the archiving action when prompted.
Before you archive any site, one important operational step: notify site owners and end users first. Once a site is archived, it's no longer directly accessible to anyone. That includes all document libraries, folder structures, files, lists, list data, permissions, and metadata, the entire site moves to the cold storage tier. Users hitting that URL will get an access error, not a "this is archived" message. Give people enough lead time to download anything they actively need.
What the archive actually includes: every piece of content in the site moves together, documents, list items, folder hierarchy, permissions, and all metadata. The good news is that metadata and permissions are preserved completely and restored on reactivation. Full content search continues to work through Microsoft Purview, eDiscovery, and the standard SharePoint/M365 search experiences even while the site is archived.
This is the most common error people hit when trying to archive Teams-connected SharePoint sites, and the error message does almost nothing to help you understand what's actually happening.
The exact error text you'll see in the SharePoint admin center:
The group connected site with channel sites associated can't be archived.What this means: the Teams site you're trying to archive has one or more private channels or shared channels associated with it. Each private or shared channel in Teams gets its own separate SharePoint site behind the scenes. The SharePoint admin center UI refuses to archive the parent site in this configuration entirely.
Your options:
Option A, Use PowerShell or the Graph API instead. Unlike the SharePoint admin center UI, PowerShell and the Graph API will not block the archiving action outright. However, there's a catch: only the main site associated with the Team (and its standard channels) gets archived. The private and shared channel sites stay active. You can't directly archive those channel sites either, because they use site templates that Microsoft 365 Archive doesn't support.
To archive the main site via PowerShell using the SharePoint PnP module:
Connect-PnPOnline -Url https://yourtenant-admin.sharepoint.com -Interactive
Set-PnPSite -Identity "https://yourtenant.sharepoint.com/sites/yourteamsite" -Archived $trueOption B, Remove the private/shared channels before archiving, if you have admin rights over the Team in question and the channels are truly inactive. This is the cleaner path if you want the UI to work, but it's destructive to the Teams channel structure.
Teams sites with only standard channels are fully supported for archiving through the SharePoint admin center UI with no issues.
File-level archiving, the ability to archive individual files rather than entire sites, is still in preview as of April 2026, and the list of known limitations is genuinely long. If you or your users are seeing errors when trying to open, load, or interact with archived files, this section explains what's going on and what you can actually do about it.
Applications and scenarios where file-level archive has known issues right now:
- Word and PowerPoint Online, archived files may fail to load or display incorrect errors
- Teams, OneDrive, and SharePoint mobile apps, archived files may not behave as expected
- macOS with the OneDrive sync client, archived state may not be honored
- Windows 10 and earlier with the OneDrive sync client, same issue; also affects Windows devices not configured to receive frequent updates
- Older Office desktop apps that haven't received updates since March 1, 2026
- Clipchamp and Power BI, will fail to load archived content when importing
A few important rules that govern file-level archiving that users frequently bump into:
- File-level archive only works on SharePoint sites, not OneDrive. If an archived file is moved or copied into OneDrive, its archived state may not show correctly in the OneDrive UI.
- Files that have been reactivated cannot be re-archived for 30 days. If a user accidentally reactivates a file, it's stuck in active storage for a month.
- The following file types cannot be archived at all: OneNote notebooks, SharePoint pages, and SharePoint agents.
- The Site Assets library on SharePoint sites does not support file-level archive.
If users encounter unexpected errors opening archived files, the path forward is to reactivate the file at its original location. Make sure users know how to do this before you roll out file-level archiving broadly, the in-app error messages for archived content are not always clear that reactivation is the solution.
Advanced Troubleshooting
Verifying Archive State with PowerShell
When the UI doesn't give you clarity on why a site isn't archiving or what state it's currently in, PowerShell is your diagnostic tool. Using the PnP PowerShell module, you can query site archive states directly:
Connect-PnPOnline -Url https://yourtenant-admin.sharepoint.com -Interactive
Get-PnPTenantSite -Identity "https://yourtenant.sharepoint.com/sites/yoursite" | Select-Object Url, IsArchived, ArchivedBy, ArchivedTimeThis will tell you whether a site is archived, who initiated the archive, and when it happened. Useful for auditing and for confirming that a bulk archive operation actually completed.
Graph API for Bulk Operations
For enterprise environments where you need to archive dozens or hundreds of sites programmatically, the Microsoft Graph API exposes site archive management endpoints. This is the right tool for automated lifecycle management pipelines, not one-off admin center clicks. The Graph API approach also bypasses the SharePoint admin center UI's restrictions on channel site archiving (with the partial archive behavior noted in Step 4).
Monitoring Archive Storage Consumption in Azure
Since Microsoft 365 Archive bills against your Azure subscription on a per-GB pay-as-you-go basis, you should set up Azure cost alerts to avoid surprise invoices. In the Azure portal, navigate to your linked subscription, go to Cost Management + Billing > Budgets, and create an alert for Microsoft 365 Archive consumption. Set the alert threshold at around 80% of your expected monthly budget to give yourself reaction time.
Purview eDiscovery and Search Behavior for Archived Content
A question I hear a lot: "Can we still find archived content in eDiscovery?" Yes, full content search continues to work for Purview Content Search, end-user search, and eDiscovery experiences even after a site is archived. Content is indexed and searchable. The catch is that exporting archived content through Purview or eDiscovery may take longer than exporting active content. Plan for that in your compliance workflows, don't wait until a legal hold deadline to discover that export from archived storage takes several hours.
Supported Site Templates
If a site simply refuses to archive with no obvious explanation, check its template type. Publishing sites, channel sites, and certain legacy site template types are explicitly not supported. Before attempting to archive at scale, run a site inventory and filter out unsupported templates first, it'll save you from hitting errors halfway through a large batch operation.
Prevention & Best Practices
Getting Microsoft 365 Archive working is one thing. Keeping it working well, and avoiding the operational headaches that come with cold-storage lifecycle management at scale, is a different challenge entirely.
The single most important prevention step is building a pre-archive checklist. Before any site gets archived, someone should verify: the site template is supported, there are no active Teams private or shared channels attached, site owners and end users have been notified, and any content that users might need immediate access to has been retrieved or documented. Skipping the notification step is how you end up with support tickets at 9am Monday because a team can't access their project site.
For the file-level archive preview specifically, given how many applications still have known issues with archived files, I'd recommend keeping file-level archiving turned off for general users until the preview stabilizes further. You can manage this at the tenant level when you initially set up Archive. Don't give end users a tool that's going to generate confused support requests when Word Online throws an error on a file they didn't realize was archived.
On the billing side, review your Azure cost reports for M365 Archive storage consumption monthly. The pay-as-you-go model is cost-effective compared to active SharePoint storage, but it's easy to archive aggressively and then lose track of what's in cold storage and what it's costing. Build a quarterly review cadence where someone checks archived sites against a retention schedule and purges truly expired content rather than just accumulating cold storage indefinitely.
Finally, think about Copilot. One of the documented advantages of archiving inactive content is that Copilot doesn't train on or surface archived content, which improves the relevancy of its responses. If your organization is deploying or expanding Microsoft 365 Copilot, archiving stale SharePoint sites isn't just a storage exercise, it's directly improving your AI tooling's quality. Frame it that way to stakeholders and you'll get faster buy-in on lifecycle management projects.
- Set up Azure cost alerts for your M365 Archive consumption at 80% of expected monthly budget before you archive anything
- Run a site template audit before bulk archiving, filter out publishing sites, channel sites, and legacy templates proactively
- Notify site owners at least 5 business days before archiving any active-use site, and document that notification in your IT change log
- Keep file-level archive (preview) disabled for general users until the preview exits and app support broadens, manage it admin-only for now
Frequently Asked Questions
Why is the Microsoft 365 Archive toggle greyed out in my admin center?
Almost always, this means pay-as-you-go billing isn't linked to your tenant yet. Microsoft 365 Archive is a consumption-billed feature, it requires an Azure subscription connected through the pay-as-you-go billing setup in the Microsoft 365 admin center before the toggle becomes interactive. Go to Settings > Org settings > Pay-as-you-go services and check whether your Azure subscription shows as connected. If it's not linked, follow the billing setup steps first, then wait 10–15 minutes and refresh before trying the Archive toggle again.
Can users still search for content after a SharePoint site is archived?
Yes, search continues to work for archived content. Microsoft 365 Archive maintains searchability through Purview Content Search, standard end-user SharePoint/M365 search, and eDiscovery. The key difference is that archived content is no longer directly accessible or browseable, users can find it in search results, but clicking through to the site itself will fail until it's reactivated. For Purview and eDiscovery specifically, content can still be exported from archived storage, though exports may take longer than they would from active storage.
I'm getting "The group connected site with channel sites associated can't be archived", what do I do?
This error means the SharePoint site is connected to a Microsoft Teams team that has private or shared channels. The SharePoint admin center UI blocks archiving entirely in this case. Your workaround is PowerShell or the Graph API, both will allow you to archive the main site, though the private and shared channel sites will remain active (they can't be archived because their site templates aren't supported). Use the PnP PowerShell module and run Set-PnPSite -Identity [site URL] -Archived $true after connecting to your admin URL. If you need the channel sites archived too, you'd need to remove them from Teams first, which is a more disruptive operation.
Does archiving a SharePoint site delete or modify any of the content?
No, archiving is completely lossless. When a site is archived, everything moves to cold storage intact: all document libraries, folder structures, files, lists, list data, permissions, and every piece of metadata. When the site is reactivated, it comes back exactly as it was with all metadata and permissions restored. Microsoft 365 Archive is designed specifically to preserve the full site state rather than stripping anything down for storage efficiency. The only change is that the content is no longer directly accessible to anyone while it sits in the cold storage tier.
Why can't I archive my OneNote files or SharePoint pages with file-level archive?
Certain file types are explicitly excluded from Microsoft 365 Archive's file-level archiving feature. OneNote notebooks, SharePoint pages, and SharePoint agents cannot be archived at the file level, these are by-design exclusions, not bugs. If you need to move inactive content that includes these file types out of active storage, your option is to archive the entire site rather than individual files. Site-level archiving covers all content within the site regardless of file type, so that's the appropriate path for retiring a site that contains OneNote notebooks or SharePoint pages.
How does Microsoft 365 Archive affect Microsoft 365 Copilot responses?
Archiving content actively improves Copilot response quality. Copilot is not trained on or influenced by archived content, once a site or file is moved to the cold storage tier, it's completely excluded from Copilot's processing. This means if you have years of stale project sites, outdated policy documents, or superseded content sitting in active SharePoint, it's potentially diluting your Copilot responses with irrelevant old information. Archiving that content removes it from Copilot's scope and focuses the AI on your current, relevant data. For organizations actively deploying M365 Copilot, this is one of the most compelling operational reasons to run a SharePoint archive cleanup project.