The Problem: Why Do Hundreds of Unused Teams Accumulate in Organizations?
Enterprise environments frequently contain significant numbers of inactive Microsoft Teams workspaces. These "ghost Teams" consume storage, maintain active permissions, and create security and compliance risks. Microsoft's Advanced Collaboration Analytics now includes an "Inactive Teams" view, acknowledging this systemic issue. The sprawl from 2020–2021 remote work expansion remains unresolved in many organizations.
The core challenge: IT teams lack reliable signals to distinguish genuinely inactive workspaces from active ones. Native Microsoft reports show activity where no productive work occurs. Without precise data, automated archiving rules don't trigger, and manually reviewing hundreds of Teams isn't realistic. This sprawl creates uncontrolled licensing costs, expanded attack surfaces from abandoned permissions, and potential compliance violations.
How Does Microsoft's Inactivity Detection Work Today?
Microsoft's Teams Activity Report — available via the Microsoft 365 Admin Center — records every Teams client interaction as activity: chat messages, channel posts, replies, reactions, mentions, meeting attendance, calls, and file shares.
Why Is This Definition Problematic?
The weakness lies in breadth. Microsoft measures activity through communication metrics, not productivity metrics. A team with one monthly reaction equals a team with daily project work. Automated notifications, system messages, and bot interactions also generate signals. Even opening a channel counts as activity in some cases.
What Is Missing from Microsoft's Native Reports?
According to Practical365, the Teams Usage Report for identifying inactive Teams is "simply not good enough." Microsoft only shows 28-day data. Teams inactive beyond 90 days disappear from reports, yet minimally active teams remain visible and incorrectly classified as "in use."
The report doesn't answer: Was the SharePoint library actually used for document work? Were files edited, content updated, deliverables created? These questions often matter more for archiving decisions than chat messages.
How Does Valprovia Governance Solve This Problem?
Valprovia Governance offers Extended Archiving with SharePoint Search Queries — a second, more precise method alongside standard inactivity detection.
Instead of asking "Did someone write in Teams chat?", Extended Archiving asks: "Has the SharePoint library actually been used for document work?" The answer comes from the SharePoint Search Index, queried with KQL (Keyword Query Language) — SharePoint's native query language.
What Is Measured?
Extended Archiving checks date-related SharePoint properties such as `LastModifiedTime` (when was the last document edited?) or `LastItemModifiedDate` (when was the library last modified?). These properties reflect actual document work, regardless of Teams chat activity.
How Is It Configured?
Administrators configure Extended Archiving in the Valprovia Governance administration interface per Provisioning Solution using three settings:
| Setting | What It Does | Example |
|---|---|---|
| Managed Property | Defines which SharePoint property is checked | `LastModifiedTime` |
| Search Query | Defines the KQL query against SharePoint Search Index | `LastModifiedTime>2025-01-01` |
| Fallback Period | Protects new workspaces without documents from immediate archiving | 90 days |
What Happens Automatically?
Valprovia Governance automatically and regularly checks all workspaces against the configured KQL query. When a workspace reaches the inactivity threshold — meaning no document in the SharePoint library has been edited since the configured period — the archiving process starts automatically.
Before archiving, workspace owners receive up to three configurable notification stages. Owners can postpone archiving if the administrator enables this option.
Extended Archiving vs. Standard Inactivity Detection: A Comparison
| Criterion | Standard (O365 Activity Report) | Extended Archiving (SharePoint Search) |
|---|---|---|
| Data source | Microsoft Graph API — Teams Activity Report | SharePoint Search Index — KQL Queries |
| What counts as activity | Chats, reactions, meetings, calls, file shares | Actual document changes in SharePoint |
| Granularity | Team level (all communication) | Library level (specific document properties) |
| Configurability | None — Microsoft defines what "active" means | Fully configurable via KQL queries and Managed Properties |
| Typical issue | False positives: Teams appear active through chat despite no productive work | Only measures what is configured — precise and traceable |
Both methods can be activated in parallel. The standard method suits Teams where communication is primary — departmental teams or community channels. Extended Archiving better serves project-based workspaces where document work indicates actual activity.
Microsoft Inactivity vs. Valprovia Extended Archiving: The Full Comparison
| Aspect | Microsoft (native) | Valprovia Governance |
|---|---|---|
| What is measured? | Chats, reactions, meetings, calls, file shares | Actual document changes in SharePoint |
| Activity definition | Fixed by Microsoft — not changeable | Freely configurable via KQL queries and SharePoint Managed Properties |
| Detection accuracy | High false positive rate: chat activity masks missing productivity | Precise: measures only the document work that actually occurs |
| Reporting period | Last 28 days — no historical data | Unlimited — SharePoint Search Index stores modification data permanently |
| Automatic archiving | Not natively available — manual action only | Fully automated with configurable rules, notifications, and postponement |
| Notifications before archiving | Not available | Up to three stages, configurable by time unit and interval |
| Owner postponement | Not possible | Configurable: number of postponements and duration per postponement |
| Protection for new workspaces | Not relevant — no archiving | Fallback period protects new workspaces without documents |
| Standalone SharePoint Sites | Not covered — report applies to Teams only | Fully supported — same rules for Teams and SharePoint Sites |
| Compliance & audit | No traceable archiving decision | Objective, auditable criterion: "No document change for X days" |
| IT effort | Manual: export reports, check workspaces individually | Automated: configure the rule once, runs independently |
What Concrete Benefits Does Extended Archiving Provide?
More Precise Detection of Inactive Workspaces
Extended Archiving identifies workspaces that Microsoft's Activity Report overlooks — because occasional chat activity skews detection. The archiving decision bases on actual SharePoint content use, not communication metrics.
Reduced Manual Effort for IT Teams
Without Extended Archiving, administrators manually review workspaces to distinguish real projects from ghost Teams. With automated SharePoint-based detection, this effort disappears — archiving runs rule-based and traceably.
Auditable Archiving Decisions
In regulated industries such as financial services or healthcare, archiving decisions must be traceable and auditable. "The SharePoint library has not been edited in 180 days" is an objective, verifiable criterion. "The team had no chat activity in the last 28 days" is not.
Full Control Over the Activity Definition
Microsoft's Activity Report dictates what counts as activity — administrators have no influence. With Extended Archiving, you decide: Which SharePoint property is relevant? Which period qualifies as inactive? Which KQL query reflects your organization's business reality?
Cost Control Through Targeted Cleanup
Every inactive workspace consumes SharePoint storage quota and Microsoft 365 license resources. Extended Archiving makes visible the workspaces that consume storage without productive use — and archives them automatically.
Which Scenarios Is Extended Archiving Particularly Suited For?
Project-Based Workspaces
Project teams typically have an active phase with intensive document work, followed by occasional chat communication. Standard detection keeps the team "alive" through chat activity, even when the project is complete. Extended Archiving detects that no file has been edited for weeks and initiates archiving.
Compliance-Driven Environments
In industries with strict retention requirements, workspaces must be demonstrably archived after project completion. Archiving decisions based on actual document activity are auditable and meet internal and external auditor requirements.
SharePoint-Heavy Working Styles
Many teams use SharePoint as their primary work tool, while Teams communication happens via private chats or other channels. In these cases, SharePoint activity reflects actual usage far more accurately than the Teams Activity Report.
What Happens When a Workspace Has No Documents Yet?
When SharePoint search returns no results for a workspace — for example, because it was recently created and contains no documents — the configured fallback period kicks in, defining a grace period in days.
A fallback of 90 days means: a new workspace has at least 90 days before inactivity archiving can apply — even if no documents were ever uploaded. This mechanism prevents empty or freshly created workspaces from being archived immediately and gives teams sufficient time to start their project.
Frequently asked questions about archiving by document activity
-
Which SharePoint properties can I use for the query?
Valprovia Governance supports all Managed Properties available in the SharePoint Search Schema. The most common ones for lifecycle management are LastModifiedTime (last document edit), LastItemModifiedDate (last modification in a library), and Created (creation date). Custom Managed Properties are also usable if configured as queryable in the SharePoint Search Schema.
-
Does Extended Archiving also work for standalone SharePoint Sites?
Yes, Extended Archiving works for both Teams-connected workspaces and standalone SharePoint Sites. Valprovia Governance checks all workspaces of a Provisioning Solution against the configured KQL query, regardless of workspace type.
-
Can workspace owners prevent archiving?
Yes, provided the administrator has activated the postponement feature. Workspace owners are notified in up to three stages before archiving and can postpone archiving by a configurable period. The maximum number of postponements is also adjustable.
-
What happens after archiving — can workspaces be restored?
Yes, Valprovia Governance supports full restoration for all archiving stages. Upon restoration, all lifecycle settings are recalculated based on current configuration, including Extended Archiving parameters.
-
Why is Microsoft's native Teams Activity Report not enough for inactivity detection?
Microsoft's Teams Activity Report measures activity through communication metrics, not productivity metrics: a single chat, reaction, or meeting attendance already counts as activity, so a team with minimal, non-productive activity appears "in use." The report also only shows the last 28 days. Extended Archiving instead bases the decision on actual SharePoint document activity, measured through KQL queries.
Summary
Microsoft's native Teams Activity Report measures communication, not productivity — keeping Teams artificially active that should have been archived long ago. Extended Archiving in Valprovia Governance restores control: archiving decisions base on actual SharePoint document activity, configurable via KQL queries and fully automated.
Learn more about Valprovia Governance and automated lifecycle management →
