Fix Microsoft 365 Archive: Setup, Billing & SharePoint Errors
Why This Is Happening
I've worked through Microsoft 365 Archive setup problems on more tenant environments than I can count. The frustration is always the same: you're an IT admin sitting in front of the SharePoint admin center, you know you need to move inactive sites into cold storage to cut costs and clean up your environment , and nothing seems to work the way Microsoft's own documentation implies it should. The toggle won't appear. The billing link breaks. Teams sites throw cryptic errors. And the error messages? Completely useless. "This operation cannot be completed." That's it. No code, no context, no help.
Microsoft 365 Archive is a relatively new product, and that new-product smell hasn't fully worn off yet. A lot of the issues admins hit come down to a few core categories.
The billing dependency is the biggest one. Microsoft 365 Archive runs on a pay-as-you-go model billed per gigabyte, which means it requires an active Azure subscription linked to your Microsoft 365 tenant before any archive toggle even shows up in the admin center. If you skip that step or your Azure subscription isn't properly connected, you will never see the Archive option under Pay-as-you-go services. It just won't be there. No error, no warning, just silence. That one missing prerequisite probably accounts for 60% of the "I can't find the Archive setting" tickets I see.
Permissions are the second major trip wire. Only SharePoint Administrators and Global Administrators can configure Microsoft 365 Archive. If you're a Teams admin, a compliance officer, or even an Exchange admin trying to help out, the admin center will either hide the options entirely or block you with a generic permissions error when you try to flip any toggles. This catches people off guard because many SharePoint tasks can be delegated more broadly.
Then there are the site template limitations. Not every SharePoint site can be archived. Publishing sites, channel sites, and several legacy site template types are simply not supported. When you try to archive a Teams site that has private or shared channels attached to it, you'll get the message: "The group connected site with channel sites associated can't be archived." That one is genuinely confusing because archiving works fine for Teams sites with only standard channels, so the same Teams-connected SharePoint site might work for one team and fail for another, depending purely on channel structure.
File-level archive (currently in preview) adds its own layer of complexity. Certain applications, Word Online, PowerPoint Online, Teams mobile, OneDrive mobile, macOS sync clients, and older Office desktop builds that haven't been updated since March 1, 2026, don't fully support archived files yet. Users open a file and get a confusing load error with no explanation, which immediately turns into a support ticket back to you.
The good news is that every single one of these problems has a clear fix path. Let's go through them. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep on troubleshooting, run through this fast checklist. In most cases, genuinely, most cases, the Microsoft 365 Archive setup problem you're hitting is one of these three things.
Check 1: Is pay-as-you-go billing actually configured? Go to the Microsoft 365 admin center. Navigate to Settings > Org settings > Pay-as-you-go services. Click the Settings tab. If you don't see a "Storage services" section with an "Archive" option underneath it, pay-as-you-go billing is not set up, and you cannot proceed until it is. You'll need an Azure subscription and resource group created first. If you do see the Archive option but the toggle is grayed out, that's a permissions issue (see Check 2).
Check 2: Does your account have the right role? Log out and log back in as a user with either the SharePoint Administrator role or Global Administrator role assigned in Microsoft Entra ID (formerly Azure Active Directory). Neither Teams Administrator nor Compliance Administrator will work here, even if those roles seem logically related to archiving. The Microsoft 365 Archive configuration surface is locked down to those two roles specifically.
Check 3: Is the site you're trying to archive on a supported template? In the SharePoint admin center, find your site and check its template type. Publishing sites, channel sites, and certain legacy templates are explicitly not supported by Microsoft 365 Archive. If you're working with a Teams-connected site, verify whether that team uses any private or shared channels. If it does, you cannot archive the site from the SharePoint admin center UI, you'd need to use PowerShell or Graph API instead (and even then, only the main site gets archived; the channel sites stay active).
If you've confirmed billing is set up, you have the right permissions, and the site template is supported, but archiving is still failing, then keep reading. The step-by-step section covers every scenario in detail.
Microsoft 365 Archive billing runs through Azure, so the very first thing you need is a working Azure subscription tied to your organization's tenant. This is non-negotiable, there is no workaround and no way to skip it. If your organization already has Azure subscriptions in use for other services (like Azure Virtual Machines or Azure AD Premium), you may be able to reuse an existing one. If not, you'll need to create one.
Log into the Azure portal and navigate to Subscriptions. If you don't have an active subscription, click Add and follow the billing setup wizard. Once your subscription is active, create or designate a resource group that will be associated with your Microsoft 365 pay-as-you-go billing. Resource groups are just logical containers in Azure, you can create a new one specifically for Microsoft 365 services to keep things clean and auditable.
A couple of common mistakes here: first, make sure the Azure subscription is associated with the same tenant as your Microsoft 365 environment. I've seen setups where the Azure subscription lives under a separate Entra ID tenant, that will break the billing link completely. Second, the subscription must be in an active, non-suspended state. Expired trial subscriptions and suspended pay-as-you-go subscriptions both fail silently when you try to link them in the Microsoft 365 admin center.
Once the subscription and resource group are ready, you're set to move on. You should see confirmation in the Azure portal showing your subscription status as "Active" before proceeding.
With your Azure subscription ready, the next step is to connect it to your Microsoft 365 environment. This is done inside the Microsoft 365 admin center, not the SharePoint admin center and not the Azure portal. The distinction matters because a lot of people go looking in the wrong place.
Navigate to Settings > Org settings in the Microsoft 365 admin center. On the Org settings page, find and select Pay-as-you-go services. If you don't see this option, your account doesn't have SharePoint Administrator or Global Administrator permissions, stop here and fix that first.
On the Pay-as-you-go services page, click the Settings tab. You'll see a prompt to link an Azure subscription. Walk through the linking wizard, select your Azure subscription and resource group, and confirm. This process takes about two to three minutes to complete in the background.
Once billing is linked, you should see the Storage services section appear under the Settings tab, with Archive listed as an option. If that section still doesn't appear after a few minutes, try signing out and back in, the admin center sometimes needs a fresh session to reflect the billing state change. You can also try a different browser as a quick sanity check; I've seen Edge's cached session data cause the admin center to display stale state even after a successful billing link.
# If you want to verify billing status via PowerShell before touching the admin center:
Connect-MgGraph -Scopes "BillingConfiguration.ReadWrite.All"
Get-MgBillingSubscriptionA successful billing setup means the toggle for Microsoft 365 Archive will now be clickable, not grayed out, in the next step.
Now you're in the home stretch for the initial setup. Back in the Microsoft 365 admin center, go to Settings > Org settings > Pay-as-you-go services, then the Settings tab. Under Storage services, click Archive. This opens the Microsoft 365 Archive panel on the right side of the screen.
You'll see a SharePoint site archive section with a status toggle. Flip that toggle to the on position. A confirmation panel titled "Enable SharePoint archiving" will slide in, click Confirm. That's the moment Microsoft 365 Archive becomes active for your tenant.
After confirming, you're now able to archive sites directly from the SharePoint admin center. By default, the file-level archive feature (currently in preview) is also enabled for users on SharePoint sites, but I'll cover how to manage that separately in step 5 since it has its own considerations.
What should you see if this worked? Go to the SharePoint admin center and navigate to Sites > Active sites. Select any eligible site, open its details panel, and look for an Archive option in the site actions. If that option appears, you're fully set up. If it doesn't appear, double-check that the toggle is showing as "On" in the pay-as-you-go services panel, sometimes a single confirm click doesn't register if the page is slow to respond, and you'll think you enabled it when you actually didn't.
# Verify Archive is enabled via SharePoint PnP PowerShell:
Connect-PnPOnline -Url "https://yourtenant-admin.sharepoint.com" -Interactive
Get-PnPTenant | Select-Object ArchiveEnabledWith Microsoft 365 Archive enabled, archiving a standard SharePoint site is straightforward: go to SharePoint admin center > Sites > Active sites, select the site you want to archive, and choose Archive from the actions menu. Microsoft's documentation is accurate here, the archive operation is genuinely fast, regardless of site size, and the site moves out of your tenant's active storage quota immediately upon archiving.
When you archive a site, everything inside it gets archived together: all document libraries, folder structures, files, lists, list data, permissions, and metadata. Nothing is lost. When you eventually reactivate the site, all of that comes back intact, lossless metadata is one of Microsoft 365 Archive's stronger design points.
Now, the Teams channel site error. If you see the message "The group connected site with channel sites associated can't be archived" in the SharePoint admin center, the Team behind this site has at least one private or shared channel. You cannot archive this site through the UI. Your options are:
Option A: Use PowerShell or Microsoft Graph API to archive the site. This doesn't block you from proceeding, but be aware that only the main team site (and its standard channels) will be archived. Private and shared channel sites stay active, and you cannot directly archive those channel sites at all, because they use unsupported site templates.
# Archive a SharePoint site via PnP PowerShell:
Connect-PnPOnline -Url "https://yourtenant-admin.sharepoint.com" -Interactive
Set-PnPSite -Identity "https://yourtenant.sharepoint.com/sites/yoursite" -Archived $trueOption B: If you need the entire Teams environment archived (including channel sites), use Microsoft Teams' own archiving feature in the Teams admin center for the team itself, this is separate from Microsoft 365 Archive and has different behavior.
Before archiving any site, notify the site owners and users. Archived sites are not accessible to anyone, not even site owners. That's not a recoverable situation without admin intervention to reactivate, so communication upfront saves a lot of confusion.
File-level archive is in preview as of this writing, and it comes with a set of limitations that are causing real user pain if you don't communicate them proactively. This step covers how to manage the feature and how to handle the error reports that will come in from users hitting unsupported apps.
By default, when you enable Microsoft 365 Archive, file-level archiving is also available to users on SharePoint sites. If you want to enable or disable the preview specifically, go back to the Microsoft 365 Archive panel in the admin center, the File archive section has its own toggle separate from site-level archiving.
Known app compatibility issues with archived files: Word Online, PowerPoint Online, Teams mobile, OneDrive mobile apps, macOS with the OneDrive sync client, older Windows versions (Windows 10 and earlier) with the OneDrive sync client, Office desktop apps that haven't received updates since March 1, 2026, Clipchamp, and Power BI all either fail to load archived files or display incorrect errors. These apps are not fully aware of the archived file state during this preview period.
When a user reports that a file "won't open" or shows a generic load error, the first thing to check is whether that file has been archived. If it has, the fix is to reactivate the file at its original location. Users with appropriate permissions can do this directly in SharePoint by right-clicking the file and selecting Reactivate.
Important constraints to know: files that have been reactivated cannot be archived again for 30 days. Certain file types cannot be archived at all, OneNote notebooks, SharePoint pages, and SharePoint agents are excluded. The Site Assets library on SharePoint sites is also excluded from file-level archive. And if an archived file is copied or moved to OneDrive, the archived state may not display correctly in the OneDrive UI, even though the file retains its archived state.
# Check if a specific file is in archived state via Graph API:
GET https://graph.microsoft.com/v1.0/sites/{siteId}/drives/{driveId}/items/{itemId}
# Look for "archiveStatus" in the response payloadAdvanced Troubleshooting
Billing links failing silently. If you've completed the Azure subscription setup but the Archive toggle still doesn't appear in the Microsoft 365 admin center even after 15+ minutes and a fresh session, check the Azure subscription's status directly in the Azure portal. A subscription in "Warned," "Disabled," or "Deleted" state will fail to link without any meaningful error surfaced in the Microsoft 365 admin center. Also check whether the account performing the billing link has the Owner or Contributor role on the Azure subscription, read-only access is not sufficient to complete the billing link.
Searching archived content returns no results. Microsoft 365 Archive maintains full content search compatibility, meaning Purview Content Search, end-user search, and eDiscovery should all index archived content. If searches against archived sites return nothing, allow 24-48 hours for the search index to reflect the newly archived content. For Purview Content Search and eDiscovery specifically, these can export archived content directly, but the export process may take significantly longer than for active content. This is expected behavior, not a bug. Factor this into any compliance timelines.
PowerShell error: "Set-SPOSite is not recognized." Microsoft 365 Archive site management via PowerShell requires the SharePoint Online Management Shell module version 16.0.24524.12000 or later. Run Update-Module -Name Microsoft.Online.SharePoint.PowerShell to get current, then reconnect.
Graph API archiving returns 403 Forbidden. Your service principal or application registration needs the Sites.FullControl.All permission in Microsoft Graph with admin consent granted. Sites.ReadWrite.All is not sufficient for archive operations. Go to the Azure portal, find your app registration under Entra ID > App registrations, navigate to API permissions, and verify the consent status.
Event Viewer indicators. On Windows devices where users experience file-level archive errors, check Event Viewer under Applications and Services Logs > Microsoft > OneDrive. Look for Event ID 1001 (sync errors) and Event ID 3000-series entries which flag file state conflicts. These won't explain the archive situation directly, but they'll confirm whether the issue is the sync client failing to represent the archived state or a genuine permissions problem on the file.
Storage quota not decreasing after archiving. When a site is archived, it moves out of the tenant's active storage quota and into Microsoft 365 Archive storage consumption. The active quota metric in the Microsoft 365 admin center can lag by up to 24 hours in reflecting this change. If it hasn't updated after 24 hours, use the SharePoint admin center storage reports to verify the site is showing as "Archived" state rather than "Active", that's the authoritative view of where the storage is being counted.
Prevention & Best Practices
Getting Microsoft 365 Archive working is one thing. Keeping it working, and avoiding the operational headaches that bite admins six months after initial setup, is a different skill set. Here's what I recommend based on real-world deployments.
Communicate before you archive, every time. Microsoft's own documentation explicitly recommends notifying site owners and end users before archiving. I'd go further: build a formal process for this. Archived sites are completely inaccessible to all users, including site owners, the moment they're moved to cold storage. Users who don't know their site is being archived will open a ticket within minutes of the change. A simple email template sent 5-7 business days before archiving, with a follow-up 24 hours out, eliminates 90% of the "my SharePoint site disappeared" helpdesk noise.
Audit your Teams channel topology before bulk archiving. If you have a large SharePoint environment with many Teams-connected sites, run a pre-archive audit to identify which sites are attached to Teams with private or shared channels. Those sites will fail in the admin center UI and need PowerShell or Graph API handling. Identifying them upfront turns what could be a chaotic bulk operation into a controlled, scripted one.
Set a review cycle for archived sites. Microsoft 365 Archive is designed for inactive, aging content that you still need to retain, not for permanent deletion avoidance. Without a review cycle, your archive storage costs will grow indefinitely. Establish a quarterly or annual review where you evaluate archived sites against your retention policies and either reactivate sites that are needed again or delete sites that have exceeded their retention period.
Monitor your Archive storage consumption in billing. Since Microsoft 365 Archive operates on pay-as-you-go pricing billed per GB, unexpected growth in archived content will show up in your Azure bill. Set up Azure cost alerts on the resource group associated with your Microsoft 365 billing to get notified if monthly spend exceeds a threshold you define. This is basic cost hygiene but I see it skipped constantly.
- Run a monthly SharePoint inactive site report (sites with no activity in 90+ days) to build a reliable candidate list for Microsoft 365 Archive, don't archive ad hoc.
- Use the SharePoint admin center's built-in storage reports before and after archiving to confirm your active storage quota is decreasing as expected.
- For file-level archive (preview), add a banner or announcement to affected SharePoint sites explaining that some older app versions may show errors on archived files and how users can reactivate files themselves.
- Keep your Microsoft 365 admin center and SharePoint admin center accounts at SharePoint Administrator rather than Global Administrator wherever possible, Microsoft specifically recommends least-privilege for archive management, and Global Admin should be reserved for genuine emergencies.
Frequently Asked Questions
The Archive option isn't showing up in my Microsoft 365 admin center, what am I missing?
The single most common cause is that pay-as-you-go billing hasn't been configured yet. Microsoft 365 Archive requires an Azure subscription linked to your tenant before the Archive option appears under Settings > Org settings > Pay-as-you-go services > Settings > Storage services. If you've set up billing and the option still doesn't appear, verify that your account holds either the SharePoint Administrator or Global Administrator role, no other roles surface the Archive configuration panel. A hard refresh of the admin center page after ensuring billing is linked usually resolves the display issue.
Can users still search for content inside an archived SharePoint site?
Yes, this is one of Microsoft 365 Archive's key design advantages over traditional cold storage approaches. Full content search works for end-user SharePoint search, Purview Content Search, and eDiscovery search even after a site is archived. However, the content is not directly accessible; users can find it in search results but cannot open files from the archived site until it's reactivated. Purview Content Search and eDiscovery can also export archived content directly, though exports from archived sites may take longer to complete than exports from active sites.
Why am I getting "The group connected site with channel sites associated can't be archived" for a Teams site?
This error appears in the SharePoint admin center UI when the Microsoft Team connected to the site has at least one private or shared channel. The UI blocks archiving in this scenario. Your options are to use PowerShell (Set-PnPSite -Archived $true) or the Microsoft Graph API to proceed, neither blocks the operation, but only the main team site and its standard channels will be archived; private and shared channel sites remain active. Directly archiving channel sites is not possible because they use unsupported site templates.
My users are getting errors when trying to open files after I enabled file-level archive. What's happening?
File-level archive is currently in preview, and a number of Microsoft 365 apps don't fully support the archived file state yet. Word Online, PowerPoint Online, Teams mobile, OneDrive mobile, macOS with the OneDrive sync client, and Office desktop apps that haven't been updated since March 1, 2026 all have known issues displaying or opening archived files. The fix is to have users (or an admin) right-click the affected file in SharePoint and select Reactivate to restore it to active status. Keep in mind that reactivated files cannot be archived again for 30 days.
Does Microsoft 365 Archive affect Copilot responses? Will Copilot search archived content?
No, and this is actually listed as a feature benefit, not a limitation. Copilot is intentionally not trained on or able to surface archived content. Microsoft's reasoning is that excluding inactive, archived data from Copilot keeps its responses more relevant and accurate. If you have old, outdated content that's been cluttering Copilot's responses and causing it to surface stale information, archiving that content is a practical way to improve Copilot's output quality for your users without deleting anything permanently.
How much does Microsoft 365 Archive actually cost, and where does the bill show up?
Microsoft 365 Archive uses a pay-as-you-go billing model priced per gigabyte of archived content, the cost is lower than the standard Microsoft 365 active storage rate, which is the whole point for long-term inactive data. The bill surfaces in your Azure subscription, under the resource group you designated when setting up pay-as-you-go billing. Archived data does not count against your tenant's license-allocated Microsoft 365 storage quota, it's tracked and billed separately as Microsoft 365 Archive storage consumption. Set up an Azure cost alert on that resource group to avoid billing surprises as archived content grows.