Fix Microsoft 365 Archive: Setup & Config Errors
Why Microsoft 365 Archive Breaks , And Why the Error Messages Won't Tell You
You've got a pile of inactive SharePoint sites eating into your tenant's storage quota, leadership wants them retained for compliance, and Microsoft 365 Archive looks like the perfect answer. You go to enable it , and either the toggle is grayed out, the "Archive" button in the SharePoint admin center simply doesn't appear, or you get a vague error message that tells you absolutely nothing useful. I've seen this exact scenario play out dozens of times across organizations of every size, from 50-seat nonprofits to global enterprises.
The frustrating reality is that Microsoft 365 Archive has a hard dependency chain that must be completed in the right order before a single site can be archived. Miss one link, say, skipping the Azure subscription creation or forgetting to actually enable the feature in the Org settings panel after setting up billing, and the entire feature silently fails or disappears from view. Microsoft's admin center UI doesn't always make this dependency chain obvious, which is why so many admins end up going in circles.
Here's who typically runs into Microsoft 365 Archive problems:
- IT admins enabling Archive for the first time who don't realize pay-as-you-go billing must be configured in a completely separate admin panel before the Archive toggle appears.
- SharePoint administrators trying to archive Teams-connected sites, specifically sites tied to Teams that have private or shared channels, who hit a hard block with the error message: "The group connected site with channel sites associated can't be archived."
- Admins attempting file-level archive during the preview period who find that Word Online, PowerPoint Online, or mobile applications show broken behavior after archiving individual files.
- Global Administrators who delegated the task to a SharePoint admin, not realizing the SharePoint admin role already has sufficient permissions, no Global Admin access needed for day-to-day archive management.
- Organizations on Education tenants who don't realize there's a separate Education offering with different configuration steps.
The root causes almost always fall into three buckets: billing isn't wired up correctly, the feature hasn't been explicitly turned on even after billing is configured, or a site template type is hitting one of Archive's known limitations. None of those root causes surface as a plain-English error. Instead you get a missing button, a grayed-out toggle, or a cryptic message about "channel sites."
I also want to flag something Microsoft buries in the documentation: archived content is not directly accessible to anyone once it moves into the cold storage tier. End users who try to access an archived SharePoint site will be blocked. That's by design, but if you don't notify site owners before archiving, you're going to get a flood of helpdesk tickets. Keep that in mind throughout this guide.
The Quick Fix, Check Your Billing Setup First
Before you spend time digging through SharePoint admin center settings, do this one check. It resolves the majority of Microsoft 365 Archive activation problems I see in enterprise environments.
Open the Microsoft 365 admin center (admin.microsoft.com), then navigate to Billing > Your products. Look for an active Azure subscription linked to your tenant. If you don't see one, that's your problem, Archive uses a pay-as-you-go billing model and cannot function without an Azure subscription and resource group in place. The Archive toggle in Org settings simply won't activate without this link established.
If an Azure subscription exists, go to Settings > Org settings > Pay-as-you-go services and click the Settings tab. Under "Storage services," look for Archive. If it's listed but toggled off, that's your fix, click it, then confirm on the Enable SharePoint archiving panel. Many admins configure billing correctly but forget this final manual enable step, and the SharePoint admin center Archive option never appears as a result.
If the Archive option isn't listed under Pay-as-you-go services at all, your Azure subscription hasn't been properly linked. You'll need to complete the full setup flow starting with creating the Azure subscription and resource group, covered in detail in the step-by-step section below.
Once you've confirmed that Archive is toggled on in Org settings, go to the SharePoint admin center (your-tenant-admin.sharepoint.com), open Sites > Active sites, select any non-Teams site, and check whether "Archive" now appears in the command bar. If it does, you're live. If the Archive option still doesn't appear, move to the full step-by-step troubleshooting below.
Microsoft 365 Archive runs on a pay-as-you-go billing model, which means it needs an active Azure subscription before a single setting in the Microsoft 365 admin center will respond. If your organization already has an Azure subscription, you can skip the creation step, but you still need to confirm a resource group is assigned. If you're starting from scratch, here's exactly how to do it.
Sign into the Azure portal (portal.azure.com) with a Global Administrator account. In the left navigation, select Subscriptions. If no subscription exists, click + Add and walk through the creation wizard, you'll need a credit card or invoice agreement tied to your organization's billing profile. Once the subscription is created, note the Subscription ID; you'll need it in the next step.
Next, create a resource group. In the Azure portal, go to Resource groups > + Create. Choose the subscription you just created, give the resource group a logical name (something like M365Archive-RG works fine), and select the region closest to your tenant's data residency. Click Review + Create, then Create.
A resource group in Azure is essentially a logical container, think of it as a folder for the billing and governance of your Archive consumption. You don't put anything in it manually; Microsoft's services attach to it automatically once billing is linked.
When done correctly, you should see the new resource group listed under Resource groups in the Azure portal with a status of "Succeeded." That green status is your confirmation that the Azure side is ready. Now move to the Microsoft 365 admin center to link it.
This is the step that trips up most admins. The Azure subscription and the Microsoft 365 tenant are separate systems, and they don't link themselves automatically, you have to manually wire them together through the pay-as-you-go billing configuration in the M365 admin center.
Open the Microsoft 365 admin center and navigate to Billing > Billing accounts. You should see your organization's billing profile here. Now go to Settings > Org settings and select the Pay-as-you-go services option. On the next screen, click Set up pay-as-you-go billing.
You'll be prompted to select your Azure subscription and resource group. Choose the subscription and resource group you created in Step 1. Confirm the billing details, this is where Microsoft will charge for Archive storage consumption beyond your license-allocated Microsoft 365 storage quota. Archive storage is billed per gigabyte, so the cost scales with how much data you move to the cold storage tier.
After confirming, you should see a success confirmation screen. The Pay-as-you-go services page will now show storage services as available. If you receive an error during this step that references insufficient Azure permissions, it usually means the account you're using doesn't have the Owner or Contributor role on the Azure subscription. Check role assignments in the Azure portal under the subscription's Access control (IAM) blade and add the appropriate role to your admin account.
Once billing is configured successfully, the "Archive" option under Storage services becomes available to enable, which brings us to the next step.
Here's where many admins think they're done after setting up billing and then wonder why the SharePoint admin center still shows nothing. Configuring billing and activating Microsoft 365 Archive are two different actions. You have to explicitly turn it on.
In the Microsoft 365 admin center, go to Settings > Org settings. On the Org settings page, click Pay-as-you-go services. You'll land on the Pay-as-you-go services page, click the Settings tab at the top. Under the "Storage services" section, you'll see Archive listed.
Click on Archive to open the Microsoft 365 Archive panel. Inside the panel, find the SharePoint site archive section. You'll see a status toggle, it will be off by default. Click the toggle to turn it on. A confirmation panel called Enable SharePoint archiving will appear. Click Confirm.
That's it. Microsoft 365 Archive is now active on your tenant. You should see the toggle switch to an "On" state and receive a success notification in the admin center. From this point, SharePoint Administrators and Global Administrators can archive sites directly from the SharePoint admin center. By default, users also gain the ability to archive individual files on SharePoint sites, though file-level archive is still in preview as of the documentation date.
One important thing: if you need to enable the file-level archive preview separately, that's managed through a different control within the Archive panel. The site archive feature and the file archive feature have separate toggles, so make sure you've enabled the specific tier you need for your use case.
With Microsoft 365 Archive enabled, you're ready to move inactive SharePoint sites into cold storage. Here's how to do it correctly, and what to watch out for.
Open the SharePoint admin center (your-tenant-admin.sharepoint.com). In the left navigation, go to Sites > Active sites. Find the site you want to archive. Before you do anything else, and I really mean this, notify the site owner and any active users. Once a site is archived, it becomes completely inaccessible to everyone. Files, lists, folder structures, permissions, everything inside the site goes cold. Users who try to access it will hit a wall. An admin notification email sent 5–7 days in advance prevents a flood of support tickets.
To archive, select the site checkbox and look for the Archive option in the command bar at the top of the Active sites list. Click it and confirm the action. The site will move out of Active sites and into the archived state. When a site is archived, everything inside it is archived too, document libraries, folder structures, files, lists and list data, permissions, and all metadata. Nothing is stripped out. This is what makes Microsoft 365 Archive a genuinely lossless operation: when you bring a site back, it comes back whole.
Archived sites no longer consume your tenant's active storage quota. Instead, that storage consumption shifts to the Microsoft 365 Archive billing meter, which is billed per GB at a lower rate, that's the cost savings the feature is designed to deliver.
You can verify the archive was successful by refreshing the Active sites list and confirming the site no longer appears there. To find it, navigate to Sites > Archived sites in the SharePoint admin center.
This is the single most common specific error I hear about from Teams-heavy organizations: you try to archive a SharePoint site that's connected to a Microsoft Teams team, and you get back the error "The group connected site with channel sites associated can't be archived." This happens via the SharePoint admin center UI, and it's not a bug, it's a documented limitation that requires a workaround.
Here's what's happening: when a Teams team uses private or shared channels, each of those channels has its own associated SharePoint site. The main Teams site is a group-connected site, and it has these channel sites hanging off it. The SharePoint admin center doesn't support archiving that main site because of those dependent channel sites using unsupported site templates.
Your options, depending on what you actually need to accomplish:
Option A, Use PowerShell or the Graph API instead of the admin center UI. When you archive through PowerShell or the Microsoft Graph API, the block is different: it isn't prevented outright. Only the main site and its standard channels get archived. The private and shared channel sites remain active. You need to understand this split-archive result before proceeding, because users may still be able to reach channel-specific content even after you've archived the main site. Use PowerShell like this:
Connect-SPOService -Url https://your-tenant-admin.sharepoint.com
Set-SPOSite -Identity https://your-tenant.sharepoint.com/sites/your-site -Archived $trueOption B, Remove private and shared channels from the Teams team first. If the private/shared channels genuinely contain inactive content, work with the Teams team owner to move or delete those channels before attempting to archive the parent site through the admin center. Once those channel sites are gone, the error condition no longer applies.
Option C, Leave the site active and archive individual files instead. If file-level archive is enabled on your tenant and the site itself can't be archived due to channel constraints, you can archive specific files within the site to reduce storage consumption without touching the site architecture.
Know going in that you cannot directly archive the private or shared channel sites themselves, they use site templates that Microsoft 365 Archive doesn't support. That limitation is firm as of the current documentation.
Advanced Troubleshooting for Microsoft 365 Archive
If the step-by-step fixes above haven't resolved your issue, the following scenarios cover the deeper edge cases that show up in enterprise environments, domain-joined setups, and organizations with complex governance configurations.
File-Level Archive Preview Broken Behavior in Office Apps
If you've enabled the file-level archive preview and users are reporting that Word Online, PowerPoint Online, or SharePoint mobile apps are throwing errors or failing to load files, this is expected behavior during the preview period. The official documentation is explicit: several Microsoft 365 applications and services don't yet fully support file-level archiving. Word Online and PowerPoint Online are on that list. Teams, OneDrive, and SharePoint mobile apps are also affected. macOS OneDrive sync client users and anyone on Windows 10 or earlier will hit the same problem.
The practical fix here is user education paired with a clear reactivation path. Make sure users know how to reactivate files at their original location. In the SharePoint site, archived files will show a visual indicator, clicking that indicator or right-clicking the file should surface a "Reactivate" option. Once reactivated, the file returns to the active tier and becomes fully accessible again. One constraint to be aware of: reactivated files cannot be archived again for 30 days after reactivation.
Also worth knowing: certain file types cannot be archived at the file level at all, regardless of the application support situation. OneNote files, SharePoint pages, and SharePoint agents are on the exclusion list. And the Site Assets library on SharePoint sites doesn't support file-level archive, don't try to archive files stored there.
PowerShell Verification of Archive State
To confirm a site's archive state via PowerShell, useful in enterprise environments where you're managing dozens of sites at scale:
Connect-SPOService -Url https://your-tenant-admin.sharepoint.com
Get-SPOSite -Identity https://your-tenant.sharepoint.com/sites/your-site | Select-Object Url, ArchivedStateThe ArchivedState property will return one of several states. An active site will show no archive state. A site in the process of being archived will show a transitional state. A fully archived site will return the appropriate archived state value. This is much more reliable than relying on the admin center UI, especially when processing bulk archives across large site inventories.
Permissions Errors When Enabling Archive
If you're getting access denied errors when trying to enable Microsoft 365 Archive in the admin center, verify that the account attempting the configuration is either a SharePoint Administrator or Global Administrator. No other role has sufficient permissions for this configuration. Critically, Microsoft's own guidance recommends using the SharePoint Administrator role where possible rather than Global Admin, Global Admin is a highly privileged role that should be reserved for emergency scenarios. Check role assignments in the Microsoft 365 admin center under Users > Active users and confirm the admin account has the SharePoint Administrator role assigned.
Copilot Behavior After Archiving
One thing enterprise admins sometimes flag after enabling Microsoft 365 Archive is a change in Microsoft 365 Copilot behavior. This is actually by design: Copilot does not surface archived content in its responses. Archived sites and files are intentionally excluded from Copilot's context, which means archiving genuinely inactive content has a side benefit of improving Copilot response relevancy by keeping the active corpus clean. If a user reports that Copilot is no longer finding content they need, check whether that content has been archived and reactivate the relevant site or files.
Prevention & Best Practices for Microsoft 365 Archive
Getting Microsoft 365 Archive running is one thing. Running it well over time, without creating compliance gaps, user disruption, or unexpected billing surprises, is another. Here's how to set yourself up for long-term success with SharePoint inactive content archiving.
Build a site lifecycle policy before you start archiving anything. Microsoft 365 Archive is a tool for managing the end stage of a site's life. Without a defined policy that says "sites inactive for X months move to archive," you end up making ad-hoc decisions that are hard to audit. Establish the policy first, document it, and ideally automate it through scheduled PowerShell scripts or Power Automate flows that flag sites meeting the inactivity criteria.
Always communicate before archiving. This is the one I see skipped most often, and it's the one that generates the most helpdesk tickets. Because archived content becomes completely inaccessible to end users, site owners and users need advance notice, ideally 7–10 business days. Send a clear notification email explaining what's happening, when the archive will occur, and who to contact if they need data from the site before the archive date. Admins who skip this step spend hours fielding complaints that look like outages.
Monitor your Microsoft 365 Archive storage consumption regularly. Because Archive uses pay-as-you-go billing billed per GB, costs can grow steadily as you archive more content. Review consumption monthly in the Microsoft 365 admin center > Billing > Your products and track whether the volume of archived data aligns with your projections. If you see unexpected spikes, audit the Archived sites list in the SharePoint admin center to identify recently archived large sites.
Be especially careful with file-level archiving during the preview period. The known limitations list for file-level archive is long: Word Online, PowerPoint Online, mobile apps, macOS sync client, Windows 10 devices, older Office desktop apps. If your organization has a heterogeneous device fleet, site-level archiving is the safer, fully supported path for now. Reserve file-level archive for use cases where you fully control the client environment and can guarantee users are on up-to-date software.
- Run
Get-SPOSite -Limit ALL | Where-Object {$_.LastContentModifiedDate -lt (Get-Date).AddDays(-365)}monthly to automatically surface candidate sites for archiving, sites with no content modifications in over a year. - Add the SharePoint admin center's Archived sites view to your monthly IT admin checklist to verify archived sites are in the expected state and no inadvertent archives have occurred.
- Test the full archive-and-reactivation cycle on a non-critical site before rolling out Archive at scale, confirm that metadata, permissions, and folder structure all come back intact on reactivation.
- Keep a shared spreadsheet or wiki page documenting which sites have been archived, when, and who approved the archive, this makes compliance audit responses straightforward and fast.
Frequently Asked Questions
Why doesn't the Archive option show up in my SharePoint admin center even after I enabled it?
The most common reason is that pay-as-you-go billing hasn't been fully configured or the Archive toggle in Org settings hasn't been explicitly turned on. These are two separate steps that both have to complete successfully. Go to the Microsoft 365 admin center, navigate to Settings > Org settings > Pay-as-you-go services > Settings tab, and confirm the Archive toggle under Storage services is switched on. Also give the system 20–30 minutes after any billing changes before expecting the SharePoint admin center to reflect the new state, admin center portal propagation isn't instant. If neither of those resolves it, check that you're using a SharePoint Administrator or Global Administrator account, as other roles won't surface the Archive option.
Can I archive a SharePoint site connected to a Microsoft Teams team?
It depends on the Teams team's channel configuration. Teams that use only standard channels are fully supported for archiving through the SharePoint admin center. Teams that include private or shared channels hit a limitation: the admin center will block you with the error "The group connected site with channel sites associated can't be archived." As a workaround, you can archive the main site using PowerShell or the Graph API, but only the main site and its standard channel content gets archived; private and shared channel sites stay active. Archiving the private or shared channel sites directly isn't possible, as those sites use unsupported template types.
What happens to a site's permissions and metadata when it's archived?
Nothing is lost. Microsoft 365 Archive is a lossless operation, when a site moves to the cold storage tier, it retains all permissions, metadata, document libraries, folder structures, lists, and list data exactly as they were at the time of archiving. When the site is reactivated, everything comes back intact without any manual reconfiguration. This is one of the key advantages over older SharePoint content migration approaches where metadata often needed to be re-applied after a move. The trade-off is that the site is completely inaccessible during the archived period, no browsing, no downloads, so timing your archive carefully relative to user activity is important.
How much does Microsoft 365 Archive cost per GB?
Microsoft 365 Archive uses pay-as-you-go pricing billed per gigabyte archived, at a rate lower than the standard Microsoft 365 active storage cost. The precise per-GB rate is listed in the official Microsoft 365 Archive pricing model documentation and may vary by region and contract type, check the Pricing model page in the Microsoft 365 Archive documentation for current figures, as these can change. The key structural point is that archived content no longer counts against your tenant's license-allocated active storage quota; it shifts to a separate Archive consumption meter. For organizations with large volumes of inactive SharePoint content, this separation can produce meaningful cost savings on storage bills.
Can I archive files at the file level rather than the whole site?
Yes, but with important caveats. File-level archive is currently in preview and has a substantial list of known limitations, Word Online, PowerPoint Online, Teams mobile apps, the OneDrive mobile app, macOS sync client, Windows 10 devices, and older Office desktop apps all have known issues with archived files. File-level archiving is available only for SharePoint sites (not OneDrive), and certain file types can't be archived at all, including OneNote files, SharePoint pages, SharePoint agents, and anything in the Site Assets library. Files reactivated from archive can't be archived again for 30 days. For production use cases, site-level archiving is the more mature and fully supported path; file-level archiving is best treated as a targeted tool for specific, controlled scenarios where you know the client environment is up to date.
Does Microsoft 365 Copilot still search archived content?
No, and this is intentional. Copilot doesn't surface archived content in its responses. Microsoft 365 Archive is designed to move truly inactive content out of Copilot's active context, which actually improves response quality for active content. If you archive a site and later find that Copilot users need content from it, you'll need to reactivate the site or the specific files first. Standard end-user search, Purview Content Search, and eDiscovery do still work on archived content, though exports from archived content may take longer than exports from active content.