If you created a new team and set its expiration policy, the expiration date may not renew as expected. This usually happens when the policy assignment is missing or the renewal process fails silently. The expiration policy in Teams relies on Microsoft 365 group lifecycle rules. This article explains why a newly created team ignores the renewal and how to force a correct renewal.
You will learn the exact steps to check policy assignment, trigger a manual renewal, and verify the new expiration date. The guide also covers common failure patterns, such as teams that show a past expiration date or renewal errors in the audit log.
Key Takeaways: Fixing Expiration Renewal for New Teams
- Teams admin center > Teams > Manage teams: Check the expiration date of the new team to see if it matches the policy.
- Microsoft 365 admin center > Groups > Expiration: Verify that the expiration policy is enabled and assigned to the correct group type.
- Microsoft Graph API (renewGroup): Manually renew a team’s expiration date when the automatic renewal fails.
Why a New Team Does Not Renew Its Expiration Date
Teams expiration is controlled by the Microsoft 365 group expiration policy. This policy applies to all groups in your tenant, but new teams may not inherit it immediately. The renewal process runs daily and checks each group’s last activity. If the group has no recent activity, the policy sends a notification and then deletes the group after the grace period.
A newly created team has a creation date that becomes its initial expiration date. The renewal only happens if the group has activity that counts as renewal. Activities that count include file edits, SharePoint access, or any user interaction with the team. If the team is empty or has no activity, the expiration date stays fixed and the team may be deleted after the policy period passes.
Policy Assignment Delay
When you create a new team, the expiration policy assignment may take up to 24 hours to apply. During this time, the team shows no expiration policy or a default date. After the assignment, the expiration date is set based on the current date plus the policy duration. If you check before the assignment, you may see the wrong date.
Renewal Trigger Requirements
The renewal process requires at least one activity that counts as renewal. Activities include any user visiting the team, uploading a file, or posting a message. If the team is created but never used, the system will not renew it. The only way to prevent deletion is to manually renew the group or add activity.
Steps to Force Renewal for a Newly Created Team
- Check the current expiration date
Go to Teams admin center > Teams > Manage teams. Select the new team and view the Expiration date column. If the date is missing or wrong, proceed to the next step. - Verify the expiration policy assignment
Open Microsoft 365 admin center > Groups > Expiration. Confirm that the policy is enabled and applies to all groups or to the specific group type. If the policy is set to All groups, it should apply to the new team. - Wait for policy propagation
If the team was created less than 24 hours ago, wait for the policy to assign. Check the expiration date after 24 hours. If the date still does not change, continue to manual renewal. - Manually renew the group using Microsoft Graph
Use Graph Explorer or PowerShell to call the renewGroup endpoint. For PowerShell, runSet-AzureADMSGroup -Id. This forces the expiration date to reset to today plus the policy duration.-RenewedDateTime $null - Add activity to the team
Have a user post a message, upload a file, or access the SharePoint site. This activity triggers the automatic renewal on the next daily cycle. - Verify the new expiration date
After manual renewal or activity, check the expiration date again in Teams admin center. It should show a date equal to today plus the policy duration, for example 365 days if the policy is set to one year.
If the Team Still Shows the Wrong Expiration Date
Teams Shows an Expiration Date in the Past
A past expiration date means the renewal did not run. Check the audit log for the group renewal events. Go to Microsoft 365 admin center > Audit > Search. Look for the event name Renew group. If no event exists, the renewal failed. Run the manual renewal again and verify the group ID is correct.
Renewal Fails with a Policy Error
If the manual renewal returns an error, the group may be excluded from the policy. Check if the group has a custom expiration policy that overrides the tenant policy. Go to Microsoft 365 admin center > Groups > Active groups, select the group, and view the Expiration section. If it shows No expiration, the group is excluded. Change it to Use default policy.
New Team Created from a Template Does Not Renew
Teams created from a template may have a different creation date or a disabled renewal flag. Check the group settings in Azure AD. The property renewedDateTime must be set to the current date. If it is null, run the manual renewal command.
Teams Admin Center vs Microsoft Graph for Expiration Renewal
| Item | Teams Admin Center | Microsoft Graph API |
|---|---|---|
| Access | GUI, no scripting required | Requires PowerShell or Graph Explorer |
| Renewal action | Not available, only view expiration date | Supports renewGroup endpoint |
| Policy assignment | Shows effective policy, but cannot change it | Can change expiration policy via group settings |
| Best for | Quick verification | Automated renewal and troubleshooting |
Conclusion
You can now force a renewal for a new team that ignores its expiration policy. Use the Teams admin center to verify the date and the Microsoft Graph renewGroup endpoint to reset it. Always add activity to the team so the automatic renewal works in the future. For advanced control, create a scheduled PowerShell script that renews all teams with a past expiration date. This prevents accidental deletion of unused teams.