Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Agent365 Auth token with external 3rd party agents

Aberta
  • Algo errado?
#207 2 comentários 0 reações 1 responsável Ver no GitHub

@ajmfehr já está trabalhando nisso.

Desde 27/3/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

Is your feature request related to a problem?

We are working with one of our customers who is building a third-party (3P) agent hosted on Google Cloud Platform (GCP) outside the Microsoft 365 Agents hosting framework and we want to integrate Agent 365 Observability to send telemetry into the A365 Admin Center. We need guidance on how to obtain the authentication token required by the observability exporter when we don't have access to a TurnContext or the M365 Agents SDK hosting layer
.
The SDK's token_resolver requires a Bearer token for instance from sample code the scope iis https://api.powerplatform.com/.default, but all documented paths obtain this via OBO token exchange through TurnContext.exchange_token() which requires the M365 Agents hosting framework.

These customer agent doesn't run inside that framework, so we have no TurnContext and no incoming Microsoft channel tokens to exchange.

Questions:

Can a 3P external agent use Entra ID client credentials flow (or another method) to independently obtain a valid token for the observability API?
What Entra ID app registration / permissions are needed for this?
Is the SpectraExporterOptions (OTLP sidecar) path an alternative for 3P agents to route telemetry into the Admin Center?

Any guidance or sample on how this can be achieved for externally hosted agents?
Following is the sample I am yet to test but was not sure if the same MSAL generated token method would work, before giving it a shot thought of checking here with the experts. here is that sample code (assumptions here are frontier enrolled, Agent blueprint id registered in Entra):

Priority

High

Describe the solution you'd like

Guidance on how this can be achieved with 3rd party agents.

Describe alternatives you've considered

No response

Available workarounds

No response

Additional context

No response

Code of Conduct
Linguagem predominante
Python
Estrelas
41
Forks
23
Merge médio
19h 58min
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/Agent365-python

Todas as issues de microsoft/Agent365-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.