Fix Microsoft 365 Archive Setup & Configuration Errors
Why This Is Happening
You've got terabytes of old SharePoint content sitting in your tenant , project sites from three years ago, compliance archives, decommissioned department portals , and someone in finance just asked why the storage bill is so high. You go to set up Microsoft 365 Archive to move that dead weight into cold storage, and nothing works the way the admin center implies it will. The toggle is greyed out. The archive option doesn't appear on a site. A site throws a cryptic error about "channel sites." Sound familiar?
I've seen this exact situation on dozens of tenant configurations. The frustration is real, especially when it's blocking a cost-reduction initiative someone upstairs is watching closely.
Microsoft 365 Archive is a pay-as-you-go cold storage tier built directly inside SharePoint. When a site or file gets archived, it leaves your tenant's active storage quota entirely and moves into a separate Archive storage pool billed at a lower per-GB rate. That's the core value: retain inactive data long-term without paying active storage prices for it. Archived content still shows up in Purview Content Search, eDiscovery, and end-user search, it just isn't directly accessible without a reactivation step.
The reason most Microsoft 365 Archive problems happen comes down to three root causes. First, the billing prerequisite: Archive is a pay-as-you-go service, which means it requires a linked Azure subscription before a single toggle appears in the admin center. Skip that step and the entire feature looks broken. Second, site template incompatibilities: not every SharePoint site type can be archived. Publishing sites, certain legacy templates, and sites associated with Teams that include private or shared channels all hit walls that return confusing error messages. Third, permissions: you must be a SharePoint Administrator or Global Administrator, not just a site owner or Teams admin, to manage archiving. A lot of "it doesn't work" tickets I've seen are actually permission gaps wearing a mask.
The file-level archive feature (currently in preview) adds another layer of complexity. Several major Microsoft 365 apps, Word and PowerPoint Online, SharePoint and OneDrive mobile apps, macOS OneDrive sync clients, and older Office desktop versions that haven't updated since March 1, 2026, don't yet fully support archived files. Users hit weird error messages when they try to open something, and nobody told them why. That's a communication and configuration problem as much as a technical one.
This guide walks you through every fix, in order of likelihood. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you spend an hour digging through admin centers, check these two things. They account for the majority of Microsoft 365 Archive setup failures I see.
1. Verify your Azure subscription is linked for pay-as-you-go billing. Open the Microsoft 365 admin center at admin.microsoft.com. Go to Billing > Your products and look for any active Azure subscription linked to the tenant. If there's nothing there, or if you see a subscription in a suspended or disabled state, that is your problem. Archive will not activate without it. You need a live Azure subscription with an associated resource group.
2. Confirm you're hitting the right toggle in the right admin center. This trips people up constantly. You enable Microsoft 365 Archive in the Microsoft 365 admin center (admin.microsoft.com), but you manage individual site archiving in the SharePoint admin center (your-tenant-admin.sharepoint.com). These are two different portals. Enabling billing in one and then looking for archive options in the wrong portal leads to a lot of "I can't find it" support tickets.
If you've confirmed both of those and it still isn't working, read on, the step-by-step section covers every scenario in depth.
One more fast check: if you're trying to archive a site and you see the error "The group connected site with channel sites associated can't be archived" via the SharePoint admin center, that's actually expected behavior. It's not a bug. Teams sites that have private or shared channels attached to them can't be archived through the admin center UI at all. I'll cover the workaround in the advanced section.
Microsoft 365 Archive runs on a pay-as-you-go billing model tethered to Azure. There's no way around this step, it's not optional fine print, it's the foundation the entire feature sits on. If your organization already has an Azure subscription, you may be able to skip most of this and jump to linking it in the M365 admin center. But if you don't have one, here's what to do.
Go to portal.azure.com and sign in with your Global Administrator account. In the left navigation, select Subscriptions, then click + Add. Choose a billing plan, most enterprise tenants select Microsoft Customer Agreement or Pay-As-You-Go. Complete the billing profile setup.
Once your subscription exists, you need a resource group. In the Azure portal, go to Resource groups and click + Create. Give it a meaningful name like M365-Archive-RG, select your subscription, choose a region geographically close to your Microsoft 365 tenant's data residency region, and click Review + Create, then Create.
Note the exact subscription ID and resource group name, you'll need both in the next step. If you're in an enterprise with separate Azure and M365 billing contacts, loop in the Azure subscription owner before proceeding. Mismatched billing contacts are a common reason this step stalls for days.
When it's done, you should see your new subscription listed under Subscriptions in the Azure portal with a status of Active. That's your green light to move on.
This is the step that unlocks the Archive toggle. Open the Microsoft 365 admin center at admin.microsoft.com and sign in as a SharePoint Administrator or Global Administrator. Remember what I said earlier, use the least-privileged role that gets the job done. If you have a SharePoint Administrator account, use that. Reserve your Global Admin for emergencies.
In the left navigation pane, go to Settings > Org settings. On the Org settings page, select the Pay-as-you-go services option. You'll land on a page with a Settings tab, click that tab.
Under the Billing section, you'll be prompted to link your Azure subscription. Select your Azure subscription from the dropdown, then select the resource group you created in Step 1. Click Save.
If your Azure subscription doesn't appear in the dropdown, it usually means one of two things: the account you're logged in with doesn't have owner or contributor access to that Azure subscription, or the subscription is in a different Azure Active Directory (Entra ID) tenant than your Microsoft 365 tenant. Both are fixable, you need to either grant the correct Azure RBAC role to your admin account, or confirm you're working within the same Entra ID directory.
A successful save here should immediately make the Archive toggle visible in the next step. If the page still shows no pay-as-you-go options after saving, try a hard browser refresh (Ctrl+Shift+R), the admin center sometimes caches aggressively.
With pay-as-you-go billing configured, you can now actually turn on Microsoft 365 Archive. Stay in the Microsoft 365 admin center. Navigate back to Settings > Org settings > Pay-as-you-go services and click the Settings tab again.
Look for the Storage services section. You should see an Archive option listed there. Click it to open the Microsoft 365 Archive side panel.
Inside that panel, you'll see a SharePoint site archive section with a status toggle. Flip that toggle to On. A confirmation panel will appear, click Confirm to finalize.
That's it. Microsoft 365 Archive is now active at the tenant level. What this means: SharePoint Administrators can now archive sites from the SharePoint admin center, and by default, users can archive individual files on SharePoint sites (the file-level archive feature). If you don't want users to have that file-level archive ability yet, given that it's still in preview and has known limitations, you can manage that separately. I'll cover that in the advanced section.
If the Archive option doesn't appear under Storage services even after completing Step 2, double-check that your Azure subscription status is Active and not Disabled or Past Due. A subscription with billing issues will silently break this entire flow.
Now you're working in a different portal. Open the SharePoint admin center, the URL is https://[your-tenant]-admin.sharepoint.com. Sign in as SharePoint Administrator or Global Administrator.
In the left navigation, go to Sites > Active sites. Find the site you want to archive. You can use the search bar at the top of the sites list to filter by URL or site name. Click the site name to select it, don't click directly through to it.
In the right-hand panel that appears, or in the top command bar, look for the Archive option. Select it. You'll see a confirmation dialog explaining what archiving does, content becomes inaccessible, it moves out of active storage, full search still works. Confirm the action.
Archiving is fast, Microsoft designed it for sites of any size. The site moves to Archived status almost immediately regardless of how many gigabytes it contains. You can verify this by going to Sites > Archived sites in the SharePoint admin center, where the newly archived site should appear.
What gets archived: everything. Document libraries, folder structures, all files, lists and list data, permissions, and all metadata. When a site is eventually reactivated, all of that metadata and permission structure comes back intact, nothing is lost. That "lossless metadata" behavior is one of the genuine strengths of this approach versus just exporting content to a blob storage account.
Important: if a site doesn't show an archive option, confirm it isn't one of the unsupported site types: publishing sites, channel sites (private or shared Teams channels), or certain legacy site template types. The next card covers those edge cases.
Archiving is reversible, that's by design. When a user or admin needs access to archived content, reactivation is the path. Here's how it works for both sites and files.
For sites: Go to the SharePoint admin center, then Sites > Archived sites. Find the site, select it, and click Reactivate in the command bar or side panel. The site will move back to active status. All metadata, permissions, and content return exactly as they were. The reactivation itself is fast for the site shell, though very large document libraries may take some additional time to fully surface in search indexes again.
For individual files (preview feature): If a user encounters an archived file and needs access, they can reactivate it directly from SharePoint. When they try to open an archived file, they'll see a message indicating the file is archived with an option to reactivate it. They click that option, confirm, and the file returns to its active state at its original location. As an admin, you can also do this from the SharePoint admin center.
One restriction to know: after a file is reactivated, it cannot be archived again for 30 days. This is a hard platform limit, plan around it if you're doing cyclical archiving workflows. Also, if you copy or move an archived file to a new location, it keeps its archived state in SharePoint. However, if you move it into OneDrive, the archived indicator might not display correctly in the OneDrive UI, even though the file is technically still archived. This is a known preview-period quirk.
After reactivating a site, you should see it back under Sites > Active sites in the SharePoint admin center. A site that fails to reactivate typically has an underlying permission or subscription billing issue, check that your Azure pay-as-you-go billing is still active and in good standing.
Advanced Troubleshooting
Teams Sites with Private or Shared Channels
This is the most common "unexplained failure" scenario I see in enterprise environments. When you try to archive a site that's associated with a Microsoft Teams group that has private or shared channel sites attached, the SharePoint admin center will block you with the error: "The group connected site with channel sites associated can't be archived."
This is not a bug, it's documented behavior. The admin center UI explicitly cannot archive these sites. Your options via the admin center are zero. However, if you use PowerShell or the Microsoft Graph API, the block is not enforced the same way. The main team site and its standard channels will archive, but the private and shared channel sites remain active. You also can't directly archive the channel sites themselves since they use unsupported site templates.
The practical workaround is to disassociate private and shared channels before archiving, archive the main site, then re-evaluate the channel sites separately. Use the Teams admin center or PowerShell to identify all channel sites associated with the Team before you begin.
Disabling File-Level Archive for End Users
By default, when you enable Microsoft 365 Archive, users get the ability to archive individual files on SharePoint sites. Given that file-level archive is still in preview and has real limitations, it breaks Word and PowerPoint Online, it doesn't work on SharePoint mobile, it misbehaves on macOS OneDrive clients, and it fails entirely on Office desktop apps that haven't updated since March 1, 2026, you may want to turn off user-facing file archive until the feature matures.
Go to the Microsoft 365 admin center, Settings > Org settings > Pay-as-you-go services > Settings > Archive. In the Microsoft 365 Archive panel, there is a separate toggle for file-level archive (the preview feature). You can disable it there while keeping site-level archive fully active. This is the right call for most organizations right now.
PowerShell for Bulk Archive Operations
For archiving multiple sites at scale, the SharePoint admin center UI gets painful fast. Use the SharePoint Online PowerShell module instead:
# Install the module if needed
Install-Module -Name Microsoft.Online.SharePoint.PowerShell -Force
# Connect to SharePoint Online
Connect-SPOService -Url https://[your-tenant]-admin.sharepoint.com
# Archive a specific site
Set-SPOSite -Identity https://[your-tenant].sharepoint.com/sites/[sitename] -Archive $true
# Reactivate an archived site
Set-SPOSite -Identity https://[your-tenant].sharepoint.com/sites/[sitename] -Archive $false
# List all archived sites
Get-SPOSite -Filter "ArchiveStatus -eq 'Archived'"
Running Get-SPOSite with the archive filter gives you a clean export of everything currently in cold storage. Pipe it to Export-Csv for audit records. This is genuinely useful for compliance teams that need documentation of what's archived and when.
Verifying Archive Status in Purview
If you're using Microsoft Purview for compliance workflows, archived content is still fully searchable through Purview Content Search and eDiscovery. The search behavior is identical to active content, but exports from archived content may take noticeably longer than exports from active sites. Build that into any eDiscovery response SLAs you have in place. Plan for additional export time on large archived sites rather than assuming standard eDiscovery turnaround.
Checking Event Logs and Audit Activity
Archive and reactivation events are logged in the Microsoft 365 Unified Audit Log. To view them, go to Microsoft Purview compliance portal > Audit. Filter by Activity: Archived site or Activity: Reactivated site. This is your paper trail for showing auditors exactly when sites were archived and by whom.
Prevention & Best Practices
Getting Microsoft 365 Archive set up correctly is one thing. Running it well over time, especially in a large enterprise tenant with hundreds or thousands of SharePoint sites, is a different skill. Here's what separates the teams that have smooth archiving operations from the ones that generate constant helpdesk noise.
Establish a site lifecycle policy before you archive anything. Decide upfront: what makes a site a candidate for archiving? Common criteria include "no activity for 12 months" or "project closed for 6 months." Document this policy, get sign-off from stakeholders, and stick to it. Ad-hoc archiving based on one-off requests creates confusion about what's accessible and what isn't.
Always notify site owners and end users before archiving. Microsoft's own documentation calls this out, and for good reason. The moment a site is archived, nobody can access it, including the site owner. No warning means users hitting dead links, broken workflows, and a support ticket flood. Give at least 48-72 hours notice. Include in your notification email: what archiving means, how long it'll stay archived, and who to contact if they need access restored urgently.
Keep your Azure subscription billing healthy. Microsoft 365 Archive is directly dependent on your Azure pay-as-you-go billing being active. If the subscription lapses, gets suspended for non-payment, or gets accidentally deleted, archive management breaks. Set up billing alerts in the Azure portal for your Archive-linked subscription so you're not caught off guard.
Hold off on file-level archive for general users until the preview matures. As of April 2026, file-level archive has significant gaps: it doesn't work correctly in Word and PowerPoint Online, SharePoint mobile apps, macOS OneDrive sync clients, or older Office desktop versions. Deploy it to a pilot group first, gather feedback, and expand gradually. Turning it on org-wide immediately is a recipe for confused users and unexplained file-open errors.
Use PowerShell for audit exports quarterly. Run Get-SPOSite -Filter "ArchiveStatus -eq 'Archived'" and export the results to a CSV. This gives you a clean record for compliance and helps you catch any sites that have been in cold storage long enough that the business may want to permanently delete them, freeing up Archive storage costs too.
- Link your Azure subscription to M365 billing before your storage overage charges hit, proactive setup saves money and rush-troubleshooting headaches.
- Create a dedicated "Archive Notification" email template now so communication is instant when a site needs to go cold.
- Disable file-level archive for end users via the M365 admin center until the preview feature gap list (Word Online, mobile apps, macOS) clears up.
- Set Azure billing alerts on your Archive-linked subscription at 80% of your expected monthly Archive spend so you never get a surprise bill.
Frequently Asked Questions
What happens to my archived SharePoint site content, can anyone still access it?
When a site is archived, it moves into a cold storage tier and is no longer directly accessible to anyone, including site owners and administrators. That's the key distinction, no one can browse or open the content while it's archived. However, the content is still fully indexed, so Microsoft Purview Content Search, end-user keyword search, and eDiscovery searches will surface it in results. Purview can also directly export archived content for compliance or legal hold purposes, though exports from archived sites typically take longer than exports from active ones. To actually open files or interact with the site, an admin needs to reactivate it first.
Why can't I see the Archive option in the SharePoint admin center even after enabling it?
The most common reason is that the specific site you're trying to archive uses an unsupported site template. Publishing sites, classic team sites with certain legacy templates, and sites associated with Teams groups that have private or shared channel sites attached are all excluded from the admin center archive UI. Check the site template by going to the site settings URL: https://[your-tenant].sharepoint.com/sites/[sitename]/_layouts/15/prjsetng.aspx. If the site falls into a supported category and the option still doesn't appear, confirm your pay-as-you-go billing is correctly linked and that your admin account has SharePoint Administrator or Global Administrator rights, not just site collection admin.
How much does Microsoft 365 Archive actually cost? Is it cheaper than regular SharePoint storage?
Microsoft 365 Archive follows a pay-as-you-go billing model billed in gigabytes consumed within the Archive storage tier, and the per-GB cost is lower than the cost of storage consumption beyond your license-allocated Microsoft 365 storage quota. The exact current pricing is published on Microsoft's official pricing page and can vary by region and agreement type, so I'd always recommend checking there for up-to-date figures rather than relying on a number in any article. The billing runs through your linked Azure subscription, so the charges appear on your Azure invoice rather than your Microsoft 365 billing directly. Factor in that archived content doesn't count against your active tenant storage quota, which is where the real savings accumulate at scale.
My users are getting errors trying to open files that were archived, how do I fix it?
This is the file-level archive preview limitation hitting your users. As of April 2026, archived files fail to open or display incorrect errors in Word Online, PowerPoint Online, SharePoint and OneDrive mobile apps, macOS OneDrive sync clients, and older Office desktop apps that haven't updated since March 1, 2026. The fix is to reactivate the file, users can do this themselves in SharePoint by clicking the reactivation prompt when they hit the error, or you can do it from the SharePoint admin center. If this is happening to many users, the right longer-term fix is to disable file-level archive for your organization in M365 admin center under Settings > Org settings > Pay-as-you-go services > Archive until client support for the feature matures.
Can I archive a Microsoft Teams site using Microsoft 365 Archive?
It depends on the Teams configuration. Teams sites that use only standard channels are fully supported for archiving, you archive the underlying SharePoint site the same way you would any other site. The complication comes with Teams that include private or shared channels. Via the SharePoint admin center UI, you cannot archive a group-connected site that has channel sites associated with it, you'll hit the error "The group connected site with channel sites associated can't be archived." Via PowerShell or the Graph API, the block isn't enforced the same way, but only the main Team site archives; the private and shared channel sites stay active and can't be archived directly since they use unsupported templates. Archiving the Teams team itself through the Microsoft Teams admin center is a separate action and doesn't directly invoke Microsoft 365 Archive.
I reactivated an archived site but now I can't archive it again, why?
This affects files specifically rather than sites: once a file is reactivated from an archived state, the platform enforces a 30-day waiting period before it can be archived again. This is a hard limit built into Microsoft 365 Archive and not something that can be overridden through admin settings or PowerShell. For full sites, this 30-day restriction doesn't apply in the same way, you can archive a site again after reactivating it without waiting 30 days. If you're building automated archive workflows around files, make sure your logic accounts for the reactivation window. Attempting to archive a file within that 30-day window will fail silently or with a generic error, which is genuinely confusing if you don't know this restriction exists.