Add A365 S2S exporter sample

[Nikhil Navakiran (nikhilNava)]

What

Adds a self-contained sample under samples/a365_s2s/ demonstrating how to export Agent 365 (A365) telemetry using the S2S (service-to-service) flow.

Why

The existing samples/a365 samples cover the AI-teammate flow (with an agentic user). This adds the missing S2S scenario, where a service authenticates on its own behalf using its app-registration credentials — there is no agentic user.

What's in it

• S2S token resolver that mirrors the SDK's _create_fic_token_resolver (app -> instance token exchange via MSAL), excluding the agentic-user (user_fic) step, combined with a365_use_s2s_endpoint=True.
• Manual A365 scope classes (InvokeAgent / Inference / ExecuteTool), so the sample needs no LLM.
• uv-managed project (pyproject.toml), .env via python-dotenv (with .env.example), and a placeholder/empty-value guard with friendly errors.
• DEBUG logging scoped to the exporter so developers see the export HTTP status and correlation id, e.g. HTTP 200 success ... Correlation ID: <id> ... "status":"sent".

Testing

Verified end-to-end against the live S2S endpoint: token acquired and HTTP 200 with all sinks reporting sent. The placeholder guard and missing-credential paths were also exercised.

Note: .env (real credentials) and .venv are gitignored and intentionally excluded from this PR.

[github-actions]

Performance comparison

Threshold: regressions >15.0% on gating scenarios fail the build. Higher ops/s is better; positive Δ means the PR is slower.

Scenario	Gating	Baseline (ops/s)	Candidate (ops/s)	Δ %	Status
azure_monitor_log	yes	36,655.5	38,301.0	-4.30%	✅
azure_monitor_span	yes	277,354.0	277,739.2	-0.14%	✅
otel_log	no	44,875.2	45,886.3	-2.20%	✅
otel_span	no	84,118.4	84,189.3	-0.08%	✅

[Copilot]

Pull request overview

Adds a new self-contained sample under samples/a365_s2s/ that demonstrates exporting Agent 365 (A365) telemetry via the service-to-service (S2S) authentication flow, including a custom MSAL-based token resolver and manual scope instrumentation.

Changes:

• Introduces an S2S sample script that configures the A365 exporter for the S2S ingest endpoint and emits representative spans using manual A365 scope classes.
• Adds sample documentation + .env template describing required credentials, runtime toggles, and expected DEBUG exporter output.
• Adds an uv-managed sample project (with lockfile) to make the sample runnable without manual venv setup.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
samples/a365_s2s/s2s_exporter.py	Implements the S2S token resolver and a runnable manual-telemetry scenario configured for the S2S exporter endpoint.
samples/a365_s2s/README.md	Documents prerequisites, setup, execution, and required environment variables for the S2S scenario.
samples/a365_s2s/pyproject.toml	Defines a small uv project with runtime dependencies for the sample.
samples/a365_s2s/.env.example	Provides a template for required env vars and exporter toggles.
samples/a365_s2s/uv.lock	Locks the sample’s dependency set for reproducible installs via uv.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Radhika Gupta (rads-1996)]

I don't think we need to add the .env.example, py.project and uv.lock files, whatever pre-requisites are required should be added to the README. If you look at the other samples, that is how they have been structured,

[Nikhil Navakiran (nikhilNava)]

Superseded by #276. The original PR head is an organization-owned branch that the authenticated author account cannot update (push returns HTTP 403). #276 contains the merged-main, Store-ready all-scope implementation, tests, documentation, and the review fixes discussed here.