Microsoft 365 Archive Not Working: Fix Setup & Config Errors
Why Microsoft 365 Archive Setup Keeps Failing
I've seen this exact scenario play out dozens of times. A SharePoint admin gets tasked with cleaning up aging, inactive sites , maybe you've got hundreds of SharePoint sites from projects that wrapped up two years ago, or a compliance team breathing down your neck about long-term data retention. So you head to the Microsoft 365 admin center to turn on Microsoft 365 Archive, and... nothing works the way you expect. The toggle isn't there, the archiving option is greyed out, or you try to archive a site and hit a cryptic error like "The group connected site with channel sites associated can't be archived."
Microsoft's error messages in this area are genuinely unhelpful. They often don't tell you why the operation failed, just that it did. And the Microsoft 365 Archive feature itself has a few prerequisites that aren't obvious at all , especially the Azure subscription requirement, which trips up admins who assume it's just a standard Microsoft 365 toggle.
Here's the core issue: Microsoft 365 Archive is not a standard subscription feature you flip on from the Microsoft 365 admin center alone. It operates on a pay-as-you-go billing model tied directly to an Azure subscription and resource group. If that Azure linkage isn't in place first, the Archive feature simply won't activate, and the admin center won't always make that clear.
Beyond the billing prerequisite, there's a whole landscape of site-type limitations that catch people off guard. Teams-connected sites with private or shared channels have partial support at best. Publishing sites, channel sites, and several legacy SharePoint site template types can't be archived at all through Microsoft 365 Archive. File-level archiving, still in preview as of early 2026, has its own separate set of application compatibility issues across Word Online, PowerPoint Online, mobile apps, and older desktop Office versions.
Who hits these problems most often? In my experience, it's mid-to-large enterprise IT teams managing Microsoft 365 at scale, compliance officers trying to move cold data out of the active storage quota, and SharePoint admins who inherited an environment with hundreds of legacy sites. If any of that sounds like you, you're in the right place. Browse all Microsoft fix guides →
The good news: every single one of these Microsoft 365 Archive problems has a specific fix. Let's walk through them in order, starting with the fastest resolution first.
The Quick Fix, Try This First
Before you go digging into site templates and PowerShell, check this first. The single most common reason Microsoft 365 Archive is unavailable or non-functional is a missing or unconfigured Azure pay-as-you-go billing link. This one prerequisite blocks everything downstream.
Here's the fast path to verify and fix it:
- Sign into the Microsoft 365 admin center at
admin.microsoft.comwith a SharePoint Administrator or Global Administrator account. - Go to Settings > Org settings.
- On the Org settings page, select Pay-as-you-go services.
- Look at the Settings tab. If you see a message prompting you to configure billing or link an Azure subscription, that's your problem right there.
- Follow the prompts to link an Azure subscription and resource group. If you don't have one, you'll need to create it in the Azure portal first, go to
portal.azure.com, create a new subscription, and set up a resource group in the appropriate region for your tenant. - Once billing is configured, go back to Pay-as-you-go services > Settings tab > Storage services, and select Archive.
- On the Microsoft 365 Archive panel, toggle SharePoint site archive to On.
- On the confirmation panel, select Confirm.
After confirming, you should be able to navigate to the SharePoint admin center and start archiving sites. If the option is still missing or greyed out after these steps, your account likely lacks the necessary permissions, continue to the step-by-step section.
admin.microsoft.com). Once Archive is enabled, the day-to-day management of archiving actual sites happens in the SharePoint admin center ([yourtenant]-admin.sharepoint.com). Getting them confused is the second most common reason admins think the feature "isn't working."
Microsoft 365 Archive setup is locked behind specific admin roles. You need to be either a SharePoint Administrator or a Global Administrator to configure it. No other role, not even a Teams Administrator or Exchange Administrator, will get you access to the Archive settings panel.
To check your current role assignment:
# In the Microsoft 365 admin center
# Navigate to: Users > Active users > [your account] > Roles tab
# Confirm you see "SharePoint Administrator" or "Global Administrator" listedAlternatively, run this in PowerShell (requires the Microsoft Graph PowerShell module):
Connect-MgGraph -Scopes "RoleManagement.Read.Directory"
Get-MgRoleManagementDirectoryRoleAssignment -Filter "principalId eq '[YOUR_USER_OBJECT_ID]'" | Select-Object -ExpandProperty RoleDefinitionIdA note on role selection that Microsoft is explicit about: they recommend using the SharePoint Administrator role rather than Global Administrator whenever possible. Global Admin is a massively privileged role, it should be reserved for genuine emergencies where a lower-privilege role won't work. For routine Microsoft 365 Archive management, SharePoint Admin is the right call. If you're asking your Global Admin to do this work, consider whether assigning the SharePoint Admin role to a dedicated admin account makes more sense for your org.
If your account shows the correct role and you still can't access Archive settings, there may be a role propagation delay. Wait 15–30 minutes after a role assignment before retrying, as Azure AD role changes aren't always instant.
What success looks like: After confirming your role, navigating to Microsoft 365 admin center > Settings > Org settings > Pay-as-you-go services should show an active Settings tab rather than a locked or empty panel.
This step is where most enterprise admins get stuck, especially if your organization's Azure and Microsoft 365 subscriptions are managed by different teams. Microsoft 365 Archive bills based on the number of gigabytes archived beyond your license-allocated storage quota, so it needs an active Azure subscription with billing configured.
Here's how to set it up from scratch if you don't have it yet:
- Go to
portal.azure.comand sign in with your admin account. - In the search bar, type Subscriptions and select it.
- Click + Add and follow the prompts to create a new Azure subscription (or select an existing one if your org already has one you can use).
- Create a Resource Group within that subscription, this is the logical container Azure uses for billing and resource management. Name it something clear like
M365Archive-RG. - Back in the Microsoft 365 admin center, go to Settings > Org settings > Pay-as-you-go services.
- Select Configure pay-as-you-go billing and follow the wizard to link your newly created Azure subscription and resource group.
# Verify billing link status via PowerShell (SharePoint PnP module required)
Connect-PnPOnline -Url "https://[yourtenant]-admin.sharepoint.com" -Interactive
Get-PnPTenantInstanceOne thing I always tell admins: loop in your Azure billing owner or finance team before doing this. Microsoft 365 Archive is pay-as-you-go, meaning the charges accumulate based on how much data you archive beyond your included quota. Archiving 10 TB of cold SharePoint data will show up on your Azure bill. Get budget approval first, don't surprise the CFO.
What success looks like: After linking billing, the Pay-as-you-go services panel in the Microsoft 365 admin center will show an active status with your linked Azure subscription name visible.
Once pay-as-you-go billing is wired up, activating Microsoft 365 Archive itself is straightforward, but the exact navigation path matters, and it's easy to miss a step if you're clicking around.
Follow this exact path:
- Sign into
admin.microsoft.com. - In the left navigation, go to Settings > Org settings.
- On the Org settings page, find and click Pay-as-you-go services.
- On the Pay-as-you-go services page, click the Settings tab (not the Overview tab, this is a common miss).
- Under the Storage services section, click Archive.
- In the Microsoft 365 Archive panel that opens on the right side, locate the SharePoint site archive section and click the status toggle to turn it On.
- An Enable SharePoint archiving confirmation panel will appear. Read it, then click Confirm.
If you also want to enable file-level archive (currently in preview), there's a separate toggle for that. File-level archiving lets you archive individual files rather than entire sites, useful for targeted cold storage. However, be aware that this preview feature has significant application compatibility limitations with Word Online, PowerPoint Online, mobile apps, and Office desktop versions older than March 1, 2026. Don't enable file-level archive for end users without a clear communication plan in place.
# You can also enable Archive via PowerShell
# Requires SharePoint Online Management Shell
Import-Module Microsoft.Online.SharePoint.PowerShell
Connect-SPOService -Url "https://[yourtenant]-admin.sharepoint.com"
# Check archive status
Get-SPOTenant | Select-Object IsArchivingEnabledWhat success looks like: After confirming, the toggle on the Microsoft 365 Archive panel should display as enabled (blue/on). You'll also now see archive management options appear in the SharePoint admin center under Sites > Active sites.
With Archive enabled, you're ready to move sites to cold storage. But this is where the site-template limitations hit, and where a lot of admins encounter their first real error message.
To archive a site from the SharePoint admin center:
- Go to your SharePoint admin center:
[yourtenant]-admin.sharepoint.com. - Navigate to Sites > Active sites.
- Select the checkbox next to the site you want to archive.
- In the command bar at the top, click Archive.
- Confirm the action in the dialog that appears.
When it works, the site moves out of Active sites and its content, document libraries, folder structures, files, lists, list data, permissions, and all metadata, moves into the cold storage tier. It stops counting against your tenant's active storage quota immediately.
Here are the error messages you'll encounter and what they mean:
"The group connected site with channel sites associated can't be archived."
This means the Teams site you're trying to archive has private or shared channels attached to it. The SharePoint admin center cannot archive these. Your only workaround through the admin center is to archive standard-channel-only Teams sites. If you need to archive via PowerShell or Graph API, only the main site gets archived, the private and shared channel sites stay active, and you cannot archive the channel sites directly because they use unsupported templates.
Site type not available for archiving:
Publishing sites, channel sites, and several legacy SharePoint site templates are not supported by Microsoft 365 Archive at all. If you hit this, the site simply cannot be archived with this feature, you'll need an alternative retention strategy for that content.
# Archive a site via PowerShell
Set-SPOSiteArchiveState -Identity "https://[yourtenant].sharepoint.com/sites/[sitename]" -ArchiveState ArchivedWhat success looks like: The site disappears from Active sites and appears in the Archived sites view in the SharePoint admin center. Its storage no longer counts against your active quota.
Reactivation is the operation that catches admins by surprise, especially under time pressure, when a legal hold or business need requires access to something that's been archived. The process is straightforward, but there are timing and recurrence rules you need to know about upfront.
To reactivate an archived site:
- In the SharePoint admin center, navigate to Sites > Archived sites.
- Select the site you want to reactivate.
- Click Reactivate in the command bar.
- Confirm the action.
When a site is reactivated, Microsoft 365 Archive guarantees lossless metadata, the site comes back with all of its original metadata, permissions, folder structures, and content exactly as it was archived. Nothing is stripped or altered during the cold storage period.
For file-level reactivation (preview feature), end users can reactivate individual archived files directly at their original location. This is important context to communicate to your users, if they try to open an archived file and get an error, they need to reactivate it first before it'll open normally in Word, Excel, or any other app.
The critical rule to know: files that are reactivated cannot be archived again for 30 days. This is a hard platform limitation. If you reactivate a file or go through a reactivation cycle, plan accordingly, you won't be able to push it back to cold storage for a month.
# Reactivate an archived site via PowerShell
Set-SPOSiteArchiveState -Identity "https://[yourtenant].sharepoint.com/sites/[sitename]" -ArchiveState ActiveAlso worth knowing: Purview Content Search and eDiscovery can still access and export content from archived sites without reactivating. The export just takes longer than it would for active content. So for compliance and legal hold scenarios, you don't always need to reactivate, you can export directly.
What success looks like: The site moves from Archived sites back to Active sites in the SharePoint admin center, and all content is accessible to site owners and members again.
Advanced Troubleshooting for Microsoft 365 Archive
If the standard steps above haven't resolved your issue, we need to go deeper. These scenarios come up most often in enterprise environments with complex tenant configurations, hybrid setups, or large-scale archiving operations.
Microsoft 365 Archive Not Showing in Pay-As-You-Go Services
If the Archive option simply isn't visible under Storage services in Pay-as-you-go services, it typically means your pay-as-you-go billing configuration is incomplete or the tenant provisioning is still in progress. Try signing out of the admin center completely, clearing browser cache, and signing back in. Tenant-side provisioning after billing link setup can take up to 24 hours in some cases.
Also confirm that you're not using a Microsoft 365 Education tenant, the Education offering has different terms and pricing for Microsoft 365 Archive, and setup steps may differ.
PowerShell: Graph API Archiving Behavior for Teams Sites
If you're archiving Teams-connected sites at scale using PowerShell or the Microsoft Graph API, understand this clearly: archiving a site with private or shared channel sites isn't blocked by the API. It silently succeeds, but only the main site (the one associated with the Team's standard channels) gets archived. The private and shared channel sites stay active. There is no error thrown. This means if you're running bulk archive scripts, you may think you've archived everything when you haven't.
# Check all sites associated with a specific Team via Graph API
GET https://graph.microsoft.com/v1.0/groups/{groupId}/sites
# This will show the main site plus any channel sites
# Only the main site can be archivedFile-Level Archive: Application Errors and Compatibility Issues
File-level archiving is in preview, and the list of known application compatibility failures is significant. If your users are reporting errors when trying to open files, or files appear broken in certain apps, check whether those files are in an archived state. The affected applications include:
- Word Online and PowerPoint Online
- Teams, OneDrive, and SharePoint mobile applications
- macOS with the OneDrive sync client
- Windows 10 and earlier with the OneDrive sync client
- Windows devices not configured for frequent updates
- Office desktop apps that haven't updated since March 1, 2026
- Clipchamp and Power BI when importing archived content
If file-level archive is enabled in your tenant, communicate proactively to end users that archived files need to be reactivated at their original location before they can be opened normally. Don't wait for help desk tickets to pile up.
Search and eDiscovery Behavior for Archived Content
One of the best things about Microsoft 365 Archive compared to third-party archiving solutions is that content remains fully indexed. Microsoft Purview Content Search, end-user SharePoint search, and eDiscovery search all continue to return results from archived sites. However, if you're running a Purview export of archived content, expect it to take significantly longer than exporting from active sites. Prepare your legal and compliance teams for this reality when archiving large repositories.
Copilot and Archived Content
This is a detail that Copilot-heavy organizations will care about a lot: Microsoft 365 Copilot is not trained on archived content. This is actually documented as a feature, it means archiving stale data has the side effect of improving Copilot response quality by removing outdated information from its training scope. If your Copilot responses are polluted with outdated project data, archiving those old SharePoint sites is a legitimate remediation strategy.
If pay-as-you-go billing is correctly configured, your role is correct, and Archive still won't enable after 24 hours, that's a tenant provisioning issue that you won't be able to fix yourself. Similarly, if archived sites aren't appearing in Purview search after several hours when they should be, or if a site reactivation hangs in a perpetual "reactivating" state in the admin center, escalate directly. Contact Microsoft Support with your tenant ID, the specific site URL, and a screenshot of the current state, that'll get you to the right team faster than a generic ticket.
Prevention & Best Practices for Microsoft 365 Archive
Getting Microsoft 365 Archive set up is one thing, using it well is another. These best practices will save you from painful mistakes that I've watched organizations make in the months after rollout.
Notify Site Owners and Users Before Archiving
This sounds obvious but gets skipped constantly. When a site is archived, it becomes completely inaccessible to everyone, not just to casual users, but to site owners too. Content is in the cold tier. If a site owner suddenly can't access their project site and nobody told them it was being archived, you'll be flooded with urgent tickets and very frustrated people. Build a formal notification process: email site owners at least 5 business days before archiving, and again 24 hours before. Treat it like a planned maintenance window.
Audit Site Templates Before Running Bulk Archive Scripts
Before attempting any large-scale archiving operation, especially via PowerShell or Graph API, export a list of all target sites and their template types. Publishing sites, channel sites, and legacy templates will fail silently in some scenarios and loudly in others. Knowing ahead of time which sites can't be archived lets you handle exceptions without derailing the broader operation.
# Get all site templates in your tenant
Connect-SPOService -Url "https://[yourtenant]-admin.sharepoint.com"
Get-SPOSite -Limit All | Select-Object Url, Template | Export-Csv sites-audit.csv -NoTypeInformationDocument Your Reactivation SLA
Somebody will eventually need content back from a Microsoft 365 Archive site under time pressure, a legal hold, an audit, an executive request. Have a documented reactivation process before you need it, not during the crisis. Include who has permission to request reactivation, who can approve it, and realistic timing expectations for reactivation plus the 30-day re-archive cooldown on individual files.
Don't Archive Sites with Active Retention Policies Without Review
Archived content still falls under Microsoft Purview compliance policies. This is generally a good thing, your retention labels and holds travel with the archived data. But before archiving sites with complex retention configurations, verify with your compliance team that the expected behavior aligns with your legal obligations. Don't assume archived equals compliant without doing that review.
- Set up a monthly review in the SharePoint admin center to identify sites with zero activity in the last 180 days, these are archive candidates.
- Before enabling file-level archive (preview) for your organization, pilot it with a small group of technically savvy users who can report application errors clearly.
- Tag all Microsoft 365 Archive costs in Azure with a
CostCentertag on your resource group so archive storage charges appear cleanly in your billing reports. - Keep a record of which sites have been archived and when, the SharePoint admin center's Archived sites view doesn't include an archive date column by default, so maintain a separate log or use the audit log in Purview.
Frequently Asked Questions
Why can't I find the Archive option in the SharePoint admin center?
The Archive option in the SharePoint admin center only appears after you've fully enabled Microsoft 365 Archive in the Microsoft 365 admin center, which itself requires pay-as-you-go billing to be configured and linked to an Azure subscription first. If you skip the billing setup step, the Archive button simply won't show up. Go to admin.microsoft.com > Settings > Org settings > Pay-as-you-go services > Settings tab > Storage services > Archive and make sure the toggle is on. Also verify you're signed in as a SharePoint Administrator or Global Administrator, any other role won't surface these options.
Can I archive a Microsoft Teams site with Microsoft 365 Archive?
It depends on the Teams site's channel configuration. Teams sites that use only standard channels are fully supported for archiving. If the Team has private or shared channels, the situation gets complicated: through the SharePoint admin center, you'll get the error "The group connected site with channel sites associated can't be archived" and the operation will be blocked. Through PowerShell or Graph API, the archive operation won't error out, but it only archives the main Team site, the private and shared channel sites stay active and cannot be archived directly because they use unsupported site templates.
Does archiving a SharePoint site delete any of the content or metadata?
No, archiving is completely lossless. When a site moves to Microsoft 365 Archive cold storage, everything travels with it: document libraries and their folder structures, all files, lists and list data, site permissions, and all metadata. When you reactivate the site later, it comes back exactly as it was. Nothing is stripped, transformed, or modified during the archiving or reactivation process. This is one of the core advantages of using Microsoft 365 Archive over third-party archiving tools that sometimes lose metadata fidelity.
Can users still search for content in archived sites?
Yes, and this is a genuinely useful capability that sets Microsoft 365 Archive apart from basic data deletion. Archived content remains fully indexed and searchable through SharePoint end-user search, Microsoft Purview Content Search, and eDiscovery search experiences. Users can find archived content via search, but they won't be able to directly access or open it without reactivation. For compliance and legal hold scenarios, Purview can export archived content directly without requiring reactivation first, though the export will take longer than exporting from active storage.
How does Microsoft 365 Archive pricing work, will I get a surprise bill?
Microsoft 365 Archive uses a pay-as-you-go model billed in gigabytes. Your Microsoft 365 licenses come with a certain amount of included SharePoint storage, Archive charges apply to storage consumed beyond that included quota. The actual per-GB rate is documented on the Microsoft pricing page and is designed to be significantly lower than active storage costs, which is the whole point. To avoid billing surprises, set up Azure cost alerts on the resource group you linked to Microsoft 365 Archive, you can configure threshold alerts that email you when charges exceed a defined amount in a billing period.
I archived a file but I need it again, why can't I archive it again after reactivating?
This is a platform-level limitation with file-level archiving (the preview feature): once a file is reactivated, it cannot be re-archived for 30 days. This is a hard rule enforced at the platform level, there's no administrative override or workaround for it. Plan your file archive cycles with this in mind. If you're running an archiving process that touches files frequently, the 30-day cooldown could interfere with your expected storage cost management. For frequently accessed files, site-level archiving (which doesn't have this restriction in the same way) or leaving the content in active storage may be more appropriate.