Agent365 Auth token with external 3rd party agents
@ajmfehr arbeitet bereits daran.
Seit 27.3.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
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.
- Vorherrschende Sprache
- Python
- Sterne
- 41
- Forks
- 23
- Ø Merge
- 7 Std. 43 Min.
- Gemergte PRs (30 T.)
- 3
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus microsoft/Agent365-python
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
microsoft/Agent365-python#249 ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 78/100
microsoft/Agent365-python#271 ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
microsoft/Agent365-python#270 ·
-
[python/agent-framework/sample-agent] Sample dependencies are inconsistent on PyPI — cannot run Offen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 38/100
microsoft/Agent365-python#262 ·
-
microsoft/Agent365-python#257 · 2 Kommentare · 1 zugewiesene Person ·
Alle Issues in microsoft/Agent365-python
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
stephrobert/dsoxlab#238 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
sublimehq/package_control#1780 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
nwg-piotr/nwg-displays#145 ·