Archive team

Namespace: microsoft.graph

Important

APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

Archive the specified team. When a team is archived, users can no longer make most changes to the team. For example, users can no longer: send or like messages on any channel in the team; edit the team's name or description; nor edit other settings. However, membership changes to the team continue to be allowed.

Archiving is an async operation. A team is archived once the async operation completes successfully, which can occur subsequent to a response from this API.

To archive a team, the team and group must have an owner.

To restore a team from its archived state, use the API to unarchive.

This API is available in the following national cloud deployments.

Global service US Government L4 US Government L5 (DOD) China operated by 21Vianet

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

This API supports admin permissions. Microsoft Teams service admins can access teams that they aren't a member of.

Permission type Least privileged permissions Higher privileged permissions
Delegated (work or school account) TeamSettings.ReadWrite.All Directory.ReadWrite.All, Group.ReadWrite.All
Delegated (personal Microsoft account) Not supported. Not supported.
Application TeamSettings.ReadWrite.Group Directory.ReadWrite.All, Group.ReadWrite.All, TeamSettings.ReadWrite.All

Note

  • The TeamSettings.ReadWrite.Group permission uses resource-specific consent.
  • The Group.ReadWrite.All and Directory.ReadWrite.All permissions are supported only for backward compatibility. We recommend that you update your solutions to use an alternative permission listed in the previous table and avoid using these permissions going forward.

HTTP request

POST /teams/{id}/archive

Request headers

Header Value
Authorization Bearer {token}. Required. Learn more about authentication and authorization.

Request body

In the request, you can optionally include the shouldSetSpoSiteReadOnlyForMembers parameter in a JSON body, as follows.

{
    "shouldSetSpoSiteReadOnlyForMembers": true
}

This optional parameter defines whether to set permissions for team members to read-only on the SharePoint Online site associated with the team. Setting it to false or omitting the body altogether results in this step being skipped.

Response

If archiving is started successfully, this method returns a 202 Accepted response code. The response also contains a Location header, which contains the location of the teamsAsyncOperation that was created to handle archiving of the team. Check the status of the archiving operation by making a GET request to this location.

Example

Request

The following example shows a request.

POST https://graph.microsoft.com/beta/teams/{id}/archive

{

}

Response

The following example shows the response.

HTTP/1.1 202 Accepted
Location: /teams({id})/operations({opId})
Content-Type: text/plain
Content-Length: 0