When you change a Microsoft 365 group, the Teams archive policy may stop running. You expect old teams to move to Archive automatically, but they stay active. This usually happens because the policy assignment is tied to the group’s old identity or because the change did not trigger a policy evaluation. This article explains why the policy stops and gives you clear steps to get it running again.
You will learn how to check the effective policy, force a policy evaluation, and reapply the archive policy. You will also find out what to do if the problem continues after the main fix.
Key Takeaways: Fix Teams Archive Policy After a Group Change
- Teams admin center > Teams > Teams policies: Shows the archive policy assignments and lets you reapply them to the affected team.
- PowerShell cmdlet Set-TeamsArchivePolicy: Forces a policy evaluation for a specific team after a Microsoft 365 group change.
- Teams admin center > Teams > Manage teams > Archive: Manually archives a team if the policy still does not run automatically.
Why the Teams Archive Policy Stops After a Microsoft 365 Group Change
The Teams archive policy is a lifecycle policy that automatically archives teams after a specified number of days without activity. When you change the underlying Microsoft 365 group, such as changing the group name, description, or membership, the policy engine may lose track of the team. The change can reset the group’s metadata, which breaks the link between the team and the policy assignment.
Another common cause is that the group change does not trigger a policy evaluation. The archive policy runs on a schedule, usually daily, but it only evaluates teams that have not changed recently. If the group change updates the team’s last activity timestamp, the policy may think the team is still active and skip it.
The policy assignment itself is not deleted. The archive policy is still assigned to the user or the team, but the evaluation fails because the team’s identifier changed. This is why the policy does not run even though it appears correct in the admin center.
Steps to Diagnose and Fix the Teams Archive Policy
Follow these steps in order. Each step either confirms the issue or fixes it.
- Check the effective archive policy for the team
Open the Teams admin center at admin.teams.microsoft.com. Go to Teams > Manage teams. Find the affected team and select it. In the pane that opens, look for the Policy section. Verify that the archive policy is assigned. If it shows No policy, the assignment was lost. - Force a policy evaluation with PowerShell
Install the Microsoft Teams PowerShell module if you do not have it. Run Connect-MicrosoftTeams. Then run Get-TeamsArchivePolicy to list all policies. To force an evaluation for the specific team, run Set-TeamsArchivePolicy -Identity “TeamName” -ArchiveAfterInactiveDays 30. Replace 30 with the number of days you want. This command reapplies the policy and triggers a new evaluation. - Reassign the archive policy to the team owner
If the policy is assigned to the team owner, the group change may have removed the owner from the policy scope. Go to Teams admin center > Users > Manage users. Select the team owner. Under Assigned policies, check the Archive policy. If it is blank or wrong, assign the correct policy and save. - Manually archive the team as a temporary fix
If the policy still does not run, you can archive the team manually. In the Teams admin center, go to Teams > Manage teams. Select the team and choose Archive. This sends the team to the archive state immediately. The automatic policy will then keep it archived. - Wait for the next policy run
After reapplying the policy, wait for the next scheduled run. The archive policy runs daily. Check the team status after 24 hours. If it is still active, repeat the PowerShell command with the same parameters.
If Teams Archive Policy Still Does Not Run
Teams Shows the Policy as Assigned but Does Not Archive
This can happen when the team has recent activity that resets the inactivity timer. The archive policy only archives teams that have been inactive for the specified days. If users posted messages or uploaded files after the group change, the timer resets. Check the team’s last activity date in the Teams admin center. If it is recent, you need to wait for the inactivity period to pass again.
The Group Change Removed the Team from the Policy Scope
If you changed the group’s membership, the new members may not inherit the archive policy. The policy is applied at the user level or the team level. If you assign policies to users, only those users’ teams are affected. After the group change, new owners or members may not have the policy. Reassign the policy to the current members as shown in Step 3.
PowerShell Command Fails with an Error
If Set-TeamsArchivePolicy returns an error, check that you have the correct permissions. You need the Teams Administrator or Global Administrator role. Also verify that the team name is correct. Use Get-Team to list all teams and confirm the exact name. If the error mentions a policy not found, create a new archive policy first.
Teams Archive Policy: Manual vs Automatic Approach
| Item | Automatic Archive Policy | Manual Archive in Admin Center |
|---|---|---|
| Trigger | Runs daily on a schedule | Runs immediately when you click Archive |
| Inactivity requirement | Requires a set number of inactive days | No inactivity requirement |
| Control | Central policy controls many teams | One team at a time |
| Best for | Long-term lifecycle management | Quick fixes after a group change |
After you fix the archive policy, you can verify the team’s status in the Teams admin center under Teams > Manage teams. The status column will show Archived if the policy worked. If you need to undo an archive, you can restore the team from the same page. For ongoing management, set a reminder to check the policy after any Microsoft 365 group change.