Agent365 Auth token with external 3rd party agents
@ajmfehr ci sta già lavorando.
Dal 27/3/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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
- I agree to follow the Microsoft Open Source Code of Conduct.
- Lingua principale
- Python
- Stelle
- 41
- Fork
- 23
- Merge medio
- 7h 43m
- PR unite (30g)
- 3
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/Agent365-python
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
microsoft/Agent365-python#249 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 78/100
microsoft/Agent365-python#271 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
microsoft/Agent365-python#270 ·
-
[python/agent-framework/sample-agent] Sample dependencies are inconsistent on PyPI — cannot run Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
microsoft/Agent365-python#262 ·
-
microsoft/Agent365-python#257 · 2 commenti · 1 assegnatario ·
Tutte le issue di microsoft/Agent365-python
Issue simili
-
link-check link-check:sphinx-theme
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
OpenHands/extensions#626 · 1 commento ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
CSCfi/sd-search-api#39 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100