How to Fix Microsoft 365 Archive Setup & Errors
Why This Is Happening
Picture this: your organization has hundreds of SharePoint sites that haven't been touched in two years. Legal says you can't delete them. Finance says the active storage bill is ballooning. Someone in IT discovers Microsoft 365 Archive, gets excited, tries to enable it , and nothing works. The toggle is grayed out, or billing throws an error, or a site that should archive just… refuses. Sound familiar?
I've walked through this exact scenario with IT admins at organizations of every size. Microsoft 365 Archive is genuinely useful, it moves inactive SharePoint content into a cold storage tier at a lower cost point than active storage, while keeping all your security policies, Purview compliance features, and search indexes intact. But the setup path has several gates, and missing any one of them produces errors that are about as descriptive as "something went wrong."
Here's what's actually going on under the hood. Microsoft 365 Archive is not a feature you flip on from a standard Microsoft 365 subscription toggle. It runs on a pay-as-you-go billing model that requires an active Azure subscription linked to your tenant. If that Azure linkage isn't configured first, every attempt to enable archiving in the admin center hits a wall, and the error message rarely points you at the Azure subscription as the culprit.
The other big source of confusion is permissions. You need to be either a SharePoint Administrator or a Global Administrator to configure Microsoft 365 Archive. Global Admin is often the first role people reach for, but Microsoft's own documentation specifically recommends using the least-privileged role possible, meaning SharePoint Administrator is the right call in almost every situation. If you're logged in as a Teams Administrator or Exchange Administrator and wondering why the Archive settings panel is missing, that's your answer.
Then there's the Teams channel site problem. Organizations running Teams with private or shared channels discover a frustrating limitation: you can't archive those channel sites directly, and trying to archive the parent site through the SharePoint admin center produces an error, specifically: "The group connected site with channel sites associated can't be archived." That error message is actually one of the more helpful ones you'll encounter, but plenty of admins still don't know what it means or how to work around it.
File-level archiving (currently in preview) introduces its own layer of compatibility issues, Word Online, PowerPoint Online, Teams mobile, the OneDrive sync client on macOS, and Office desktop apps that haven't been updated since March 1, 2026 all have known issues with archived files. If your users are seeing broken file loads or strange error dialogs after you started archiving content, that's almost certainly the cause.
The short version: most Microsoft 365 Archive problems come from one of four root causes, missing Azure billing linkage, wrong admin role, unsupported site templates, or client application compatibility gaps. This guide walks through all of them. Browse all Microsoft fix guides →
The Quick Fix, Try This First
If Microsoft 365 Archive isn't showing up in your admin center, or the enable toggle does nothing when you click it, the fastest thing to check is whether pay-as-you-go billing is actually configured. This is the single most common reason O365 Archive setup fails, and it's the one Microsoft buries deepest in the UI.
Here's exactly where to look:
- Sign in to the Microsoft 365 admin center at
admin.microsoft.com. - Go to Settings > Org settings.
- Click the Pay-as-you-go services option in the list.
- Select the Settings tab, not the Overview tab. This trips people up constantly.
- Under Storage services, look for Archive. If it's grayed out or missing, your Azure subscription linkage is not set up.
If Archive appears and the toggle is off, click it, then select Archive, and confirm by selecting Confirm on the Enable SharePoint archiving panel. That's the full sequence. If the toggle is grayed out entirely, you need to complete the Azure subscription and pay-as-you-go billing setup before you go any further, jump to Step 1 below.
If the Archive toggle is already on and you're still having problems archiving specific sites, that's a different issue, most likely a site template incompatibility or a Teams channel site conflict. Those scenarios are covered in the step-by-step section.
Microsoft 365 Archive billing runs through Azure, which means before you can archive a single SharePoint site, you need an active Azure subscription tied to your tenant and a resource group to associate costs with. If your organization already has an Azure subscription in use for other services, you can use that, just make sure it's linked to the same tenant as your Microsoft 365 environment.
To create a new Azure subscription, go to portal.azure.com, sign in with your admin credentials, and navigate to Subscriptions in the left nav. Click Add and follow the wizard. Once you have a subscription, create a resource group inside it, go to Resource groups, click Create, select your subscription, name the resource group something identifiable (like M365ArchiveBilling), and choose a region close to your primary data location.
A few things that cause this step to fail silently: expired Azure free trials, subscriptions in a disabled state due to billing issues, and subscriptions that belong to a different Azure Active Directory tenant than your Microsoft 365 environment. All three produce confusing errors downstream in the Microsoft 365 admin center rather than surfacing here where the actual problem is.
Once your subscription and resource group are ready, take note of the Subscription ID, you'll need it when linking pay-as-you-go billing. If the subscription shows a status other than Active in the portal, resolve that before proceeding. A suspended or expired subscription will not work for Microsoft 365 Archive billing regardless of how the admin center is configured.
Expected result: You can see your subscription listed under Subscriptions in the Azure portal with a status of Active.
With your Azure subscription active, the next step is linking it to Microsoft 365 Archive's pay-as-you-go billing. This is done entirely in the Microsoft 365 admin center, not the Azure portal. I know that feels counterintuitive, but that's where Microsoft put it.
Navigate to admin.microsoft.com and go to Settings > Org settings > Pay-as-you-go services. Click the Settings tab and look for the option to configure your Azure subscription. You'll be prompted to select your Azure subscription and resource group from the dropdowns. Select the subscription and resource group you just created (or your existing ones).
If you don't see your Azure subscription in the dropdown, it almost always means one of two things: your admin account doesn't have an Owner or Contributor role on the Azure subscription, or the subscription is in a different tenant. Grant the appropriate role at the subscription level in the Azure portal, wait a few minutes for permissions to propagate, then refresh the Microsoft 365 admin center page and try again.
After linking billing, Microsoft 365 Archive is billed per gigabyte of archived content. The pricing applies to storage consumption beyond your license-allocated Microsoft 365 storage quota. You won't be charged for archiving data that's already within your existing quota, only the overage consumes pay-as-you-go billing. This is an important distinction when doing cost planning, because the effective price depends on your current storage footprint.
Expected result: The Pay-as-you-go services page shows your Azure subscription as linked, and the Storage services section becomes interactive rather than grayed out.
Now that billing is wired up, enabling Microsoft 365 Archive itself takes about thirty seconds, assuming you're in the right role. You must be a SharePoint Administrator or Global Administrator. If you're logged in as anything else, the Archive option simply won't appear in the panel.
In the Microsoft 365 admin center, go to Settings > Org settings > Pay-as-you-go services > Settings tab > Storage services > Archive. The Microsoft 365 Archive panel will open on the right side of the screen. Under the SharePoint site archive section, you'll see a status toggle. It should currently show as off.
Click the toggle to turn it on. A confirmation panel called Enable SharePoint archiving will appear. Click Confirm. That's it. The feature is now active at the tenant level.
At this point, you can archive sites from the SharePoint admin center. File-level archiving (preview) is a separate toggle, if you need that, see the Advanced Troubleshooting section for instructions on enabling it. Note that file-level archive is still in preview as of April 2026 and comes with a specific set of application compatibility limitations that you should communicate to users before enabling it organization-wide.
One thing admins miss: enabling Archive here doesn't archive anything automatically. It just makes the capability available. You still need to go to the SharePoint admin center and manually select which sites to archive, or use PowerShell/Graph API for bulk operations.
Expected result: The Archive toggle shows as enabled (on) in the Microsoft 365 admin center. No error messages appear. You can now access archiving controls in the SharePoint admin center.
With Microsoft 365 Archive enabled at the tenant level, you now manage the actual archiving of individual sites from the SharePoint admin center at admin.sharepoint.com. This is where you select which specific sites move into the cold storage tier.
In the SharePoint admin center, go to Sites > Active sites. Find the site you want to archive. You can use the search bar at the top to filter by site name or URL. Select the site by checking its checkbox, then look for the Archive option in the command bar at the top of the list, it may appear under a ... (more actions) menu depending on your screen resolution.
Before you archive, there's something important that the official documentation is explicit about: you need to notify site owners and end users before archiving a site. Once a site is archived, it is no longer directly accessible to anyone. All content within it, document libraries, folders, files, lists, permissions, and metadata, moves into the cold tier. End users who try to access the site won't be able to. Purview Content Search and eDiscovery still work, but standard SharePoint access does not. Don't skip the communication step.
If the Archive action is unavailable for a specific site, it's most likely a site template issue. Publishing sites, channel sites, and certain legacy site templates don't support archiving. If you see the error "The group connected site with channel sites associated can't be archived," that site has private or shared Teams channels, see Step 5 for handling this case.
Expected result: The site moves out of the Active sites list and into the archived state. The site's storage no longer counts against your active tenant quota; it counts against Microsoft 365 Archive consumption instead.
This is the step that frustrates IT admins the most, and I want to be upfront about the limitation before you spend an hour trying to work around it: if a SharePoint site is associated with a Teams team that has private or shared channels, you cannot archive the full site through the SharePoint admin center. Period. The error message you'll see is: "The group connected site with channel sites associated can't be archived."
Here's why. Private and shared channels in Teams each have their own associated SharePoint sites, called channel sites, that use site templates Microsoft 365 Archive doesn't support. When you try to archive the parent team site, the system detects these associated channel sites and blocks the operation to prevent orphaned, inaccessible channel content.
Your options depend on what you actually need:
Option A, Use PowerShell or Graph API instead of the admin center. When archiving through PowerShell or the Microsoft Graph API, the system won't block you outright. However, only the main team site and its standard channels get archived. The private and shared channel sites remain active and accessible. You're accepting a partial archive. Use this if archiving the main content is sufficient and channel site content can stay active.
# Example: Archive a site via SharePoint PnP PowerShell
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com" -Interactive
Set-PnPSite -Identity "https://yourtenant.sharepoint.com/sites/YourSite" -Archived $trueOption B, Remove private/shared channels before archiving. If the Teams team is genuinely inactive, work with the team owner to delete or migrate private and shared channels first, then archive the parent site. This is the cleanest solution but requires coordination.
Option C, Archive only the files, not the site. Using file-level archive (preview), you can archive specific files within the site without archiving the whole site. This avoids the Teams channel limitation entirely, though file-level archive has its own compatibility caveats.
Expected result: You have a documented approach for each Teams-connected site with channel conflicts, with affected site owners notified of the approach being used.
Advanced Troubleshooting
File-Level Archive Preview, Enabling It and Its Known Limitations
File-level archiving is separate from site-level archiving and requires its own opt-in. As of April 2026, it's still in preview, which means the experience is uneven across Microsoft's own applications. If users are coming to you with broken file opens, strange error dialogs when clicking files in SharePoint, or files that show as inaccessible after an archive operation, you're almost certainly hitting file-level archive compatibility issues.
The known incompatible clients as of the current documentation are significant: Word and PowerPoint Online don't handle archived files correctly, Teams and OneDrive mobile apps have issues, the OneDrive sync client on macOS fails, older Windows versions (Windows 10 and earlier) with the OneDrive sync client are affected, and any Office desktop app that hasn't received updates since March 1, 2026 is at risk. Power BI and Clipchamp fail to import archived content outright.
Before enabling file-level archive broadly, audit which client versions your users are running:
# Check Office build version via registry (run on user machines)
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" |
Select-Object VersionToReport, UpdateChannelAny build older than the equivalent of the March 2026 cumulative update should be updated before users encounter archived files. You can enforce Office update channels via Group Policy at User Configuration > Administrative Templates > Microsoft Office 2016 > Updates > Update Channel.
Reactivation and the 30-Day Re-Archive Lock
When a file is reactivated from archive status, it cannot be archived again for 30 days. This is a hard platform limit and there is no admin override. If your data lifecycle policies require more frequent archival cycles, you'll need to redesign those policies around this constraint. The 30-day window resets from the moment of reactivation, not from the original archive date.
Archived Files Moved to OneDrive, Visual State Issues
Here's a subtle one: when an archived SharePoint file is moved or copied to OneDrive, it retains its archived state, but that archived state might not be visually represented in the OneDrive user interface. The file is still technically archived, still requires reactivation to access fully, but the OneDrive UI won't show the archive indicator. This leads to confusing situations where users try to open a file in OneDrive that looks completely normal but behaves like it's missing. The fix is to reactivate the file at its original SharePoint location before moving it, not after.
Storage Quota Accounting
One thing admins sometimes get wrong in cost planning: archived content does not count against your tenant's active Microsoft 365 storage quota. It goes into a separate Microsoft 365 Archive storage consumption bucket billed at the pay-as-you-go rate. However, if you reactivate a site, all that content immediately moves back into your active quota. If your active quota is already near its limit, reactivating a large archived site can push you over and cause service degradation. Plan reactivations carefully and check your active storage headroom first.
Copilot and Archived Content
This is an advantage that's easy to overlook: Copilot is not trained on archived content. If your organization has compliance concerns about proprietary or sensitive content influencing Copilot responses, archiving that content is an effective control. This is documented behavior, not an assumption.
Prevention & Best Practices
Getting Microsoft 365 Archive working is one thing. Keeping it working reliably, and avoiding the common traps that cause surprise costs or compliance gaps, is a different discipline entirely.
The single biggest preventable mistake I see is admins archiving sites without notifying users. The documentation is explicit about this, and it's not just a courtesy: when a site is archived, it becomes inaccessible to everyone, including the site owner. If a business-critical process silently depends on a file in that site, archiving it will break that process with no warning. Build a communication template and a notification workflow into your archive procedures before you archive a single site in production.
Plan your archive strategy around site activity data, not assumptions. The SharePoint admin center shows you last activity dates for sites, use that data. Sites with no activity in 18+ months are strong candidates for archiving. Sites with low traffic but regular access patterns (monthly reporting sites, for example) need more careful evaluation before archiving.
For organizations with large-scale archiving needs, PowerShell and the Microsoft Graph API are your friends. The admin center UI is fine for one-off operations but becomes unmanageable at scale. Build a script that pulls inactive sites from the SharePoint admin center report, filters by last activity date, notifies owners via email, and queues sites for archiving after a defined waiting period. That workflow prevents most emergency reactivation requests.
Keep your Office clients current. With file-level archive in preview and the March 2026 cutoff for desktop app support, stale Office installs are an active risk. If your organization manages Office updates through Windows Update for Business or WSUS, verify that the OfficeC2R update channel policy is delivering monthly updates to all endpoints, especially machines that are rarely used and therefore rarely patched.
- Run the SharePoint site activity report monthly and flag sites with zero access in the past 180 days as archive candidates.
- Create a standard email template for notifying site owners 30 days before archiving, include the reactivation process so they know how to get content back.
- Before enabling file-level archive for end users, enforce an Office update policy that ensures all desktop apps are past the March 2026 build cutoff.
- Document which Teams-connected sites have private or shared channels and decide your archive approach for each before you start bulk archiving operations, discovering the block mid-run is avoidable.
Frequently Asked Questions
Why can't I see the Archive option in the SharePoint admin center even though it's enabled in Org settings?
The most common cause is that you're not signed in with an account that has the SharePoint Administrator or Global Administrator role. Even if you enabled Archive in the Microsoft 365 admin center with Global Admin permissions, trying to use it from the SharePoint admin center with a lesser role (like Teams Admin or Exchange Admin) will hide the Archive option entirely. Verify your role assignment in the Microsoft 365 admin center under Users > Active users > [your account] > Roles. Also double-check that the toggle in Org settings > Pay-as-you-go services > Settings > Storage services > Archive is actually switched on, it's easy to navigate away before confirming.
How much does Microsoft 365 Archive actually cost per month?
Microsoft 365 Archive uses a pay-as-you-go model billed per gigabyte of archived storage, but importantly, you only pay the archive rate for storage that exceeds your license-allocated Microsoft 365 storage quota. If your tenant's total storage footprint is still within the quota included with your licenses, archiving doesn't cost anything extra; the archived content simply shifts from one accounting bucket to another within your quota. Costs kick in when archived content pushes you beyond that quota ceiling. For current per-GB pricing, check the official Microsoft 365 Archive pricing page as rates are subject to change and vary by region.
Can archived SharePoint sites still be searched in eDiscovery?
Yes, this is one of the key advantages of Microsoft 365 Archive over other cold storage approaches. Full content search works for Purview Content Search, standard end-user search, and eDiscovery search experiences even when a site is in the archived state. The difference is in export: Purview Content Search and eDiscovery can still export archived content directly, but export operations may take longer compared to active content. Compliance holds and retention policies applied to content before archiving remain in effect after archiving. The cold tier doesn't break compliance, that's the whole point.
What happens to permissions and metadata when a site is archived and then reactivated?
Nothing is lost. Microsoft 365 Archive is designed as lossless, when a site is reactivated, it comes back with all original permissions, metadata, folder structures, list data, and file versions exactly as they were at the time of archiving. No data is deleted or degraded during the archive or reactivation process. This is a meaningful difference from older archiving approaches that sometimes stripped metadata or flattened folder structures. The reactivation process also restores the site to the active storage quota, so make sure you have headroom in your active quota before reactivating large sites.
My users are getting errors opening files after I enabled file-level archive, what's happening?
File-level archive (currently in preview) has known compatibility gaps with several Microsoft applications. Word Online and PowerPoint Online don't correctly handle archived files, Teams and OneDrive mobile apps have issues, the OneDrive sync client on macOS fails, and Office desktop apps that haven't been updated since March 1, 2026 will produce errors. If your users are hitting these errors, the immediate fix is to reactivate the affected files at their original SharePoint location, users can do this themselves if they have the right permissions, or an admin can do it from the SharePoint admin center. Longer term, update all Office desktop clients and evaluate whether file-level archive is appropriate for your environment until the preview matures.
Can I archive a Teams-connected SharePoint site that has private channels?
Not through the SharePoint admin center, you'll get the error "The group connected site with channel sites associated can't be archived." However, you can archive it through PowerShell or the Microsoft Graph API, with the understanding that only the main team site and its standard channels will be archived. Private and shared channel sites remain active and cannot be directly archived because they use site templates that Microsoft 365 Archive doesn't support. If you need the full site, including all channel content, in a cold storage tier, your options are to remove the private/shared channels before archiving, or to work with the file-level archive feature to archive specific files within those channel sites rather than archiving the sites themselves.