Unable to get more replies via "List of Replies" in Logic App Teams Connector

Question

Unable to get more replies via "List of Replies" in Logic App Teams Connector

Ching-Chuan Chen 10 Microsoft Employee

The "@odata.nextLink" from "List of Replies" in Logic App Teams Connector is a graph API url, we cannot run it in HTTP GET without authorization.

The URL looks in the following format: https://graph.microsoft.com/v1.0/teams/4bc904df-9999-4411-1111-b0183952acd1/channels/19:b6e50b94a0594b50821234563b29@thread.skype/messages/177022984561/replies?$top=50&$skiptoken=MSwwLDE3NzE2MzE3AAAA. (information in url is changed.)

In the case that getting message, it was return a logic app URL and we can run it.

The error message is below:
{

"statusCode": 401,

"headers": {

    "Transfer-Encoding": "chunked",

    "Vary": "Accept-Encoding",

    "Strict-Transport-Security": "max-age=31536000",

    "request-id": "8329754e-9c1d-4de6-bda1-27587b523d07",

    "client-request-id": "8329754e-9c1d-4de6-bda1-27587b523d07",

    "x-ms-ags-diagnostic": "{\"ServerInfo\":{\"DataCenter\":\"West US\",\"Slice\":\"E\",\"Ring\":\"4\",\"ScaleUnit\":\"003\",\"RoleInstance\":\"SJ1PEPF00001C54\"}}",

    "WWW-Authenticate": "Bearer realm=\"\", authorization_uri=\"https://login.microsoftonline.com/common/oauth2/authorize\", client_id=\"-c000\"",

    "Date": "Sat, 14 Mar 2026 03:59:33 GMT",

    "Content-Type": "application/json",

    "Content-Length": "265"

},

"body": {

    "error": {

        "code": "InvalidAuthenticationToken",

        "message": "Access token validation failure. Invalid audience.",

        "innerError": {

            "date": "2026-03-14T03:59:33",

            "request-id": "8329754e-9c1d-4de6-bda1-27587b523d07",

            "client-request-id": "8329754e-9c1d-4de6-bda1-27587b523d07"

        }

    }

}
```}

Naveena Patlolla 9,310 Reputation points Microsoft External Staff Moderator

2026-03-14T04:32:34.28+00:00
Hi Ching-Chuan Chen
Hey there! It sounds like you’re running into the fact that the Teams connector’s “List replies” action hands you back an @odata.nextLink that points at Microsoft Graph, but you can’t just drop that into a plain HTTP GET without the proper Graph auth. Here are a couple of ways to handle it:

Enable built-in pagination

In your Logic App designer, click the “List replies” action’s … menu and choose Settings.

Turn on Pagination and set a sufficiently high threshold (e.g. 500).

The connector will then automatically follow @odata.nextLink and pull in all replies behind the scenes.

Manually loop with the SkipToken parameter

On your first “List replies” call set your normal parameters (e.g. top=50).

Grab the NextLink value (the skip token) from body('List_replies')['@odata.nextLink'].

Wrap things in a Until or For Each loop that runs while that token isn’t empty.

Inside the loop invoke “List replies” again, this time under Advanced options populate the Skip Token field with your dynamic NextLink.

Collect the returned replies and repeat until there’s no more skip token.

Call Graph directly (if you really need to)

Use the HTTP with Azure AD connector (or Azure Function) instead of the built-in Teams connector.

Register an AAD app (or use your Logic App’s managed identity) with https://graph.microsoft.com/.default scope and Teams read permissions (e.g. ChannelMessage.Read.All).

Acquire a bearer token targeting the audience https://graph.microsoft.com/.

Call the raw …/teams/{teamId}/channels/{chanId}/messages/{msgId}/replies?$skiptoken=… URL with that token.

Which approach you choose depends on how much control you need:

For most scenarios, pagination or the SkipToken loop is easiest – you stay inside the Teams connector, no extra auth work, and you get all pages of replies.

If you need to mix in other Graph calls or you want to re-use existing Graph auth, go the HTTP with Azure AD route.

Hope one of these gets you past the 401 and fetching all your replies!

—

References

Overview of Teams connector: https://learn.microsoft.com/en-us/connectors/teams/?tabs=text1%2Cdotnet

Logic Apps connector pagination: use Settings → Pagination in the designer

List of all Logic Apps connectors: https://learn.microsoft.com/connectors/connector-reference/connector-reference-logicapps-connectors

Importing APIs into APIM (for HTTP-trigger tips): https://supportability.visualstudio.com/AzureDev/_wiki/wikis/AzureDev/855104/Azure API Management/Troubleshooting Guides/Creating and Importing APIs/Importing API (Logic, API or Function Apps)
Ching-Chuan Chen 10 Reputation points Microsoft Employee

2026-03-16T02:21:38.5566667+00:00

Hi, @Naveena Patlolla ,

Thank you for your prompt response.

I am using the action, "List replies of a channel message". There is no pagination option in settings to use or the advanced option for skip token field.

For calling graph directly, our organization will not allow us to build such AAD app, so it's dead end for me.
Praveen Kumar Gudipudi 2,275 Reputation points Microsoft External Staff Moderator

2026-03-16T16:47:16.9866667+00:00

Hi Ching-Chuan Chen

What you are experiencing is a limitation of the Microsoft Teams connector in Azure Logic Apps.

The “List replies of a channel message” action internally calls a Microsoft Graph endpoint that supports pagination. When more replies exist than the page size, Graph returns an @odata.nextLink containing a $skiptoken. However, the Teams connector does not expose pagination or a Skip Token parameter for this action in the Logic App designer.

The @odata.nextLink you receive points directly to a Graph API URL. Calling that URL using a normal HTTP action fails with InvalidAuthenticationToken – Invalid audience because the token used by the Teams connector is scoped for the connector service and cannot be reused to call Microsoft Graph directly.

Because of this:

The @odata.nextLink cannot be invoked directly from the Logic App.

The Teams connector currently does not provide a way to retrieve additional pages of replies for this action.

The only supported approach to fetch all replies would be to call the Graph API directly (for example using an HTTP action with Azure AD authentication or managed identity). If your organization does not allow registering an app for Graph access, then unfortunately there isn’t a connector-only workaround at the moment.

3 answers

Your answer

Ching-Chuan Chen 10 Reputation points Microsoft Employee

2026-03-16T02:21:38.5566667+00:00

Hi, @Naveena Patlolla ,

Thank you for your prompt response.

I am using the action, "List replies of a channel message". There is no pagination option in settings to use or the advanced option for skip token field.

For calling graph directly, our organization will not allow us to build such AAD app, so it's dead end for me.
Praveen Kumar Gudipudi 2,275 Reputation points Microsoft External Staff Moderator

2026-03-16T16:47:16.9866667+00:00

Hi Ching-Chuan Chen

What you are experiencing is a limitation of the Microsoft Teams connector in Azure Logic Apps.

The “List replies of a channel message” action internally calls a Microsoft Graph endpoint that supports pagination. When more replies exist than the page size, Graph returns an @odata.nextLink containing a $skiptoken. However, the Teams connector does not expose pagination or a Skip Token parameter for this action in the Logic App designer.

The @odata.nextLink you receive points directly to a Graph API URL. Calling that URL using a normal HTTP action fails with InvalidAuthenticationToken – Invalid audience because the token used by the Teams connector is scoped for the connector service and cannot be reused to call Microsoft Graph directly.

Because of this:

The @odata.nextLink cannot be invoked directly from the Logic App.

The Teams connector currently does not provide a way to retrieve additional pages of replies for this action.

The only supported approach to fetch all replies would be to call the Graph API directly (for example using an HTTP action with Azure AD authentication or managed identity). If your organization does not allow registering an app for Graph access, then unfortunately there isn’t a connector-only workaround at the moment.

Answer 1

I am encountering the same issue.

When making a Teams HTTP request for a parent message ID with more than 100 replies, including the nextLink still results in a response with 0 items.

v1.0/teams/0f81c800-ab73-47fc-81ef-83780bd86a6b/channels/19:abf125b14fec42f28a5ade572efebf5b@thread.tacv2/messages/1772412679940/replies?$top=50&$skiptoken=MSwwLDE3NzI3NjkwOTE4OTI

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#teams('0f81c800-ab73-47fc-81ef-83780bd86a6b')/channels('19%3Aabf125b14fec42f28a5ade572efebf5b%40thread.tacv2')/messages('1772412679940')/replies",
  "@odata.count": 0,
  "value": []
}

Answer 2

Praveen Kumar Gudipudi 2,275 Microsoft External Staff Moderator

Hello Ching-Chuan Chen •

Thank you for the confirmation, Send a Microsoft Graph HTTP request" that can resolve your question.

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

0 comments

Answer 3

Ching-Chuan Chen 10 Microsoft Employee

There is a new action th"Send a Microsoft Graph HTTP request" that can resolve my question.

0 comments

Share via

Unable to get more replies via "List of Replies" in Logic App Teams Connector

3 answers

Your answer