deletedTeam: getAllMessages

Namespace: microsoft.graph


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.

Retrieve all messages across all channels in a deleted team, including text, audio, and video conversations.

To learn more about using the Microsoft Teams export APIs to export content, see Export content with the Microsoft Teams Export APIs.

Note: This API has licensing and payment requirements. It supports both model=A and model=B query parameters. If no model is specified, evaluation mode will be used.


One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Permissions.

Permission type Permissions (from least to most privileged)
Delegated (work or school account) Not supported.
Delegated (personal Microsoft account) Not supported.
Application ChannelMessage.Read.All


Before you call this API with application permissions, you must request access. For details, see Protected APIs in Microsoft Teams.

HTTP request

GET /teamwork/deletedTeams/{deletedTeamId}/channels/getAllMessages

Request headers

Name Description
Authorization Bearer {token}. Required.

Optional query parameters

You can use the model query parameter, which supports the values A and B, based on the preferred licensing and payment model, as shown in the following examples.

GET /teamwork/deletedTeams/{deletedTeamId}/channels/getAllMessages?model=A
GET /teamwork/deletedTeams/{deletedTeamId}/channels/getAllMessages?model=B

If the model parameter is not specified, the evaluation mode will be used.

This method supports the $top query parameter to control the number of items per response and the $filter query parameter with the dateTime range query on lastModifiedDateTime. Other OData query parameters are currently not supported.

Request body

Do not supply a request body for this method.


If successful, this function returns a 200 OK response code and a collection of chatMessage objects in the response body.



The following is an example of a request.



The following is an example of the response.

Note: The response object shown here might be shortened for readability.

HTTP/1.1 200 OK

    "@odata.context": "$metadata#Collection(chatMessage)",
    "@odata.count": 2,
    "@odata.nextLink": "",
    "value": [
            "@odata.type": "#microsoft.graph.chatMessage",
            "id": "1616990417393",
            "replyToId": null,
            "etag": "1616990417393",
            "messageType": "message",
            "createdDateTime": "2021-03-29T04:00:17.393Z",
            "lastModifiedDateTime": "2021-03-29T04:00:17.393Z",
            "lastEditedDateTime": null,
            "deletedDateTime": null,
            "subject": null,
            "summary": null,
            "chatId": null,
            "importance": "normal",
            "locale": "en-us",
            "webUrl": "",
            "policyViolation": null,
            "eventDetail": null,
            "from": {
                "application": null,
                "device": null,
                "conversation": null,
                "user": {
                    "id": "8ea0e38b-efb3-4757-924a-5f94061cf8c2",
                    "displayName": "Robin Kline",
                    "userIdentityType": "aadUser"
            "body": {
                "contentType": "text",
                "content": "Test message"
            "channelIdentity": {
                "teamId": "fbe2bf47-16c8-47cf-b4a5-4b9b187c508b",
                "channelId": "19:d5d2708d408c41d98424c1c354c19db3@thread.tacv2"
            "attachments": [],
            "mentions": [],
            "reactions": []