Archive for reference
Archive freezes Team activity while keeping conversations and files searchable. Owners can later restore the Team; the connected SharePoint site can optionally become read-only for members.
Microsoft Teams operations and governance
Microsoft Teams Lifecycle and Archiving Governance Guide
Control the complete Team ecosystem—from purpose, ownership, channels, guests, apps, meetings, and files through periodic review, reversible archive, expiration, retention, deletion, restoration, and evidence.
Ownership and guestsChannel lifecycleArchive and restoreExpirationRetention evidence
Executive purpose
Choose a lifecycle state based on business need—not on a single activity signal
A Team is more than a chat space. It is backed by a Microsoft 365 group and can connect a SharePoint team site, group mailbox and calendar, Planner plans, OneNote, apps, meetings, standard channels, private-channel sites, shared-channel sites, guests, and cross-tenant access. A lifecycle decision therefore affects identity, permissions, communications, content, retention, support, and recovery.
Renew for continued work
Renew when the purpose remains valid, ownership is current, guests are justified, controls still match the data, and the connected workloads remain operationally needed.
Delete only with evidence
Deletion soft-deletes the underlying Microsoft 365 group and Team for 30 days. It is not the same as archive and should follow retention, dependency, and recovery review.
Practical decision rule: Archive when work has stopped but users still need a searchable reference. Renew when work remains active and justified. Delete only when the business owner, records owner, security team, and service owner agree that the workspace and its dependencies can be removed.
Lifecycle architecture
Inventory the connected Team before changing its state
| Component | Lifecycle evidence | Archive or deletion impact | Validation |
|---|---|---|---|
| Team and Microsoft 365 group | Purpose, owners, members, guests, sensitivity, expiration, activity, naming, classification | Archive freezes Team activity; deletion soft-deletes the group-backed ecosystem | Team visibility, owners, membership, settings, label, expiration, and group object |
| Standard channels | Posts, meetings, tabs, connectors, apps, channel owners, file folders | Team archive freezes activity; individual channels can also be archived independently | Search, read-only behavior, favorites, permissions, apps, tabs, and restore |
| Private channels | Separate owners/members, guests, messages, dedicated SharePoint site, retention | Lifecycle is linked to the parent Team but channel membership and site access are distinct | Channel owner, membership, site access, files, compliance copies, and restore timing |
| Shared channels | Internal and external participants, B2B direct connect, invited teams, separate site | Archive and retention must account for cross-tenant users and channel-specific ownership | Cross-tenant access, participant removal, site permissions, messages, and invited teams |
| SharePoint and files | Site activity, sharing links, storage, permissions, sensitivity, retention, legal hold | Optional member read-only state on Team archive; files follow SharePoint retention, not Teams-message retention | Site lock state, owner editing, libraries, links, private/shared channel sites, and holds |
| Apps, bots, workflows, meetings | Installed apps, webhooks, Power Automate, Planner, tabs, scheduled meetings, recordings | Archive can freeze collaboration while integrations or external references persist | Disable or migrate automation, validate recordings and plans, close support dependencies |
Operating model
Move each Team through accountable, reversible stages
Define purpose
Capture sponsor, owners, data type, guests, duration, label, and expected channels.
Apply controls
Set naming, sensitivity, privacy, apps, guest rules, channel types, and retention scope.
Monitor health
Track ownership, activity, guests, sharing, apps, storage, incidents, and service changes.
Attest need
Confirm business purpose, members, external access, label, content, and dependencies.
Renew or archive
Keep active, archive for reference, transfer ownership, or approve controlled deletion.
Validate outcome
Preserve records, remove access, test archive or restore, and retain decision evidence.
Creation gate
- At least two accountable owners where practical
- Clear purpose, duration, data classification, and support route
- Approved standard, private, and shared channel design
- Guest and cross-tenant need documented before access
Periodic review
- Owners and channel owners remain active
- Guests, shared-channel participants, and invited teams remain justified
- Apps, bots, tabs, workflows, and connectors remain approved
- Files, messages, labels, retention, and sharing match business need
Closure gate
- Records and legal-hold requirements confirmed
- Content disposition and migration approved
- External access and integration dependencies removed
- Archive, deletion, restoration deadline, and validation recorded
Archive, expiration, and deletion
Do not use three different controls as if they produce the same result
| Control | Best use | User experience | Recovery and caveats |
|---|---|---|---|
| Archive Team | Inactive work still needed as a searchable reference or likely to resume | Conversations and files become read-only/searchable; Team activity, new posts, channel changes, settings changes, and new apps are frozen | Team owner can restore. Owners can still manage members/roles and delete, renew, or restore; optional SharePoint member read-only leaves owners able to edit. |
| Archive channel | A completed workstream inside an otherwise active Team | Channel activity freezes and remains searchable; retention and deletion policies continue | Team/channel owners restore it. Restoring an archived Team does not automatically restore separately archived channels. |
| Group expiration | Automated cleanup of inactive group-backed Teams with owner renewal | Activity can auto-renew; otherwise owners receive 30-, 15-, and 1-day notices before soft deletion | Deleted Team/group can be restored for 30 days. Team/group expiry dates can take up to 24 hours to synchronize. |
| Manual deletion | Confirmed end of business purpose with approved content and dependency disposition | Team and group-backed resources become unavailable | Restore within the 30-day soft-delete window and validate every connected workload; do not recreate prematurely. |
| Purview retention | Preserve or delete messages/files according to legal, regulatory, and business policy | Users may still lose the visible Team while retained content remains in protected compliance locations | Retention is not an operational archive, backup, or Team restoration mechanism. |
Archive nuance: selecting SharePoint read-only during Team archive restricts members, but Team owners can still edit the site. If the objective is immutable records preservation, use appropriate Purview records and retention controls rather than relying on the archive checkbox alone.
Channels and connected sites
Govern standard, private, and shared channels as different security and lifecycle boundaries
Standard channels
All Team members can normally see standard channels. Files live in folders on the parent Team’s SharePoint site. A channel can be archived independently without archiving the Team.
Private channels
Membership is a subset of the parent Team and the channel has separate ownership and a dedicated SharePoint site. Deleted private channels can be restored for 30 days.
Shared channels
Participants can include people and teams outside the parent Team, including cross-tenant users. Review cross-tenant access, channel ownership, invited teams, site access, and retention together.
Teams manages the lifecycle of private-channel sites. Deleting a private-channel site outside Teams can cause a background job to restore it while the channel remains active. A restored private-channel site beyond the channel’s 30-day recovery window can become a standalone site. Treat orphaned or standalone channel sites as a reconciliation defect—not as evidence that the Team lifecycle succeeded.
Retention and evidence
Messages and files follow separate retention locations and must be tested separately
Teams retention policies can retain or delete channel messages and chats. Files shared in channels are stored in SharePoint; files shared in chats are typically stored in the sender’s OneDrive. Microsoft recommends coordinating Teams retention with Microsoft 365 Groups, SharePoint, and OneDrive retention as needed. An archived Team or channel remains subject to applicable retention and deletion policies.
| Information type | Primary service/location | Lifecycle dependency | Evidence to validate |
|---|---|---|---|
| Standard/shared channel messages | Teams compliance storage associated with group/substrate message data | Teams channel-message retention policy and current private-channel migration behavior | Policy scope, test message, eDiscovery result, retention/deletion timing |
| Private channel messages | Post-migration behavior inherits parent Team retention; legacy storage can differ | Migration state and Teams retention policy configuration | Channel creation date/state, policy location, eDiscovery test, audit result |
| Channel files | Parent or channel-specific SharePoint site | SharePoint/Microsoft 365 Groups retention, labels, holds, recycle bins, sharing | Site URL, policy lookup, library, label, hold, storage, recovery test |
| Chat files and recordings | OneDrive, SharePoint, or meeting/recording storage according to context | User lifecycle, OneDrive retention, meeting policy, sharing, ownership | Owner, location, permissions, retention, transcript/recording access |
| Apps, plans, tabs, workflows | Teams plus connected Microsoft 365 or third-party services | Independent service ownership, credentials, URLs, licensing, data retention | Dependency register, owner, export/migration plan, disablement and recovery test |
Top lifecycle risks
Common failures that make Teams cleanup unsafe
Lifecycle governance fails when administrators act on the Team shell without reconciling its owners, channels, sites, retention, guests, and integrations.
Archive assumed immutable
Archive is reversible and owners may still edit the connected SharePoint site. It is not a records lock or backup.
Expiration assumed archive
Group expiration deletes an unrenewed Team into a 30-day soft-delete state; it does not create a searchable archived Team.
Channel sites overlooked
Private and shared channels can have separate SharePoint sites and membership. Parent-Team review alone is incomplete.
Retention scope incomplete
Teams message retention does not automatically govern SharePoint or OneDrive files. Validate every content location.
Ownerless workspaces
Departed or inactive owners leave renewal, guest review, archive, and recovery decisions without accountable authority.
Integrations abandoned
Apps, bots, webhooks, workflows, scheduled meetings, recordings, and Planner dependencies can outlive the Team decision.
Operations and assurance
Measure whether Teams remain useful, owned, protected, and recoverable
Weekly
- Review impending expiration and soft-deleted Teams
- Resolve ownerless or disputed workspaces
- Track restoration and workload recovery cases
- Investigate abnormal guest or app changes
Monthly
- Reconcile Teams, groups, sites, private/shared channels, and owners
- Review inactive Teams with business owners
- Validate archived Teams and channel exceptions
- Report external access, storage, apps, and lifecycle trends
Quarterly
- Test archive and restore with a safe pilot
- Test soft-delete recovery across connected workloads
- Validate message and file retention independently
- Review policies, roles, runbooks, licensing, and escalation paths
Related ecosystem
Connect Teams lifecycle to the controls that determine safe access and disposition
Groups expiration policyCoordinate Team renewal, activity, owner notices, soft deletion, and restoration.Group naming and classificationMake purpose, ownership, sensitivity, and lifecycle expectations visible at creation.SharePoint site provisioningGovern parent, private-channel, and shared-channel sites, sharing, labels, and ownership.External collaboration settingsReview guests, shared channels, cross-tenant trust, invitations, and sharing controls.Access package lifecycleTime-bound and review access to Teams and groups through entitlement management.Microsoft 365 managed servicesOperate identity, collaboration, support, security, and lifecycle as one service.
Created by Ali Hassani, CISO — 25+ years of IT, cybersecurity, compliance, and infrastructure experience.
Microsoft references
Authoritative lifecycle, channel, retention, and recovery resources
Frequently asked questions
Microsoft Teams lifecycle and archiving FAQ
What happens when a Team is archived?
Team conversations and files become read-only and searchable, and Team activity is frozen. Team owners can still manage members and roles and can delete, renew, or restore the Team. They can optionally make the connected SharePoint site read-only for members while owners retain edit capability.
Is archiving the same as deleting or expiring a Team?
No. Archive is a reversible reference state. Deletion and group expiration place the Team and underlying Microsoft 365 group into a 30-day soft-delete recovery window.
Can an individual channel be archived?
Yes. Standard, private, and shared channels can be archived by eligible owners. Channel archive is independent: restoring an archived Team does not automatically restore channels that were separately archived.
Does a Teams retention policy retain channel files?
Not by itself. Teams retention policies govern chats and channel messages. Channel files are stored in SharePoint, while chat files commonly use OneDrive, so file retention must be configured and validated in those workloads.
How do private channels change lifecycle review?
Private channels have separate owners and members and a dedicated SharePoint site. Review channel membership, site access, files, messages, retention, and recovery rather than relying only on the parent Team inventory.
How long can a deleted Team be restored?
A deleted group-backed Team can normally be restored within Microsoft’s non-customizable 30-day soft-delete window. After restoration, validate the Team, group, membership, standard/private/shared channels, SharePoint sites, files, apps, plans, and other dependencies.
Operate the complete collaboration lifecycle
Build a Teams governance program that can archive, recover, and prove every decision
IT Perfection can inventory Teams and connected sites, correct ownership, review guests and channels, align expiration and retention, document archive and deletion decisions, test recovery, and establish evidence-driven operations for Orange County and Southern California organizations.
This guide is for initial guidance only and does not replace a professional cybersecurity audit, compliance assessment, penetration test, legal/compliance review, Microsoft licensing review, records-management decision, or tenant-specific change-control process.
