Is GraphServiceClient threadsafe?

Hi,

I am using msgraph sdk to get 'User' details in an application. Initialized the GraphServiceClient for app-only authentication as specified in the tutorial: https://learn.microsoft.com/en-us/graph/tutorials/java-app-only?tabs=aad&tutorial-step=3.

I want to query the 'users' using certain filter and select criteria, e.g.

_appClient.users().get(requestConfig -> {
        requestConfig.queryParameters.filter = "displayName startsWith \'A\'";
        requestConfig.queryParameters.select = new String[] { "displayName", "id", "mail" };
        requestConfig.queryParameters.top = 25;
        requestConfig.queryParameters.orderby = new String[] { "displayName" };
    });

However, this request may happen from the context of different threads.
My queries are:

• Does each thread need to instantiate GraphServiceClient separately, or, can we initialize once and share across threads?
• If _appClient (i.e the instance of GraphServiceClient) can be shared, is it thread-safe or do we need to synchronize access to it?

Any insight will be helpful.

The following artifact versions are used: microsoft-graph (v 6.20.0) and azure-identity (1.14.1).

Commencez par le tutoriel Microsoft Graph Java app-only lié et par l’utilisation de GraphServiceClient pertinente pour microsoft-graph 6.20.0 et azure-identity 1.14.1. Consultez la documentation du dépôt et l’implémentation du client pour obtenir des indications sur le partage d’une même instance entre plusieurs threads. La tâche sera considérée comme terminée lorsqu’il sera clairement documenté si le partage est pris en charge et si les appelants doivent utiliser une synchronisation.