Manage lifecycle of teams (archiving and deletion)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
We should define some lifecycle control options for Teams.
So question is about Teams (and folders/resources) cleanup, with reminders up to auto-removal.
###.Some TODO items
- introduce 'archive' feature: don't delete team immediately but freeze and hide, but allow un-archiving by server admins and Team admins.
- Show a popup team owners/admins get when a team is unused for 6 months, offer to archive teams.
- Like we have for admins, we could have an overview in the settings for a specific group - as in, for a department head (aka non-admin) who is responsible for the quota perhapss - showing all team folders part of a group. Could be connected with the "group admin" feature.
###.See:
https://learn.microsoft.com/en-us/entra/identity/users/groups-lifecycle
###.Relation with Governance:
Governance retention labels (should) apply to Teams and their resources, but that should be an add-on, not the core way of managing the lifecycle of teams.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reading the linked Microsoft Entra lifecycle guidance and clarify the scope, permissions, reminders, archiving, deletion, and governance interactions; done should be a decided, implementable lifecycle design with defined behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100