Chapter 6 of 6
Confirm the result#
The module is complete when the Agent 365 administrator and the agent owner see the intended live record in Agent Registry, the runtime owner names its update path, and the retirement coordinator names the approved removal decision. For Registry sync, the connection also shows the selected provider and a current sync result.
Stop the module if the record is missing, the live state does not match the selected route, or any owner cannot explain the retirement path.
After implementation#
The Agent 365 administrator keeps inventory visibility. The agent owner makes lifecycle decisions. The retirement coordinator approves the change that removes the agent from use, and keeps the cross-platform plan in onboarding-decision.json current when owners change.
Restore or remove the inventory state through the same route:
| Route | Removal action | Check first |
|---|---|---|
built-in | The platform operator uses that platform's retirement, unpublish, or removal path. | The platform's own lifecycle effect. Agent Registry reflects the result. |
registry-sync | Retire the agent on the connected platform, run or await the sync, then revoke the connection credential through the recorded revocation path. Delete a connection only in the Microsoft 365 admin center. | A connection change can affect every agent synchronized through it. The retirement coordinator and Agent 365 administrator review that blast radius before deleting anything. |
sdk | The runtime owner removes the SDK integration and releases it through the product's approved path. | The live result in Agent Registry, and whether the runtime service itself should also be retired. |
After any of these, review the live record again. If the agent should no longer appear, confirm that through the route you used.