Start free trial
Start free trial
How-to 5 steps 3 min read Updated 11 November 2026

How to automate the Microsoft 365 workspace lifecycle

Run every Teams team, site and group from request to archive, with owners deciding at each stage and the record kept.

Torsten Mandelkow Works with
How-to

What is workspace lifecycle automation in Microsoft 365?

Automating the Microsoft 365 workspace lifecycle means every Teams team, SharePoint site and Microsoft 365 group moves through the same stages, from request to archive, under policies that run on a schedule. Owners approve and review at each stage, and inactive workspaces are archived on your rules.

In short

  • A lifecycle has stages: request, use, review, inactivity, archive and deletion.
  • Each stage needs a rule and a named owner who decides.
  • Automate the finding and the routine steps; keep a person's approval on archive and delete.
  • Record every decision so the lifecycle can be evidenced.

Step by step

Five steps put the whole lifecycle under policy.

  1. Start every workspace from a template

    Require requests to use templates that fix the naming, visibility, owners and approvers. A workspace that begins with a named owner is far easier to run through the rest of its life.

    In Rencore:

  2. Review ownership and access on a cycle

    Have owners confirm quarterly that they still own the workspace and that its members and guests are right. Escalate unanswered reviews.

  3. Define and detect inactivity

    Write the inactivity rule for each workspace type and let a policy find matches on every scan. Include Viva Engage communities as well as Teams, sites and groups.

    Tip: Ask the owner whether to keep or archive before anything changes. A reply costs a minute and saves a restore request.

    In Rencore:

  4. Archive, and delete only with approval

    Archive inactive workspaces so content is kept but read-only. Delete after the retention period, with an approval from a named person.

    In Rencore:

  5. Keep the lifecycle record

    Log each request, review, archive and deletion with the reason. That record answers an auditor's question about what happened to a workspace.

Why the lifecycle needs automating

Most organizations control how a workspace starts and nothing about how it ends. Teams, sites and groups are created freely, and without a lifecycle they stay until someone happens to notice. By then nobody remembers why they exist.

Doing this by hand does not scale: finding inactive workspaces, asking each owner and acting on the answer is a repeatable process, which is exactly what automation is for. The point is not to remove people from the decision, but to bring the decision to the owner at the right time.

Connectors in this How-to

Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.

Common questions about workspace lifecycle automation

Which tools automate the Microsoft 365 workspace lifecycle?
Microsoft covers single stages natively: Entra can expire unused groups, SharePoint Advanced Management handles inactive site policies and Purview retains and deletes content. The stages are separate, though. Rencore Governance connects them for Teams, SharePoint sites and Microsoft 365 groups, from templated requests and owner reviews to inactivity policies and automations that archive or delete.
What are the stages of a workspace lifecycle?
Request and approval, so each workspace starts from a template with a named owner; active use, with periodic reviews of ownership and access; inactivity, where unused workspaces are found and the owner is asked; archive, where content is kept but read-only; and deletion, once retention and approval allow it. Each stage needs a rule and an owner.
How should inactivity be defined?
Pick a measurable rule per workspace type and apply it consistently. A common one for Teams is no messages and no SharePoint content changes in six months. For SharePoint sites it can be no use in 90 days. Write the rule down, and ask the owner before acting so a quiet but important workspace is not archived by mistake.
Can archiving and deletion wait for an approval?
Yes, and they should for anything destructive. In Rencore Governance the archive and delete automations each come in a variant that asks a designated approver first and acts only once it is granted; a rejected request leaves the workspace as it is. The archive automation also sets the team's SharePoint site to read-only.
Who should be involved besides IT?
Workspace owners, because they know whether a project is finished, and their managers as the escalation when an owner leaves or does not respond. Compliance should agree the retention and archive rules, and finance gains from the storage that archiving frees. IT runs the process and the policies, it does not decide for every workspace.

Last updated 11 November 2026

About the author

Torsten Mandelkow

Torsten is co-founder and CAA at Rencore. During his time as a SharePoint consultant, he always tried to improve and automate the SharePoint development process, first by creating the SharePoint Software Factory (SPSF), and later by creating the SharePoint code analysis tools, today known as SPCAF. After an intermezzo for 3 years at Microsoft, he is now part of the RENCORE team and is responsible for the further technical development of all our tools.

Related

See the lifecycle from request to archive

We will show how requests, owner reviews, inactivity policies and approved archiving fit together, in a short demo.

Request a demoGet started free
Rencore newsletter

Subscribe to our newsletter

Get the latest insights on governing Microsoft 365, Copilot and AI agents, delivered to your inbox.

Loading form