Control objective

Onboard one existing external agent into Microsoft Agent 365 through a supported route. Record the
route, credential, owner, and retirement decisions, then review the live Agent Registry record.

Why it matters

Problem. Agents built outside the Microsoft ecosystem run on their own platforms. Nobody in the
tenant can say which of them exist, who owns them, or how they get retired.

Solution. Onboarding puts the agent in the same registry as Microsoft-built agents. The runtime
owner keeps maintaining the agent through its existing source.

Architecture at a glance

The decision record holds what the registry does not: the chosen route, the credential owners, and
the retirement plan.

Choose a route the runtime supports

Stop if no route fits the runtime. Try built-in and Registry sync before adding code.

Sequencing with Agent 365 access-boundary control

Built-in means the agent is already in Agent Registry, so Agent 365 data controls can come first.

Registry sync and the SDK create the registry record here. The access-boundary control follows this module
on those routes.

The credential decision

A Registry sync connection uses a credential the external platform issues. On every supported
platform it also carries delete permissions on agent resources.

Record before the connection is created:

• Issuing owner and the approved least-privilege scope.
• The retirement coordinator's acceptance of the delete permissions.
• The managed secret store that holds it, never this repository.
• The rotation and revocation owner, and the concrete revoke action.

Implementation tradeoffs

What preflight checks

It reads onboarding-decision.json and rejects:

• unresolved decisions and an unrecognized route;
• a source reference that is not absolute HTTP or HTTPS, or that carries embedded credentials;
• an incomplete credential decision, or a store inside this repository;
• a retirement plan missing a required action.

It does not contact Agent 365 or the external platform. Licensing, admin access, and a working
connection are still confirmed live.

Confirm the result

The intended live record is in Agent Registry, arrived through the selected route, and its owners
can maintain and retire it.

Stop for a missing, duplicate, stale, or wrongly owned record. Resolve it in the source platform,
then read the registry again.

Operating state

Delete a Registry sync connection only after checking every agent it can affect.