Repository navigation
useMicrosoftOpenTelemetry a365 config does not expose useS2SEndpoint option #154
Description
Summary
The distro Agent365Exporter supports useS2SEndpoint, but the high-level useMicrosoftOpenTelemetry({ a365: { ... } }) API doesn't expose it. For OBO scenarios, you need to use Agent365Exporter directly instead of the high-level API.
// High-level API — no useS2SEndpoint option available
useMicrosoftOpenTelemetry({
a365: {
enabled: true,
tokenResolver: ...,
// useS2SEndpoint not available here
},
});
// Agent365Exporter — useS2SEndpoint is supported
const exporter = new Agent365Exporter({
tokenResolver: ...,
useS2SEndpoint: false, // ✓ works here
clusterCategory: 'prod',
});Request
Expose useS2SEndpoint in the useMicrosoftOpenTelemetry({ a365: { ... } }) config for consistency with the Python and .NET distros:
- Python:
use_microsoft_opentelemetry(a365_use_s2s_endpoint=True/False) - .NET:
o.Agent365.Exporter.UseS2SEndpoint = true/false
Package
@microsoft/opentelemetry v0.1.0-beta.1
Activity
github-actions commentedon May 26, 2026
cc Hector Hernandez (@hectorhdzg) Jackson Weber (@JacksonWeber) Leighton Chen (@lzchen) Nev (@MSNev) Radhika Gupta (@rads-1996) Jeremy Voss (@jeremydvoss)
fpfp100 commentedon May 28, 2026
Verified that
useS2SEndpointis properly wired throughuseMicrosoftOpenTelemetryin v1.0.2:The chain:
A365Options.useS2SEndpoint→A365Configuration→Agent365Exporter({ useS2SEndpoint })→/observabilityServiceendpoint.This was missing in v0.1.0-beta.1 (required manual
Agent365Exporterworkaround) but is fully supported in v1.0.2.