Teams Lifecycle

Teams Lifecycle Management

This skill provides comprehensive knowledge for managing the full lifecycle of Microsoft Teams — from creation with templates to archival — using Graph API. It includes non-technical language mapping for project-oriented users.

Base URL

https://graph.microsoft.com/v1.0

All endpoints below are relative to this base URL unless noted.

API Endpoints

Team Management

Channel Management

Member Management

Templates

Activity & Reporting

Group Settings (Naming Policy, Expiration)

Non-Technical Language Mapping

Team Creation

Create Team from Template

POST /teams
{
  "template@odata.bind": "https://graph.microsoft.com/v1.0/teamsTemplates('standard')",
  "displayName": "PRJ-Marketing-Campaign-2026",
  "description": "Marketing campaign project team",
  "visibility": "private",
  "members": [
    {
      "@odata.type": "#microsoft.graph.aadUserConversationMember",
      "roles": ["owner"],
      "user@odata.bind": "https://graph.microsoft.com/v1.0/users('{ownerId}')"
    }
  ]
}

Response: 202 Accepted with Location header containing the async operation URL. Poll until completed.

Built-in Templates

Clone Team Body

POST /teams/{teamId}/clone
{
  "displayName": "PRJ-Marketing-Campaign-2026-v2",
  "description": "Cloned from Q1 campaign team",
  "visibility": "private",
  "partsToClone": "apps,tabs,settings,channels,members"
}

partsToClone values: apps, tabs, settings, channels, members (comma-separated).

Response: 202 Accepted — asynchronous. Poll the Location header URL.

Create Channel Body

POST /teams/{teamId}/channels
{
  "displayName": "Design Review",
  "description": "Channel for design review discussions",
  "membershipType": "standard"
}

membershipType values: standard (visible to all team members), private (invite-only), shared (cross-team shared channel).

Team Settings Reference

Update Team Settings

PATCH /teams/{teamId}
{
  "memberSettings": {
    "allowCreateUpdateChannels": true,
    "allowDeleteChannels": false,
    "allowAddRemoveApps": true,
    "allowCreateUpdateRemoveTabs": true,
    "allowCreateUpdateRemoveConnectors": true
  },
  "guestSettings": {
    "allowCreateUpdateChannels": false,
    "allowDeleteChannels": false
  },
  "messagingSettings": {
    "allowUserEditMessages": true,
    "allowUserDeleteMessages": true,
    "allowOwnerDeleteMessages": true,
    "allowTeamMentions": true,
    "allowChannelMentions": true
  },
  "funSettings": {
    "allowGiphy": true,
    "giphyContentRating": "moderate",
    "allowStickersAndMemes": true,
    "allowCustomMemes": false
  },
  "discoverySettings": {
    "showInTeamsSearchAndSuggestions": true
  }
}

Settings Boolean Reference

Sensitivity Labels

Apply Label to Team

PATCH /groups/{groupId}
{
  "assignedLabels": [
    {
      "labelId": "{sensitivityLabelId}"
    }
  ]
}

Common Labels for Teams

Naming Policy

Prefix/Suffix Convention

[Type]-[Department]-[Name]-[Year]

Examples: PRJ-Marketing-Campaign-2026, DEP-Finance-General, TMP-Hiring-Sprint

Check Naming Policy

GET /groupSettings

Look for CustomBlockedWordsList and PrefixSuffixNamingRequirement in the directory settings template Group.Unified.

Archival

Archive Team

POST /teams/{teamId}/archive
{
  "shouldSetSpoSiteReadOnlyForMembers": true
}

Makes the team read-only. Content is preserved but no new messages or files can be added.

Unarchive Team

POST /teams/{teamId}/unarchive

Expiration Policy

Set Group Expiration

PATCH /groupLifecyclePolicies/{policyId}
{
  "groupLifetimeInDays": 180,
  "managedGroupTypes": "Selected",
  "alternateNotificationEmails": "admin@contoso.com"
}

managedGroupTypes values: None, Selected, All.

Activity Report Schema

GET /reports/getTeamsTeamActivityDetail(period='D30')

Returns per-team: teamName, lastActivityDate, activeUsers, activeChannels, channelMessages, postMessages, replyMessages, urgentMessages, meetings, audioDuration, videoDuration.

Ownership Enforcement

Check Owners

GET /groups/{groupId}/owners

Flag teams with:

• Zero owners (orphaned)
• Only one owner (single point of failure)
• Owners who have left the organization

Add Owner

POST /groups/{groupId}/owners/$ref
{
  "@odata.id": "https://graph.microsoft.com/v1.0/users/{userId}"
}

Required Permissions

Error Handling

Async Operation Handling

Team creation and cloning return 202 Accepted. Poll the Location header URL:

GET {operationUrl}

Status values: notStarted, running, succeeded, failed.

Wait for succeeded before accessing the new team. Typical creation time: 10-30 seconds.

OData Filter/OrderBy Examples

# Teams with specific display name prefix
/groups?$filter=startswith(displayName,'PRJ-') and resourceProvisioningOptions/Any(x:x eq 'Team')

# Teams without owners
/groups/{groupId}/owners/$count  (returns 0 = orphaned)
Header: ConsistencyLevel: eventual

# Activity report for last 30 days, sorted by last activity
/reports/getTeamsTeamActivityDetail(period='D30')

Common Lifecycle Patterns

Pattern 1: Project Kickoff

1. POST /teams — create team from template with naming convention
2. POST /teams/{id}/channels — create project-specific channels (Design, Dev, Testing)
3. POST /teams/{id}/members — add team members
4. POST /groups/{id}/owners/$ref — ensure at least 2 owners
5. PATCH /groups/{id} — apply sensitivity label matching project classification
6. Document team in project registry

Pattern 2: Monthly Governance Review

1. GET /reports/getTeamsTeamActivityDetail(period='D30') — get activity for all teams
2. Flag teams with zero activity in 30 days as stale candidates
3. GET /groups/{id}/owners — check owner health for all teams
4. Flag orphaned teams (0 owners) and single-owner teams
5. Generate governance report with action items for team owners
6. Send notifications to owners of stale/at-risk teams

Pattern 3: Project Closeout

1. GET /teams/{id} — verify team status and activity
2. Export important files from SharePoint site if needed
3. POST /teams/{id}/archive with shouldSetSpoSiteReadOnlyForMembers: true — archive
4. Update project registry with archive date
5. Add to expiration policy for automated deletion after retention period

Pattern 4: Team Template Standardization

1. GET /teamwork/teamTemplates — inventory existing templates
2. Create reference team with standard channels, tabs, and apps
3. POST /teams/{id}/clone — clone reference team for new projects
4. PATCH /teams/{newId} — update display name, description, and settings
5. PATCH /groups/{newId} — apply appropriate sensitivity label
6. Document template usage in governance guide

Pattern 5: Orphaned Team Remediation

1. List all teams: GET /groups?$filter=resourceProvisioningOptions/Any(x:x eq 'Team')&$select=id,displayName
2. For each team: GET /groups/{id}/owners — check owner count
3. Flag teams with 0 owners as orphaned
4. For each orphaned team: identify most active member from activity report
5. POST /groups/{id}/owners/$ref — assign new owner
6. Notify new owner and document change

Progressive Disclosure — Reference Files