Fix Microsoft 365 Archive: Setup & Config Problems
Why Microsoft 365 Archive Problems Keep Happening
You've got a growing SharePoint environment, inactive sites eating into your storage quota, and someone upstairs asking why the Microsoft 365 bill keeps climbing. So you go to set up Microsoft 365 Archive , the cold-storage tier Microsoft built exactly for this scenario , and nothing works the way you expect. The toggle isn't there. The site won't archive. Or worse, the Archive option is grayed out completely and you have no idea why.
I've seen this exact scenario play out on dozens of tenants. The frustrating part isn't the feature itself, it actually works well once it's running. The problem is the setup chain. Microsoft 365 Archive has a hard dependency on pay-as-you-go billing, which in turn requires a linked Azure subscription. If any link in that chain is broken, the entire feature either doesn't appear or fails silently. And the error messages Microsoft surfaces in the admin center? They range from vague to completely missing.
Let me break down the actual root causes you're most likely hitting.
The Azure billing link isn't configured. This is the number one reason Microsoft 365 Archive setup fails. You cannot turn on Microsoft 365 Archive without first linking an Azure subscription and configuring pay-as-you-go billing in the Microsoft 365 admin center. Skipping this step, even partially, blocks the feature entirely. A lot of admins discover this only after spending 30 minutes hunting through the SharePoint admin center for the Archive option that simply isn't there yet.
You're running into unsupported site templates. Not every SharePoint site can be archived. Publishing sites, channel sites (the ones associated with Teams private or shared channels), and several legacy site template types are explicitly excluded. If you try to archive one of these through the SharePoint admin center, you'll hit an error like "The group connected site with channel sites associated can't be archived." That message is at least honest. The fix, however, isn't obvious, I'll cover it in the advanced section.
Permissions are wrong. Microsoft 365 Archive is managed exclusively by SharePoint Administrators or Global Administrators. If the person setting this up holds a lesser role, even one with broad SharePoint access, they won't be able to reach the correct settings pages. Microsoft is deliberate about this, and for good reason.
File-level archive (currently in preview) has application support gaps. Word Online, PowerPoint Online, Teams mobile, OneDrive mobile, macOS OneDrive sync client, and older Windows 10 devices with the OneDrive sync client all have known issues with file-level archiving as of early 2026. If your users are hitting broken previews or unexpected errors opening files, this is almost certainly why.
None of these problems are permanent. Every single one of them is fixable. Let's get into it. Browse all Microsoft fix guides →
The Quick Fix, Try This First
If Microsoft 365 Archive simply isn't showing up in your admin center, or if the toggle to enable it is missing, there's an 80% chance the fix is a single missing step: you haven't configured pay-as-you-go billing. Here's how to confirm that and fix it in under ten minutes.
First, open the Microsoft 365 admin center at admin.microsoft.com. Sign in with your SharePoint Administrator or Global Administrator account, any other account will get you blocked before you even start.
Now navigate to Settings > Org settings. On the Org settings page, look for the Pay-as-you-go services option. If you click into it and land on a page asking you to set up an Azure subscription, that's your answer right there. The Archive toggle doesn't appear until billing is wired up.
To complete the billing link, you'll need an active Azure subscription and a resource group. If your organization already uses Azure for anything, virtual machines, storage, Entra ID premium licensing, you likely already have a subscription. Grab the subscription ID from the Azure portal at portal.azure.com under Subscriptions.
Once pay-as-you-go billing is live in the M365 admin center, come back to Settings > Org settings > Pay-as-you-go services and select the Settings tab. Under Storage services, you'll now see Archive. Click it. On the Microsoft 365 Archive panel, find the SharePoint site archive section, flip the status toggle to on, and confirm when prompted. That's it, Microsoft 365 Archive for SharePoint sites is now enabled.
After that, head to the SharePoint admin center, navigate to Sites > Active sites, select the site you want to archive, and look for the Archive action in the command bar or site details panel.
Microsoft 365 Archive follows a pay-as-you-go pricing model, billed per gigabyte of archived data. That billing flows through Azure, which means you need an Azure subscription before anything else happens. If your organization doesn't have one yet, this step isn't optional, it's the foundation.
Go to portal.azure.com and sign in with a Global Administrator or Billing Administrator account. From the left nav, select Subscriptions. If you see an existing subscription, note the Subscription ID, you'll need it shortly. If you need to create one, select + Add and follow the wizard to set up a Pay-As-You-Go subscription.
Next, create a Resource Group to house the Archive billing resource. In the Azure portal, search for "Resource groups" in the top search bar, select + Create, give it a name that makes sense for your org (something like M365-Archive-RG works fine), select your subscription, choose your region, and click Review + create, then Create.
The resource group itself doesn't cost anything to create. Costs only accrue when Microsoft 365 Archive actually starts storing archived SharePoint content. According to the current Microsoft 365 Archive pricing model, charges apply to storage consumption beyond your license-allocated Microsoft 365 storage quota.
Once the resource group is created, you should see it appear in the Resource groups list within about 30 seconds. Keep both your Subscription ID and Resource Group name handy, the next step in the M365 admin center will ask for them.
What success looks like: Your Azure resource group shows a status of "Succeeded" in the portal. No errors, no failed deployments listed in the Activity log.
With your Azure subscription and resource group ready, the next step is connecting them to your Microsoft 365 tenant. This is the link that makes Microsoft 365 Archive billing actually work, and the step most admins either skip or do out of order.
Open the Microsoft 365 admin center (admin.microsoft.com) and sign in as a Global Administrator or SharePoint Administrator. From the left navigation, go to Settings > Org settings. On the Org settings page, find and select Pay-as-you-go services.
You'll land on the Pay-as-you-go services configuration page. Select Set up billing (or similar, the exact label may vary by tenant configuration state). You'll be prompted to enter:
- Your Azure Subscription ID
- Your Resource Group name
- Your Azure region (pick the one closest to your tenant's primary region)
After submitting, Microsoft spins up a lightweight billing resource in your Azure resource group. You can verify this by going back to portal.azure.com, opening your resource group, and looking for a new resource of type Microsoft 365 Billing or similar. It typically appears within 2–5 minutes.
One important note: if you see an error during this step saying something like "You don't have permission to create resources in this subscription," the Azure account you're using lacks the Contributor or Owner role on the subscription. Fix that in Azure under Subscriptions > Access control (IAM) before retrying.
What success looks like: The Pay-as-you-go services page in the M365 admin center shows a status of "Active" or "Connected" next to your Azure subscription details. No pending actions, no warning banners.
Now that pay-as-you-go billing is configured, you can actually turn on Microsoft 365 Archive. This step is surprisingly quick, the long part was the billing setup.
Still in the Microsoft 365 admin center, go back to Settings > Org settings > Pay-as-you-go services. This time, select the Settings tab at the top of the page. Look for the section labeled Storage services, you'll see Archive listed there. Select it.
A side panel opens called the Microsoft 365 Archive panel. Inside it, you'll see a section for SharePoint site archive. There's a toggle switch. Flip it to on. Microsoft will show you a confirmation dialog, something like the Enable SharePoint archiving panel. Read it, then select Confirm.
That's all it takes to enable site-level archiving. Within a few minutes, the option to archive sites will appear in the SharePoint admin center under Sites > Active sites.
If you also want to enable file-level archive (currently in preview as of early 2026), there's a separate toggle for that. Be aware of the preview limitations before enabling it for end users, Word Online, PowerPoint Online, Teams mobile, and the OneDrive sync client on macOS and older Windows versions all have known issues with archived files. I'd strongly recommend enabling file-level archive for a pilot group first, not tenant-wide.
To control whether users can archive files themselves, or to restrict file-level archive to admins only, look for the management settings within the same Archive panel.
What success looks like: In the SharePoint admin center, when you select an active site, you'll see an Archive option available in the command bar or the site properties panel. The feature is live.
With Microsoft 365 Archive enabled, let's actually archive a site. This is where the real storage savings begin, and where you need to know what you can and can't archive before you start.
Open the SharePoint admin center at [yourtenant]-admin.sharepoint.com. Navigate to Sites > Active sites. Find the site you want to archive. You can use the search bar at the top right, search by site name or URL.
Select the site by clicking the checkbox next to it. In the command bar at the top, look for the Archive button (it may be inside a ... overflow menu depending on your screen width). Click it. You'll get a confirmation prompt reminding you that the site will no longer be directly accessible. Confirm the action.
The site moves to an archiving state. Depending on the site's size, this can be nearly instant or take a few minutes. Once complete, the site disappears from Active sites and appears under Archived sites (look for this in the left navigation of the SharePoint admin center).
A few things will happen from this point forward. The site, including all document libraries, folder structures, lists, permissions, and metadata, moves into the cold storage tier. It no longer counts against your tenant's active storage quota. It starts contributing to Microsoft 365 Archive storage consumption instead, billed through your linked Azure subscription.
End users who try to access the site will find it inaccessible. This is expected and by design. Before archiving any site, notify its owners and users. Microsoft's own documentation is explicit about this recommendation, and I'd add: send that notification at least a week in advance, not the day of. People need time to save or move anything critical.
If you hit the error "The group connected site with channel sites associated can't be archived", stop. That site has Teams private or shared channels attached to it. The SharePoint admin center blocks archiving in this case. See the Advanced Troubleshooting section for how to handle this with PowerShell.
What success looks like: The site no longer appears under Active sites. It shows up in Archived sites with a status indicating it's in the archived state. Storage reports will reflect the shift within 24 hours.
At some point, someone is going to need access to an archived site. Maybe there's a compliance inquiry, a former employee's files are needed, or a project suddenly becomes active again. Reactivating a site in Microsoft 365 Archive is straightforward, but there are a few things to know ahead of time.
Go to the SharePoint admin center and navigate to Archived sites in the left navigation. Find the site you need. Select it, then look for the Reactivate option in the command bar or details panel. Confirm when prompted.
Reactivation restores the site exactly as it was when archived, all metadata, permissions, folder structures, and content come back intact. Microsoft calls this "lossless metadata," and in my experience it holds up. I've reactivated sites that were archived for over a year and found everything exactly as expected.
Reactivation time depends on site size. Small sites come back in minutes. Very large sites, multi-gigabyte repositories, can take longer. Plan accordingly if you're reactivating for a time-sensitive compliance request.
A few important constraints to be aware of:
- File-level archive reactivation: Individual files that are reactivated cannot be archived again for 30 days. This is a hard platform limit, not something you can work around with PowerShell or API calls.
- Search availability: Even while archived, content remains searchable via Purview Content Search, eDiscovery, and end-user search. However, if you're running a Purview Content Search or eDiscovery export against archived content, expect longer export times, the cold storage tier has higher retrieval latency than active storage.
- Cost: Reactivating a site moves it back to active storage, which means it once again counts against your active storage quota. If storage costs were the reason you archived it, you'll want a plan for what happens after reactivation.
You can also reactivate sites programmatically using PowerShell or the Microsoft Graph API, which is useful if you're handling bulk reactivations or integrating with a lifecycle management workflow.
What success looks like: The site reappears under Active sites in the SharePoint admin center. Users can access it again. The site shows its full content with all permissions and metadata intact.
Advanced Troubleshooting for Microsoft 365 Archive
The steps above handle the most common setup and usage scenarios. But enterprise environments hit edge cases that don't fit neatly into the admin center UI. Here's what I see most often with SharePoint archive management at scale.
Teams Sites with Private or Shared Channels
This one trips up a lot of Teams-heavy organizations. When a SharePoint site is associated with a Microsoft Teams team that includes private or shared channels, the SharePoint admin center will flat-out refuse to archive it with the message: "The group connected site with channel sites associated can't be archived."
If you need to archive the main site anyway, PowerShell and the Microsoft Graph API will let you do it, but understand what you're actually getting. When you archive this way, only the main site associated with the Team (and its standard channels) gets archived. The private and shared channel sites stay active. Those private and shared channel sites use site templates that Microsoft 365 Archive doesn't support, so you can't archive them separately either.
To archive the main Teams site via PowerShell:
# Install the SharePoint Online Management Shell if you haven't already
Install-Module -Name Microsoft.Online.SharePoint.PowerShell -Force
# Connect to SharePoint Online
Connect-SPOService -Url https://[yourtenant]-admin.sharepoint.com
# Archive the site
Set-SPOSite -Identity https://[yourtenant].sharepoint.com/sites/[sitename] -ArchiveStatus ArchivedVerify the archive state with:
Get-SPOSite -Identity https://[yourtenant].sharepoint.com/sites/[sitename] | Select-Object -Property Url, ArchiveStatusChecking Archive State via Graph API
If you're managing Microsoft 365 Archive storage programmatically, say, as part of a lifecycle management script, the Microsoft Graph API exposes archive state information. This is useful for building dashboards or automated archival pipelines that trigger based on site inactivity thresholds.
GET https://graph.microsoft.com/v1.0/sites/{site-id}?$select=id,displayName,archiveStatusBilling Isn't Showing Up in Azure After Archiving
If you've archived sites but you're not seeing any charges appear in your Azure subscription within 48–72 hours, the most likely cause is that the billing linkage between M365 and Azure didn't complete correctly. Go back to Settings > Org settings > Pay-as-you-go services in the M365 admin center and verify that your Azure subscription shows as actively linked. If it's showing a disconnected or error state, you may need to re-run the billing setup. Don't just assume archiving is free because no charges appear yet, it's more likely a misconfiguration than a pricing gift.
Copilot Still Seems to Access Archived Content
One of the advertised benefits of Microsoft 365 Archive is that Copilot is not trained on archived content, which helps improve response relevancy. If your organization is seeing Copilot reference content that should be archived, first confirm the site is actually in an archived state (not just inactive) via the SharePoint admin center's Archived sites view. Content that's merely old but still in the active storage tier is still visible to Copilot. The separation only applies to content that has been explicitly moved to the cold storage tier through Microsoft 365 Archive.
Prevention & Best Practices for Microsoft 365 Archive
Once Microsoft 365 Archive is running, keeping it healthy is mostly about having a clear policy so things don't become chaotic over time. Here's what works in practice.
Define an archival policy before you archive anything. What makes a site "inactive"? Common thresholds are 180 days or 12 months since last content modification. Whatever you choose, document it and apply it consistently. Ad-hoc archiving, where you archive individual sites when someone complains about storage, creates inconsistency and makes lifecycle management a nightmare when you need to find something later.
Notify site owners before archiving. This isn't just good manners, it's explicitly recommended by Microsoft's own documentation. Give site owners at least one week's notice. Some organizations set up an automated email workflow that fires when a site hits the inactivity threshold, asking the owner to either claim the site (keeping it active) or let it archive. This reduces escalations significantly.
Keep file-level archive in preview status on a limited pilot. As of early 2026, the file-level archiving feature has too many application support gaps to deploy broadly without causing end-user confusion. Word Online, PowerPoint Online, and Teams mobile are all on the known-issues list. Wait until Microsoft has shipped broader client support updates, check for Office desktop app updates newer than March 1, 2026 as a baseline, before expanding file-level archive to general users.
Document which site templates you're working with before attempting bulk archival. Run a SharePoint admin center report or a PowerShell script before any large archiving push to identify which sites use template types that Microsoft 365 Archive doesn't support. Trying to archive unsupported templates in bulk just generates errors and wastes time.
- Set a calendar reminder to review the Archived sites list in the SharePoint admin center every quarter, sites that stay archived for years without review may be safe to delete entirely, saving Archive storage costs
- Use the SharePoint admin center's Site usage report (under Reports) monthly to identify new candidates for archiving before they become a storage complaint
- Create a dedicated SharePoint Admin role assignment for the team member responsible for archive management, avoid using Global Administrator for routine archive tasks
- Test the reactivation process on a non-critical archived site before you need it for a real compliance event, nothing worse than discovering reactivation quirks during a time-sensitive legal hold situation
Frequently Asked Questions
Why can't I see the Archive option in the SharePoint admin center at all?
The most likely reason is that Microsoft 365 Archive hasn't been enabled in the Microsoft 365 admin center yet. The Archive functionality in the SharePoint admin center only appears after you've enabled it under Settings > Org settings > Pay-as-you-go services > Settings > Storage services > Archive. Before you can get there, pay-as-you-go billing must be configured with a linked Azure subscription. No Azure link, no billing, no Archive toggle. Walk through steps 1–3 in this guide in order and the option will appear.
Does archiving a SharePoint site delete any content or permissions?
No, and this is one of the genuinely good things about Microsoft 365 Archive. When a site is archived, everything is preserved exactly: document libraries, folder structures, files, list data, permissions, and all metadata. Microsoft refers to this as "lossless metadata." When you later reactivate the site, it comes back exactly as it was when archived. Nothing is deleted, nothing is stripped, no permissions are changed. The only thing that changes is the storage tier the content lives in and the fact that end users can't directly access it while it's archived.
How much does Microsoft 365 Archive cost per month?
Microsoft 365 Archive uses a pay-as-you-go model billed per gigabyte of archived storage consumption. The key thing to understand is that the Archive pricing applies to storage beyond your license-allocated Microsoft 365 storage quota. Storage within your quota doesn't trigger Archive billing even if the content is archived. For current pricing numbers, check the official Microsoft 365 Archive pricing page directly, prices have changed since the feature launched and any specific per-GB figure I give you here could be outdated within weeks. The savings compared to keeping content in active storage are real and significant, especially for large tenants with a lot of inactive data.
Can my users search archived content from the regular SharePoint search bar?
Yes, but with one important caveat. Full content search works for archived content across end-user search, Purview Content Search, and eDiscovery search experiences. Users can find archived content by searching. However, they cannot directly open or access it without an admin reactivating the site or file first. Think of it like finding a book in a library catalog but the book being in off-site storage, you can see it exists, but you need to request retrieval to actually read it. For Purview Content Search and eDiscovery exports specifically, exporting archived content works but takes longer than exporting active content.
I get "The group connected site with channel sites associated can't be archived", what do I do?
This error appears when you try to archive a SharePoint site connected to a Microsoft Teams team that has private or shared channels. The SharePoint admin center doesn't allow archiving in this case. Your options are: use PowerShell with the Set-SPOSite -ArchiveStatus Archived command, which will archive the main Teams site and its standard channels while leaving private and shared channel sites active (they stay on unsupported site templates and can't be archived directly). Before you do this, make sure you understand what's staying active, private channel sites remain accessible even after the main site is archived, which may or may not be what you want from a compliance standpoint.
Can I archive OneDrive accounts with Microsoft 365 Archive?
Microsoft 365 Archive at the site level is for SharePoint sites, not OneDrive personal drives. File-level archive (the preview feature) is also available only for SharePoint sites. That said, there is a separate pay-as-you-go billing consideration for unlicensed OneDrive accounts, which is a distinct feature area from Microsoft 365 Archive. If your question is specifically about managing storage for former employees' OneDrive accounts, that falls under a different part of the Microsoft 365 admin center. One thing to watch: if an archived file is copied or moved into OneDrive, it retains its archived state, but the OneDrive UI may not always visually represent that state correctly, this is a known preview limitation.