Fix Teams Archive Policy Does Not Run for a Newly Created Team

When you create a new team in Microsoft Teams, the archive policy you set in the Teams admin center may not apply automatically. This leaves the team active past its intended expiration date, which can clutter your tenant and create compliance risks. The root cause is that archive policies are evaluated only when a team is created through certain channels or when the policy assignment is refreshed. This article explains why the policy stalls and provides clear steps to force it to run for new teams.

Why Teams Archive Policy Does Not Run for New Teams

Archive policies in Teams are part of the Teams policy framework. They define how long a team stays active before it is automatically archived. The policy engine runs on a schedule, usually every 24 hours. When you create a team, the policy assignment should apply immediately. However, in many tenants, the policy is not applied to teams created through the Teams desktop app, mobile app, or the Microsoft 365 admin center.

The reason is that these creation methods do not always trigger the policy evaluation event. Only teams created through the Teams admin center or via PowerShell with the correct parameter set get the policy applied at creation time. Teams created by users directly in the app may remain unassigned until the next scheduled policy refresh, which can take up to 24 hours. In some cases, the refresh never happens because the policy assignment is not linked to the team’s lifecycle event.

Another factor is the policy priority. If you have multiple archive policies, the one with the highest priority should win. But if the new team inherits a policy from a group or a user that has a lower priority, the intended policy may not apply. This is common when the team owner has a different policy assigned than the one you set for the entire tenant.

How the Archive Policy Works

An archive policy has two main settings: the number of days after which the team is archived, and whether to notify members before archiving. The policy is stored in the Teams policy service and is applied to teams based on the policy assignment. When a team is created, the policy service checks the assignment. If the team is created via the Teams app, the service may not receive the creation event in real time.

Steps to Force the Archive Policy to Run for a New Team

You have three methods to ensure the archive policy applies to a newly created team. Use the one that fits your admin access level.

Method 1: Check and Reassign the Policy in Teams Admin Center

1. Open the Teams admin center
   Go to https://admin.teams.microsoft.com and sign in with an account that has the Teams Administrator role.
2. Navigate to Teams policies
   In the left navigation, select Teams then Teams policies. Locate the archive policy you want to apply.
3. Check the policy assignment
   Select the policy, then go to the Assigned teams tab. Search for the new team. If it is not listed, the policy is not applied.
4. Manually assign the policy
   Select Manage teams at the top, add the new team to the list, and save. This forces the policy engine to evaluate the team immediately.
5. Verify the policy is active
   Go back to Teams then Manage teams. Find the team, open it, and check the Policy tab. Confirm the archive policy is listed.

Method 2: Use PowerShell to Apply the Archive Policy Immediately

1. Install the Teams PowerShell module
   Open Windows PowerShell as an administrator and run Install-Module -Name MicrosoftTeams -Force. Accept the prompt to install from PSGallery.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with your admin credentials.
3. Get the team ID
   Run Get-Team -DisplayName "Your Team Name" to find the GroupId of the new team.
4. Apply the archive policy
   Run Set-TeamArchivalState -GroupId "GroupId" -Archived $true. This immediately archives the team, bypassing the policy schedule.
5. Confirm the archive
   Run Get-Team -GroupId "GroupId" | Select-Object Archived. The output should show True.

Method 3: Trigger a Policy Refresh by Reassigning a Different Policy

1. Open the Teams admin center
   Sign in as a Teams administrator.
2. Select the new team
   Go to Teams then Manage teams. Find the new team and open its settings.
3. Change the policy assignment
   In the Policy tab, change the archive policy to a different one, then save. Wait a few minutes.
4. Revert to the intended policy
   Change the policy back to the one you originally wanted and save again. This triggers a fresh policy evaluation.
5. Verify the policy is now applied
   Check the Policy tab again. The archive policy should now appear as assigned.

If Teams Still Does Not Archive the New Team

Teams Shows the Archive Policy but Does Not Archive After the Set Days

The policy may be assigned, but the archiving job may fail due to a conflict with retention policies. Check your Microsoft 365 compliance center for retention policies that might override the archive action. If a retention policy keeps the team active, the archive policy cannot run. Remove or adjust the retention policy for that team.

The Archive Policy Is Applied to the Wrong Teams

If the policy applies to other teams but not the new one, the policy assignment may be scoped to a specific group. In the Teams admin center, go to Teams then Teams policies. Open the archive policy and check the Assigned teams list. If the new team is missing, use Method 1 to add it manually.

New Teams Created by Users Are Not Affected by the Policy

Users who create teams through the Teams app bypass the policy assignment. To fix this, you can restrict team creation to only admins. Go to Teams then Team settings in the admin center. Under Security, disable the option that allows users to create teams. Then, use PowerShell to create all new teams going forward, which ensures the policy is applied.

New Teams Desktop vs PowerShell Creation: Key Differences

Item	Teams Desktop App	PowerShell Creation
Policy application	May not trigger archive policy	Triggers policy evaluation
Admin control	Limited to post-creation fixes	Full control over policy assignment
Automation	Manual steps required	Can be scripted

You can now force the archive policy to run for any new team using the admin center or PowerShell. Start by checking the policy assignment in the Teams admin center. If that fails, use the PowerShell Set-TeamArchivalState cmdlet to archive the team immediately. For long-term control, restrict team creation to admins and use PowerShell for all new teams. This prevents the issue from recurring.