Correct Agent 365 Lifecycle Atlas setup and runtime-integration guidance - #547
Merged
Alejandro Lopez (soyalejolopez) merged 1 commit intoSep 22, 2026
Conversation
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>
Alejandro Lopez (soyalejolopez)
merged commit Sep 22, 2026
d328b6a
into
microsoft:master
3 checks passed
Alejandro Lopez (soyalejolopez)
deleted the
alejanl-microsoft-public-agent-365-atlas-corrections
branch
September 22, 2026 19:20
Contributor
🛰️ PR Sweeper reportRisk: 🟢 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.
The automated guardrails are authoritative and gate the security status. The AI review is advisory and never auto-merges. Thanks for contributing to FastTrack! 🛩️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correct Agent 365 Lifecycle Atlas setup and runtime-integration guidance
Summary
Corrects the Agent 365 Lifecycle Atlas coverage of
a365 setup allruntime configuration and observability, and adds a runtime-integration architecture diagram. All changes are grounded in public Microsoft Learn documentation and the pinned publicmicrosoft/Agent365-devToolssource (commit08e48a9). Only thesetup-allandtelemetrysections changed; navigation, attribution, license, sources bibliography, and all other diagrams are preserved.Corrections
ProjectSettingsSyncHelperusesDeploymentProjectPath, falling back to the configuration-file directory when that path is missing or absent, detects .NET/Node.js/Python, and writesappsettings.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.title/desc. Clarifies that--aiteammateprovisions only the blueprint and permissions during setup and that--agent-registration-onlyis a narrow recovery path.TokenValidation.Enabled = falseand appliesEnableAgent365Exporter ??= false(explicit values preserved); Node.js/Python setENABLE_A365_OBSERVABILITY_EXPORTER=false. Adds that written configuration does not prove the SDK, token validation, or exporter is installed or active.gen_ai.agent.idmust equal the agent's authenticatedappId/ OAuthclient_id(tokenappid/azp) and the ingestion-URLagentId, never the Entra object ID or blueprintappId. Adds per-request identity resolution for shared multi-instance hosts.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.Validation
<section>/<svg>tags balanced.title/desc.node --check; catalog metadata check passes for all resources.1.3.0; updatesCHANGELOG.mdand review dates.Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com