How to Fix Microsoft 365 Archive: Setup, Billing & Site Issues
Why Microsoft 365 Archive Problems Keep Happening
I've seen this scenario play out dozens of times: an IT admin gets the green light to cut storage costs, spins up Microsoft 365 Archive, and then hits a wall of vague errors, missing toggles, or billing screens that just won't cooperate. You're not doing anything wrong , the setup path genuinely has more moving parts than Microsoft's documentation suggests at first glance, and a wrong step early on blocks everything downstream.
Microsoft 365 Archive is a cold storage tier inside SharePoint that lets you move inactive sites and files out of your active storage quota and into a lower-cost archive layer. Content stays fully searchable through Purview Content Search and eDiscovery, permissions and metadata survive intact through the whole lifecycle, and archived sites don't count against your tenant's active storage quota. That's the promise. The reality is that getting there requires an Azure subscription, a correctly wired pay-as-you-go billing setup, and the right admin roles, in exactly the right order.
The most common reasons organizations hit a wall with Microsoft 365 Archive setup include:
- Missing Azure subscription link. The feature simply won't appear in the Microsoft 365 admin center until pay-as-you-go billing is configured against a valid Azure subscription and resource group. Admins who skip this step see a blank or locked "Archive" option under Pay-as-you-go services.
- Insufficient admin role. You need either SharePoint Administrator or Global Administrator rights. Other roles, even tenant-level billing admins, can't complete the activation. If you're working in a delegated admin scenario, this is the first thing to check.
- Unsupported site templates. Publishing sites, channel sites, and several legacy SharePoint templates are not supported for Microsoft 365 Archive. Trying to archive them from the SharePoint admin center gives you an opaque error message rather than a clear explanation.
- Teams with private or shared channels. This one trips up almost every Teams-heavy organization. A site connected to a Team that has private or shared channels cannot be archived from the SharePoint admin center UI at all. The error reads: "The group connected site with channel sites associated can't be archived." It's frustrating because the error is accurate but doesn't tell you the path forward.
- File-level archive preview gaps. The file-level archive feature is still in preview as of early 2026, and compatibility gaps across Word Online, PowerPoint Online, Teams mobile, and older Office desktop clients mean users encounter unexpected errors when interacting with archived files.
I know this is frustrating, especially when you're trying to hit a cost-reduction target or compliance deadline and the admin portal seems to be actively working against you. The good news is that once you understand the exact sequence, every one of these issues is fixable. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before anything else: confirm that your Azure subscription is linked and that pay-as-you-go billing is actually active. This single misconfiguration is behind the majority of "Microsoft 365 Archive not showing up" or "Archive option greyed out" reports I've seen.
Here's the fastest way to verify:
- Sign in to the Microsoft 365 admin center (admin.microsoft.com) with a SharePoint Administrator or Global Administrator account.
- Go to Billing > Your products and confirm you see a pay-as-you-go product line tied to an Azure subscription. If nothing shows here, you need to complete the Azure linkage first, skip to Step 1 in the full walkthrough below.
- If the Azure link is in place, go to Settings > Org settings > Pay-as-you-go services.
- Select the Settings tab. Under Storage services, look for Archive. If you see it but it's toggled off, you're one click away from being operational.
- Select Archive, then toggle on SharePoint site archive and confirm.
If Archive doesn't appear under Storage services at all, your pay-as-you-go billing isn't properly configured, even if you think it is. Go through the full Azure subscription and billing steps below rather than trying workarounds.
One more quick check: make sure you're looking at the right tenant. If your organization has multiple Microsoft 365 tenants (common with M&A environments or education institutions), it's easy to have billing configured in one and be browsing admin settings in another. The archive toggle lives at the tenant level, not the subscription level.
Microsoft 365 Archive pricing is consumption-based, you're billed per gigabyte archived beyond your license-allocated storage quota. That means before you can touch the archive feature, you need a valid Azure subscription with a resource group, and it needs to be linked to your Microsoft 365 tenant through the pay-as-you-go billing setup. There's no way around this step, and the admin center won't surface the Archive option until it's done.
If you don't already have an Azure subscription set up for this:
- Go to portal.azure.com and sign in with your organization account.
- Select Subscriptions from the left navigation, then + Add.
- Choose a subscription type (a Pay-As-You-Go subscription works for most organizations; EA agreements can also be used).
- Create a resource group, name it something descriptive like
rg-m365-archive-prod. You'll need to reference this resource group when you link billing in the next step.
Once your Azure subscription and resource group exist, go back to the Microsoft 365 admin center and navigate to Settings > Org settings > Pay-as-you-go services. From there, follow the "Configure for pay-as-you-go billing" workflow to link your Azure subscription. You'll select your Azure subscription ID and resource group from dropdowns during this process.
If the process completes successfully, you'll see a confirmation that pay-as-you-go billing is active. At that point, the Archive option under Storage services becomes visible and clickable. If it still doesn't appear, sign out of the admin center completely and sign back in, there can be a short session cache delay after billing activation.
With billing linked, actually turning on Microsoft 365 Archive is straightforward, but the exact navigation path matters because it's buried a few levels deep and the labels aren't obvious.
- In the Microsoft 365 admin center, select Settings in the left sidebar, then choose Org settings.
- On the Org settings page, select Pay-as-you-go services.
- Select the Settings tab, not the Overview tab. This is where the actual service toggles live.
- Under the Storage services section, select Archive.
- A panel slides in from the right. In the SharePoint site archive section, flip the status toggle to the on position.
- A confirmation panel appears, read it, then select Confirm.
Once confirmed, Microsoft 365 Archive is live for SharePoint site archiving. You should see the toggle status update to "On" within the panel. From this point forward, SharePoint Administrators can archive and reactivate sites from the SharePoint admin center.
By default, users can also archive individual files on SharePoint sites through the file-level archive preview. If you want to disable file-level archive for end users until it matures, which I generally recommend given the current compatibility limitations, you can control that through a separate toggle in the same panel. Keep site archiving on and leave file-level archive off until your organization is ready to manage it.
Now that Microsoft 365 Archive is enabled at the tenant level, here's how to actually archive a SharePoint site. This is where admins often run into their second round of problems, usually because they're trying to archive a site type that isn't supported, or they haven't notified site owners first.
Before you archive anything, notify the site's owners and active users. When a site is archived, all content within it becomes inaccessible to anyone, document libraries, folder structures, files, lists, list data, and permissions. End users will not be able to open or edit anything in the site until it's reactivated. This is not a soft "read-only" mode. It's a cold archive. Send a communication at least a few days in advance.
To archive a site:
- Open the SharePoint admin center (admin.sharepoint.com).
- Select Sites > Active sites from the left navigation.
- Find the site you want to archive. You can use the search bar at the top to filter by URL or name.
- Select the site name to open its details panel, or check the checkbox next to it.
- In the command bar, select the … (More actions) menu and look for the Archive option.
- Confirm the archival action in the dialog that appears.
The archive operation is near-instant for sites of any size, this is one of the genuine wins with Microsoft 365 Archive. Once complete, the site moves from Active sites to Archived sites within the SharePoint admin center, and it stops consuming your tenant's active storage quota. Content remains fully indexed for Purview Content Search, eDiscovery, and end-user search.
This is one of the most common errors I see organizations hit, and the error message itself doesn't give you enough to go on: "The group connected site with channel sites associated can't be archived."
What's actually happening: Teams sites that include private or shared channels have associated sub-sites for each channel. The SharePoint admin center UI blocks archiving the parent site when these channel sub-sites exist, because it can only archive the main site and its standard channels, not the private or shared channel sites, which use unsupported site templates.
Your options depend on what you actually need:
Option A, Use PowerShell or Graph API (partial archive): If you use PowerShell or the Microsoft Graph API to archive the site instead of the UI, the block is not enforced. Only the main team site (and its standard channels) gets archived. The private and shared channel sites remain active. This is an acceptable approach if the channel sites have minimal content or you're primarily archiving the main site's document library and lists.
To archive via PowerShell, use the SharePoint PnP module:
Connect-PnPOnline -Url "https://yourtenant-admin.sharepoint.com" -Interactive
Set-PnPSite -Identity "https://yourtenant.sharepoint.com/sites/yoursite" -ArchiveStatus ArchivedOption B, Remove channel sites first: If you can restructure the Team to remove private and shared channels (moving content elsewhere first), the main site becomes archivable through the UI. This is more disruptive but gives you a cleaner archive state.
Option C, Archive channel site content separately: Note that directly archiving the channel sub-sites themselves is not possible, they use unsupported site templates. Any content in those sub-sites that needs long-term retention should be moved to a supported site before archiving.
Reactivation is the process that turns archived content back into active, accessible content. When a site is reactivated, all of its metadata and permissions are restored exactly as they were, no data loss, no permission drift. This lossless metadata preservation is one of the core design guarantees of Microsoft 365 Archive.
To reactivate an archived site from the SharePoint admin center:
- Open the SharePoint admin center and select Sites > Archived sites.
- Find the site you want to restore.
- Select the site, then choose Reactivate from the command bar or the details panel.
- Confirm the reactivation.
The site moves back to Active sites and resumes consuming your active storage quota. Users regain full access.
For file-level reactivation, users can reactivate individual archived files directly from the SharePoint site interface at the file's original location. This is important for end users to know, if they encounter an unexpected error opening a file, they should look for a "Reactivate" option at that file's location rather than contacting IT immediately.
One important restriction: files that have been reactivated cannot be archived again for 30 days. Plan reactivations accordingly, especially if you're running automated archive/reactivate workflows. There's no override for this restriction, it's enforced at the platform level.
Also note that when archived files are copied or moved, they retain their archived state. However, if you move an archived file into OneDrive, the archived state might not always display correctly in the OneDrive UI, even though the file is still technically archived. This is a known limitation of the current preview.
Advanced Troubleshooting for Microsoft 365 Archive
Archive option not appearing for specific sites. Beyond the Teams channel site issue, several other site types are blocked from archiving: publishing sites and sites using legacy SharePoint templates. There isn't a comprehensive public list of every blocked template, but if you're hitting unexpected "can't be archived" errors on sites that don't involve Teams channels, run the following PowerShell command to check the site template in use:
Connect-PnPOnline -Url "https://yourtenant-admin.sharepoint.com" -Interactive
Get-PnPTenantSite -Identity "https://yourtenant.sharepoint.com/sites/yoursite" | Select TemplateIf the template value starts with BLANKINTERNET, PUBLISHING, or an unfamiliar legacy prefix, the site is using an unsupported type and cannot be archived at the site level.
Archived content export taking longer than expected through Purview. This is expected behavior, not a bug. Purview Content Search and eDiscovery can still locate and export archived content, but export times are longer compared to active content because the data lives in cold storage. Plan compliance workflows around this, don't schedule same-day archive + eDiscovery export operations.
Microsoft 365 Copilot and archived content. One thing worth explicitly knowing: Copilot is not trained on or grounded by archived content. If your organization uses Microsoft 365 Copilot, archiving irrelevant or outdated content actively improves the quality of Copilot responses for your users by removing noise from the active index. This is a genuine secondary benefit of good archive hygiene, not just a cost play.
Billing discrepancies. Microsoft 365 Archive is billed per gigabyte of archived storage consumed beyond your license-allocated Microsoft 365 storage quota. If your archive billing looks unexpectedly high, check whether your tenant has already exceeded its included storage quota before content was archived, storage already over-quota before archiving will show up in archive billing calculations. Review your storage consumption in the SharePoint admin center under Settings > Storage before and after major archive operations.
Confirming archive state via Microsoft Graph API. For enterprise environments that want programmatic confirmation of archive state, the Graph API exposes archive status on site objects. Use:
GET https://graph.microsoft.com/v1.0/sites/{site-id}?$select=archiveStatusThis returns the current archive state and is useful for automated inventory scripts and compliance reporting.
If you've completed all setup steps correctly, Azure subscription linked, pay-as-you-go billing active, admin role confirmed, and the Archive toggle still doesn't appear under Pay-as-you-go services after a full sign-out and sign-in cycle, something may be wrong at the tenant provisioning level that you can't fix from the admin console. Similarly, if archived sites are not showing up in Purview Content Search after 24 hours, or if you're seeing billing charges for archive storage on a tenant where you haven't archived anything, escalate directly. Contact Microsoft Support and open a ticket under "Microsoft 365 admin center, billing and services." Include your tenant ID, the Azure subscription ID you linked, and the approximate date when the issue started. These details cut the resolution time significantly.
Prevention & Best Practices for Microsoft 365 Archive
Getting Microsoft 365 Archive set up is one thing, running it well over time is another. The organizations that get the most value out of SharePoint site archive are the ones that treat it as a managed lifecycle process, not a one-time operation.
Build an archive policy before you archive anything. Decide upfront which types of sites qualify for archival, sites inactive for more than 12 months, project sites after closure, sites below a certain activity threshold, and document it. Without a written policy, you'll end up with ad hoc archiving that makes it impossible to answer "why was this site archived and who approved it?" during compliance reviews.
Always notify site owners before archiving. Microsoft explicitly recommends this, and it's not optional in practice. When a site is archived, all content becomes inaccessible immediately, not just to the archive process, but to all users. A site owner who discovers their content is gone without warning will escalate loudly, and reactivating a site that shouldn't have been archived wastes everyone's time. Build a minimum 5-business-day notification window into your archive workflow.
Separate your site archive and file archive strategies. Site-level archiving is production-ready and suitable for systematic use. File-level archiving is in preview as of early 2026, with known compatibility gaps in Word Online, PowerPoint Online, Teams mobile, macOS OneDrive sync, and Office desktop versions prior to updates from March 1, 2026. Hold off on broad file-level archive rollouts until these client gaps close and users have been trained on how to reactivate files on their own.
Monitor archive storage consumption monthly. Archive storage costs money, a lower per-GB rate than active storage, but it adds up at scale. Set a monthly calendar reminder to review archive storage consumption in the Microsoft 365 admin center. If archived content is growing faster than expected, check whether your archive policy criteria are set too aggressively or whether automated processes are archiving content that should stay active.
Test reactivation before you need it under pressure. Reactivation is fast and lossless by design, but you don't want to discover edge cases in a reactivation workflow during a compliance emergency. Do a dry run, archive a low-stakes test site, confirm it shows in Archived sites, then reactivate it and verify content and permissions are intact. This gives you a clear playbook and builds confidence that the process works in your specific tenant configuration.
- Always confirm your Azure subscription link before enabling Microsoft 365 Archive, billing disconnects are the #1 source of setup failures.
- Use the SharePoint admin center's Archived sites view as your ongoing inventory, don't rely on a spreadsheet.
- Set file-level archive to off at tenant level until your Office desktop and mobile clients are fully updated to post-March 2026 builds.
- Document which sites have been archived, why, and when, this is essential for audit trails and makes reactivation requests far easier to action.
Frequently Asked Questions
Why is the Archive option greyed out or missing in the Microsoft 365 admin center?
In almost every case, this means pay-as-you-go billing isn't properly configured yet. Microsoft 365 Archive requires an active Azure subscription linked to your tenant through the pay-as-you-go billing setup in the Microsoft 365 admin center. Without that link in place, the Archive toggle under Settings > Org settings > Pay-as-you-go services > Storage services simply won't appear. Go through the Azure subscription creation and pay-as-you-go billing configuration steps first, then sign out and back in before checking again. Also confirm you're logged in with a SharePoint Administrator or Global Administrator account, other roles won't see the option even if billing is configured.
Can users still search archived content after a SharePoint site is archived?
Yes, this is one of the core design features of Microsoft 365 Archive. Archived content remains fully indexed and searchable through Purview Content Search, end-user search, and eDiscovery search experiences. Users can find content through search, but they can't directly open or edit files in an archived site until it's reactivated. Purview Content Search and eDiscovery can also export archived content directly, though export operations on archived content take longer than they do for active content because the data lives in cold storage.
I'm getting the error "The group connected site with channel sites associated can't be archived", what does that mean?
This error means the SharePoint site you're trying to archive is connected to a Microsoft Teams team that has private or shared channels. The SharePoint admin center UI blocks site archiving in this scenario because private and shared channel sub-sites use unsupported site templates that can't be archived. Your options are: use PowerShell or the Graph API to archive the main site (only the main site and standard channels get archived; channel sub-sites stay active), or remove the private/shared channels from the Team before attempting to archive through the UI. There's no way to directly archive private or shared channel sites themselves.
Does archiving a SharePoint site affect Microsoft 365 Copilot results?
Yes, and in a good way, Copilot is not trained on or grounded by archived content. This means archiving old, inactive, or irrelevant sites actively improves the relevancy of Copilot responses for your users by removing outdated content from the active index Copilot works against. Organizations deploying Copilot at scale should consider running an archive pass on inactive SharePoint sites as part of their Copilot readiness work, it's a meaningful quality improvement, not just a storage cost-saving measure.
How long does it take to reactivate an archived SharePoint site?
Reactivation is generally fast. Microsoft's design goal for Microsoft 365 Archive is ultra-fast operation for both archiving and reactivation, regardless of site size. In practice, most site reactivations complete within a few minutes in my experience, though larger sites with very large document libraries can take longer. Once reactivated, all content, permissions, and metadata are restored exactly as they were, no reconstruction needed, no data loss. One restriction to keep in mind: if you're working with file-level archive rather than site archive, reactivated files cannot be re-archived for 30 days after reactivation.
Can I archive a SharePoint site that's associated with Microsoft Teams?
It depends on whether the Team has private or shared channels. Teams sites that use only standard channels are fully supported for Microsoft 365 Archive, you can archive them through the SharePoint admin center UI just like any other site. Teams with private or shared channels are only partially supported: the admin center UI blocks archiving, but PowerShell and the Graph API allow you to archive the main site (without the channel sub-sites). The private and shared channel sub-sites themselves cannot be directly archived because they use site templates that aren't supported by Microsoft 365 Archive. Plan your Teams archive strategy accordingly, especially if private channels contain significant content.