Microsoft Teams Lifecycle Management
Govern the entire workspace lifecycle - from creation through detecting inactive teams to orderly decommissioning. Rule-based per template, with owner notification before every action. Part of the Valprovia Governance module (Standard tier).
Basics
What is lifecycle management in Microsoft Teams?
Lifecycle management governs the entire lifecycle of a workspace - from creation through inactive phases to final deletion. Rules are defined per template; every workspace created from it inherits them automatically. Project teams can be decommissioned after 365 days, department teams after 90 days of inactivity. Available for Microsoft Teams and SharePoint site collections.
A trigger defines when counting starts: creation date, inactivity, or a metadata date field. Inactivity is detected by default via the O365 Teams Activity Report (messages, channel posts, file uploads and edits, meetings) - each activity resets the countdown. For more granular criteria, Extended Archiving uses KQL queries against the SharePoint search index, e.g. a specific library or metadata field.
The lifecycle runs in three stages: soft archiving (read-only), hard archiving (team hidden) and deletion - the stages cascade automatically. The read-only decommissioning itself is covered by Microsoft Teams archiving. The permanent offload of inactive files into your own Azure Blob Storage is handled by the separate Valprovia Archive module. Part of preventive Microsoft Teams governance.
Frequently asked questions about lifecycle management in Microsoft Teams
-
How does Valprovia detect that a team is inactive?
By default via the O365 Teams Activity Report (messages, posts, file uploads and edits, meetings) through Microsoft Graph. Optionally via SharePoint search KQL queries for granular criteria. Every detected activity resets the inactivity countdown.
-
What lifecycle actions are there?
Three stages: soft archiving (workspace read-only, stays visible), hard archiving (Teams only - users removed, team hidden, documents read-only via SharePoint) and deletion. The stages cascade automatically based on the deadlines configured per template.
-
Am I notified before an automatic action?
Yes. Before every automatic action all owners receive emails in up to three configurable stages (e.g. 30, 15 and 1 day before) with the workspace name, the planned date and a link to postpone.
-
Can owners postpone an action?
Yes, if allowed in the template - via the postpone link in the notification. The number of postponements can be capped by a Max Extension Count; when postponed, the following dates are recalculated proportionally.
-
Can I set different rules for different team types?
Yes. Lifecycle rules are configured per template; each workspace inherits its template's rules - e.g. project teams after 365 days, department teams after 90 days of inactivity.
-
Does lifecycle management also apply to SharePoint sites?
Yes, for SharePoint site collections - without the hard-archiving stage, since soft archiving already achieves full read-only access there.
The workspace lifecycle, automated and under control
See how Valprovia Governance detects inactive teams and decommissions them in an orderly way. Talk to one of our experts.