Chapter 5 of 6
Implement#
1. Complete the decision record#
Fill in every __REQUIRED_...__ value in artifacts/onboarding-decision.json with the owners in the room. Keep the credential itself out of the file.
2. Run preflight#
PowerShell
.\scripts\preflight.ps1 -TargetScope "one-approved-external-agent"Bash
./scripts/preflight.sh --target-scope "one-approved-external-agent"Preflight reads the record. It rejects unresolved decisions, a route it does not recognize, a source reference that is not an absolute HTTP or HTTPS URL or that carries embedded credentials, a credential decision that is incomplete or points into this repository, and a retirement plan that drops a required action. It does not contact Agent 365 or the external platform, so it cannot tell you that a live connection works.
3. Complete the selected route#
| Route | Operator action | Observe before moving on |
|---|---|---|
built-in | The platform operator follows that platform's current enablement or publication path. | The platform shows the agent enabled or published through its Agent 365 integration. |
registry-sync | The Agent 365 administrator opens Agents > All Agents, selects Manage in Connected platforms, creates or reviews the connection, validates the credentials, and runs Sync agents. | The connection names the provider and shows a current sync result. Read the sync errors before expecting anything in Agent Registry. |
sdk | The runtime owner changes the integration in the product repository and deploys it through the approved release path. | The released version is the one meant to register the agent. |
4. Read the live record#
Open Agent Registry with the Agent 365 administrator. Confirm the record is the intended agent, arrived through the selected route, and shows a known owner and lifecycle state.