Excessive Informational Logs from Library During HTTP Requests

I am using the library as shown below and I am flooded from logs coming from the library:

2025-02-11 17:17:37,072 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,119 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,199 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,249 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,330 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,391 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,470 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,516 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,591 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,641 - INFO - ClientSecretCredential.get_token succeeded

How do I make it stop?

async def find_user(client: GraphServiceClient, user_id: str) -> None:

    query_params = UserItemRequestBuilder.UserItemRequestBuilderGetQueryParameters(
		expand = ["manager($levels=max;$select=id,displayName,mail,department,jobTitle)"],
		select = ["customSecurityAttributes","id","displayName","mail","department","jobTitle"],
    )

    request_configuration = RequestConfiguration(
        query_parameters = query_params,
    )

    return await client.users.by_user_id(user_id).get(request_configuration = request_configuration)

Originally posted by @Marcuccio in https://github.com/microsoftgraph/msgraph-sdk-python/discussions/1112

Comece pelo ponto de entrada find_user fornecido e reproduza a saída informativa repetida usando GraphServiceClient e a configuração de requisição mostrada. Rastreie qual componente da biblioteca emite as mensagens de HTTP e de credenciais; o trabalho estará concluído quando a requisição continuar funcionando sem os logs informativos excessivos e o comportamento estiver coberto por uma verificação de regressão adequada.