Share via

Error ColdStoreNotSupportedForMessageException when sending message MS Teams via Graph API.

Kimchhun Tan 0 Reputation points
2026-03-25T10:08:55.6633333+00:00

I'm using the Graph API to send a message to a Microsoft Teams channel, but I'm getting the following error.

Endpoint: https://graph.microsoft.com/v1.0/teams/{team_id}/channels/{channel_id}/messages

Reference: https://learn.microsoft.com/ja-jp/graph/api/chatmessage-post?view=graph-rest-1.0&tabs=http#http-request

Error response:

{
  "code": "NotFound",
  "message": "NotFound",
  "innerError": {
    "code": "1",
    "message": "MessageNotFound-Message does not exist in the thread: ColdStoreNotSupportedForMessageException:ColdStoreMessageOperations is not supported if cutOffColdStoreEpoch is not provided. (msgVersion:1773201279001, cutoff:1773137924398)",
    "date": "2026-03-17T10:18:44",
    "request-id": "7e4d1acd-05d0-4ff6-82ac-4cf0549bfa56",
    "client-request-id": "7e4d1acd-05d0-4ff6-82ac-4cf0549bfa56"
  }
}

I couldn't find any documentation related to ColdStoreNotSupportedForMessageException. Has anyone encountered this before or have any insight into what's causing it?

Microsoft Security | Microsoft Graph
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-25T10:09:08.0833333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error is not documented in the public Microsoft Graph docs, but the behavior around sending messages to Teams via Graph is documented and indicates what is required for a successful call.

    For sending a new message to a channel, only the body property of the chatMessage is mandatory. A valid request looks like this:

    POST https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{channel-id}/messages
Content-type: application/json

{
  "body": {
    "content": "Hello World"
  }
}

    If the request is correctly formed and the channel and team IDs are valid and accessible, the API returns 201 Created and a chatMessage object in the response.

    Given that the error text mentions MessageNotFound-Message does not exist in the thread and ColdStoreMessageOperations is not supported if cutOffColdStoreEpoch is not provided, it is consistent with an internal condition where the service is trying to operate on an existing message (for example, a reply or an operation that assumes a parent message) rather than a simple “create new message” operation. For a pure create operation to a channel, the documented pattern is:

    POST /teams/{team-id}/channels/{channel-id}/messages

    and for replies:

    POST /teams/{team-id}/channels/{channel-id}/messages/{message-id}/replies

    To avoid this error based on the documented behavior:

    1. Ensure the HTTP method and URL match the “create message” pattern (no {message-id} segment) when sending a new top-level message.
    2. When posting a reply, ensure the {message-id} actually exists in the channel and is not deleted or otherwise unavailable.
    3. Ensure the request body at least contains a valid body.content field as shown in the examples.
    4. Confirm that the app has the appropriate permissions for channel messaging (for example, ChannelMessage.Send or other documented least-privilege permissions) when using the Teams messaging APIs.

    If all of the above are correct and the error persists, it is likely an internal service condition related to how older or archived messages are stored (“cold store”) and would require a support case with Microsoft, since there is no public parameter such as cutOffColdStoreEpoch exposed in the documented Graph API for Teams messages.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.