Clarification on Chat-GetAllMessages() endpoint

Tarun George Koshy 71 Reputation points
2021-09-08T12:49:39.763+00:00

Hi,

This is about the chats-getallmessages endpoint. While using local environment, I am able to fetch the messages through the endpoint. However, in a customers environment it doesn't seem to be working. I can confirm that the necessary permissions(Chat.Read.All and Chat.ReadWrite.All) have been added, the id in /users/{id} is valid and the protected APIs request has been approved. I can't get exact error message/ status code being thrown. Is there any setting which could prevent the request from going through?

On that note, it is mentioned in the documentation of the endpoint that "APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported". Does this mean that beta applications won't return data in "production" applications? If so, I would like to know how an app would be considered production and another not because I couldn't find any information on

Thanks!

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,649 questions
Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
2,870 questions
{count} votes

Accepted answer
  1. Ramjot Singh 861 Reputation points Microsoft Employee
    2021-09-08T18:10:29+00:00

    Has the tenant you are using the app in consented to the application? If not please follow https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/grant-admin-consent

    The beta warning basically says that changes can be made to API. We tend to avoid any breaking changes but they are certainly a possibility in /beta (vs /v1.0 where we do not make such changes, but that also means you might not get new features).

    Apps in themselves are not production or non-production.

    To assists in debugging please log client-request-id and request-id response headers and share with us.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful