Fix Teams Archive Policy Does Not Run for a Department Team

When you set a Teams retention or archive policy for a department team, you expect the policy to run automatically. But sometimes the policy never triggers, and the team stays active with all its data. This usually happens because the policy assignment is incorrect, the team is excluded by a broader policy, or the archive job is delayed. This article explains the technical causes and gives you step-by-step fixes to make the archive policy run reliably.

Archive policies in Teams are part of Microsoft 365 retention and are managed through the Microsoft Purview portal. They work by placing a hold on content and then moving it to an archive location after a specified period. If your department team is not archiving, the issue is likely in how the policy is scoped, applied, or prioritized.

You will learn how to verify policy assignments, check for conflicting policies, and force an archive run using PowerShell. You will also see what to do if the policy still does not run after these steps.

Why Teams Archive Policy Does Not Run for a Department Team

Archive policies in Teams are built on Microsoft 365 retention. When you create a retention policy that archives content, it applies to the underlying SharePoint site, Exchange mailboxes, and OneDrive accounts of the team members. The policy runs on a timer, usually every 7 days, and moves content that is older than the specified retention period to the archive.

If the policy does not run for a specific department team, the root cause is often one of these:

• The policy is scoped to a distribution group or security group, but the department team is not a member of that group.
• A broader policy with a shorter retention period is overriding the archive policy.
• The team has a sensitivity label that blocks archiving or sets a different retention rule.
• The archive job is stuck because of a large amount of data or a service issue.

Another common cause is that the policy is set to “retain” but not “archive.” In Microsoft 365, archiving is a type of retention action. If the policy only retains content without moving it to the archive, you will not see the expected result.

How Archive Policies Interact with Teams

Teams data is stored in multiple locations. Channel messages are in the group mailbox, files are in the SharePoint site, and chat messages are in each user’s mailbox. An archive policy must cover all these locations to work correctly. If your policy only targets the SharePoint site, for example, the chat messages will not be archived.

Steps to Diagnose and Fix the Archive Policy

Follow these steps in order. Each step checks a possible cause and applies a fix if needed.

1. Check the policy scope in Microsoft Purview
   Go to Microsoft Purview portal > Data lifecycle management > Microsoft 365. Find your archive policy and click on it. Look at the “Locations” tab. Confirm that the department team’s SharePoint site and group mailbox are listed. If they are not, edit the policy and add the team’s site or mailbox. You can add by URL or by group name.
2. Verify the team is a member of the assigned group
   If your policy is scoped to a group, open the group in Azure AD and check membership. The department team must be a member of that group. If it is not, add the team’s group as a member. Wait up to 24 hours for the policy to pick up the change.
3. Check for conflicting retention policies
   In the same Purview portal, list all retention policies. Look for any policy that has a shorter retention period or a “delete” action. If a delete policy applies to the same team, it may override the archive. To fix this, either extend the delete policy or exclude the team from it. Remember that the longest retention period wins, but a delete action can still block archiving.
4. Check the sensitivity label on the team
   Open Teams admin center > Teams > Manage teams. Select the department team and view its properties. Look at the sensitivity label. If the label has a retention setting, it may conflict with your archive policy. Remove the label or change its retention settings so that it does not block archiving.
5. Use PowerShell to force a policy run
   Connect to Exchange Online PowerShell. Run the command Get-RetentionCompliancePolicy to see all policies. Then run Start-ManagedFolderAssistant -Identity to force the archive job for that mailbox. For the SharePoint site, use the SharePoint Online Management Shell and run Start-SPOSiteArchive -Identity . This triggers an immediate archive attempt.
6. Check the archive mailbox status
   For chat messages, each user must have an archive mailbox enabled. Run Get-MailUser | FL ArchiveStatus in Exchange Online PowerShell. If the archive is disabled, enable it with Enable-RemoteMailbox -Archive. Without an archive mailbox, the policy cannot move messages.
7. Wait for the next scheduled run
   If nothing is wrong, the policy may simply be waiting for the next scheduled run. Retention policies run every 7 days. Check the policy’s “Last run” date in the Purview portal. If it has not run in over 7 days, contact Microsoft support.

If Teams Still Has Issues After the Main Fix

Teams Archive Policy Does Not Run for a Specific Channel

If the policy runs but a specific channel is not archived, the channel may have a private or shared status. Private and shared channels have separate SharePoint sites that are not automatically included in the team’s site. You must add each channel site to the policy scope manually. Go to the channel’s Files tab, copy the site URL, and add it in the policy locations.

Archive Policy Runs But No Data Is Moved

If the policy status shows “running” but no data moves, check the retention period. The archive policy only moves content that is older than the retention period. If your team has only been active for a few weeks and the retention period is 90 days, nothing will be archived yet. Adjust the retention period to a shorter value for testing.

Archive Policy Does Not Run for a Team After a Name Change

When you rename a team, the SharePoint site URL changes. The policy may still point to the old URL. Edit the policy in Purview and remove the old site, then add the new site URL. You can find the new URL in the team’s Files tab.

Archive Policy Scenarios: Group-Based vs Location-Based

Item	Group-Based Policy	Location-Based Policy
Scope	Applies to all members of a distribution or security group	Applies to specific SharePoint sites, mailboxes, or OneDrive accounts
Setup	Select the group in the policy wizard	Add each site or mailbox manually
Best for	Department teams that are static	Teams that change membership often
Limitation	New teams must be added to the group	Time-consuming for many teams

A group-based policy is easier to manage if you have many department teams. A location-based policy gives you more control but requires more maintenance.

You can now check the policy scope, fix group membership, and force an archive run using PowerShell. Start by verifying the policy locations in the Purview portal, then run the PowerShell commands to trigger an immediate archive. As a next step, review all your retention policies to ensure none conflict with the archive. For advanced control, use the Start-ManagedFolderAssistant cmdlet to run archiving on demand for any mailbox.