Skip to content

Correct Agent 365 Lifecycle Atlas setup and runtime-integration guidance - #547

Merged
Alejandro Lopez (soyalejolopez) merged 1 commit into
microsoft:masterfrom
soyalejolopez:alejanl-microsoft-public-agent-365-atlas-corrections
Sep 22, 2026
Merged

Alejandro Lopez (soyalejolopez) merged 1 commit into
microsoft:masterfrom
soyalejolopez:alejanl-microsoft-public-agent-365-atlas-corrections

Conversation

@soyalejolopez

Copy link
Copy Markdown
Member

Correct Agent 365 Lifecycle Atlas setup and runtime-integration guidance

Summary

Corrects the Agent 365 Lifecycle Atlas coverage of a365 setup all runtime configuration and observability, and adds a runtime-integration architecture diagram. All changes are grounded in public Microsoft Learn documentation and the pinned public microsoft/Agent365-devTools source (commit 08e48a9). Only the setup-all and telemetry sections changed; navigation, attribution, license, sources bibliography, and all other diagrams are preserved.

Corrections

  • Runtime-config synchronization is conditional on project detection, not a flag. The pinned ProjectSettingsSyncHelper uses DeploymentProjectPath, falling back to the configuration-file directory when that path is missing or absent, detects .NET/Node.js/Python, and writes appsettings.json/.env; it skips only when no usable directory or supported project is found. The config-free path can therefore still write configuration; the standard-agent orchestrator deliberately skips sync only for --agent-registration-only.
  • Setup sequence scoped to the default standard-agent, non-AI-teammate path in the visible heading, the in-SVG label, and the accessible title/desc. Clarifies that --aiteammate provisions only the blueprint and permissions during setup and that --agent-registration-only is a narrow recovery path.
  • Language-specific generated defaults. .NET sets TokenValidation.Enabled = false and applies EnableAgent365Exporter ??= false (explicit values preserved); Node.js/Python set ENABLE_A365_OBSERVABILITY_EXPORTER=false. Adds that written configuration does not prove the SDK, token validation, or exporter is installed or active.
  • Observability identity binding. gen_ai.agent.id must equal the agent's authenticated appId / OAuth client_id (token appid/azp) and the ingestion-URL agentId, never the Entra object ID or blueprint appId. Adds per-request identity resolution for shared multi-instance hosts.
  • New "What changes in my code?" runtime-integration diagram (compact, static, accessible title/desc, existing palette) plus an illustrative code-area table describing customer-hosted integration boundaries. Emphasizes that registration establishes a management record and does not take ownership of the executable or auto-intercept operations.
  • Package lifecycle labeled specifically as Microsoft 365 package distribution.

Validation

  • Internal anchors all resolve; <section>/<svg> tags balanced.
  • Edited SVGs parse as well-formed XML and carry title/desc.
  • Inline JavaScript passes node --check; catalog metadata check passes for all resources.
  • Rendered in a headless browser (light and dark) with no content-related console errors.
  • Bumps version to 1.3.0; updates CHANGELOG.md and review dates.

Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com

Update the atlas's �365 setup all and observability content and add a
runtime-integration diagram, grounded in public Microsoft Learn and the pinned
public microsoft/Agent365-devTools source.

- Runtime-config sync depends on detecting a supported project (with a config-file
  directory fallback), not on a project-path flag; only --agent-registration-only
  deliberately skips it, so the config-free path can still write configuration.
- Scope the setup sequence diagram, heading, and accessible description to the
  default standard-agent, non-AI-teammate path; clarify --aiteammate provisions
  only the blueprint and permissions during setup.
- Clarify language-specific generated defaults: .NET TokenValidation.Enabled=false
  and EnableAgent365Exporter ??= false (explicit values preserved); Node.js/Python
  ENABLE_A365_OBSERVABILITY_EXPORTER=false; written config is not proof the SDK,
  token validation, or exporter is active.
- Bind gen_ai.agent.id to the agent's authenticated appId / OAuth client_id, never
  the Entra object or blueprint ID; add per-request identity resolution for shared
  multi-instance hosts.
- Add a "What changes in my code?" runtime-integration architecture diagram and
  illustrative code-area table describing customer-hosted integration boundaries.
- Label the package lifecycle as Microsoft 365 package distribution.
- Bump version to 1.3.0 and update the changelog and review dates.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@soyalejolopez
Alejandro Lopez (soyalejolopez) merged commit d328b6a into microsoft:master Sep 22, 2026
3 checks passed
@soyalejolopez
Alejandro Lopez (soyalejolopez) deleted the alejanl-microsoft-public-agent-365-atlas-corrections branch September 22, 2026 19:20
@github-actions

Copy link
Copy Markdown
Contributor

🛰️ PR Sweeper report

Risk: 🟢 LOW · Security gate: ✅ passing · Files: 3

🔒 Automated guardrails (authoritative)

No secret, PII, file-policy, or scope issues detected. ✅

🤖 Dual-model AI review (advisory)

AI review unavailable for this run (models not reachable or no diff). Guardrails above are unaffected.

  • GPT-class reviewer (openai/gpt-5): skipped — request failed: Unexpected token 'O', "OK
    " is not valid JSON
  • Deep-reasoning reviewer (openai/o3): skipped — request failed: Unexpected token 'O', "OK
    " is not valid JSON

The automated guardrails are authoritative and gate the security status. The AI review is advisory and never auto-merges. Thanks for contributing to FastTrack! 🛩️

@github-actions github-actions Bot added the sweeper:risk-low PR Sweeper: low risk label Sep 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sweeper:risk-low PR Sweeper: low risk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant