The agent action gate
The fictional bank records the exact action and approver.
Coming
See every demonstrationCROSS-VENDOR AGENT CONSOLIDATION
One decision per agent: keep, migrate, merge, rebuild or retire.
Business units have bought or built overlapping agents, copilots, automations and knowledge assistants across Microsoft and other platforms, and nobody holds the portfolio view or the retirement process. In four weeks we inventory every agent with its owner, contract, users, integrations and data access, analyze the overlap and the risk, and hand over a disposition per agent with a target governance architecture and a wave plan.
01 Source02 Boundary03 Human decision04 Evidence
HOW IT WORKS
The control path in practice.
- Inventory the platforms, agents, owners, contracts, users, integrations, data access and dependencies, read-only.
- Analyze capability overlap, risk, cost, identity, data and lifecycle across the portfolio.
- Write the target architecture, the disposition decisions, the migration patterns and the dependency sequencing.
- Deliver the business case, the transition roadmap and the executive decisions, with the implementation handoff.
THE PROBLEM
Why does the agent count keep rising while nothing gets retired?
Because every unit bought or built what it needed, nobody owns the portfolio, and retirement is an unassigned task. The assessment produces the missing object: one register with an owner, a purpose, usage, cost, data access and risk per agent, and a decision on each.
The headline deliverable is a keep, migrate, merge, rebuild or retire decision per agent, with a governance model centered on Microsoft Agent 365 where that is technically appropriate, and no forced Microsoft destination where a workload has a documented reason to stay elsewhere.
THE MICROSOFT INSIGHT
Where do the kept agents get governed?
In Microsoft Agent 365, the control plane that observes, governs and secures agents built on Microsoft platforms or acquired from third parties, through the Microsoft 365 admin center, Microsoft Entra, Microsoft Purview and Microsoft Defender you already run.
Microsoft Agent 365 is the control plane that observes, governs and secures agents built on Microsoft platforms or acquired from third parties, through the Microsoft 365 admin center, Microsoft Entra, Microsoft Purview and Microsoft Defender. (Microsoft Learn, checked Oct 31, 2026)
Bring the kept agents under the control plane in the wave plan and the portfolio has one inventory. Leave them where they are and the next consolidation starts from the same blank page.
THE METHOD
What happens in the four weeks?
Inventory, analysis, target state and business case, each a deliverable you hold.
- Week 1: inventory platforms, agents, owners, contracts, users, integrations, data access and dependencies.
- Week 2: capability overlap, risk, cost, identity, data and lifecycle analysis.
- Week 3: target architecture, disposition decisions, migration patterns, dependency sequencing.
- Week 4: business case, transition roadmap, executive decisions, implementation handoff, with a one-hour executive readout.
THE JOIN
How do agents built elsewhere join the control plane?
Agents built with Microsoft Foundry, Copilot Studio and Agent Builder are integrated with Microsoft Agent 365 automatically; agents built elsewhere join through registry sync or the Agent 365 SDK, which the disposition for each kept agent names as its migration pattern.
Agents built with Microsoft Foundry, Copilot Studio and Agent Builder are integrated with Microsoft Agent 365 automatically; agents built elsewhere join through registry sync or the Agent 365 SDK. (Microsoft Learn, checked Oct 31, 2026)
Name the join path per agent and the wave plan is a schedule. Leave it vague and the wave plan is a wish.
WHAT IT IS NOT
Does the assessment migrate or shut anything down?
No. Agent migration, contract termination, production shutdown and source-code remediation are excluded; the cost projections state their inputs and assumptions and are not a financial audit; and no agent is forced to a Microsoft destination where a documented reason says otherwise.
Access is read-only to platform inventories, procurement records, usage reports, integration catalogs and identity metadata, limited to thirty days, with named owners for AI governance, enterprise architecture, procurement, security and the highest-use business-unit agents. The target state uses Agent 365 where supported, Entra, Purview, and Microsoft Foundry or the Microsoft Agent Framework on Azure, with external systems shown through approved integration boundaries.
AFTER TWO WEEKS
What will be working after two weeks?
- You hold the cross-vendor agent portfolio register: owner, purpose, usage, cost, data access and risk per agent.
- You hold the disposition matrix: keep, migrate, merge, rebuild or retire, one decision per agent.
- You hold the capability-overlap and contract-renewal map, and the target governance and integration architecture showing Agent 365, Entra, Purview and the approved runtime boundaries.
- You hold the wave plan and the executive business case with its assumptions stated.
The work is delivered remotely inside your own Microsoft tenant, wherever your business is, and on site only when the work needs it.
HONEST ABOUT LIMITS
What this does not do yet
It does not detect an attack on a kept agent with a generally available control today. Microsoft Defender threat detection for Agent 365 managed agents, in public preview, raises near real time alerts for jailbreak attempts, indirect prompt injection, credential leakage and suspicious access. (Microsoft Learn, checked Nov 4, 2026, preview) Microsoft Defender threat detection for Agent 365 managed agents is in public preview and covers published Foundry agents; the target architecture labels it as such and relies on identity, the approval seam and the real-time tool-call gate that are available now.
It does not migrate, terminate or shut anything down; each disposition is executed under its own scope.
It does not audit the finances; the projections state inputs and assumptions.
THE ONE THING TO REMEMBER
One register, one owner and one decision per agent, before the next renewal.
Said another way: inventory, overlap, disposition, wave.
Said a third way: consolidation is a decision per agent, not a migration to a vendor.
SHOW YOUR WORK
See the control path on a fictional bank.
DIRECT ANSWERS
Questions before you decide.
Which platforms are in scope?
Whichever ones your agents run on, Microsoft and otherwise; you confirm the vendors and environments in scope at the start. The register treats every agent the same way regardless of where it runs.
Does every agent end up on Microsoft?
No. The target state uses Agent 365 where it is supported and appropriate. An agent with a documented reason to stay elsewhere keeps its disposition and is shown through an approved integration boundary.
What access do you need?
Read-only access to platform inventories, procurement records, usage reports, integration catalogs and identity metadata, limited to thirty days, plus named owners for governance, architecture, procurement, security and the busiest business-unit agents.
How do we start?
A scoping session confirms fit, access, schedule and private-offer pricing. Microsoft licenses and consumption are separate. No price appears on this site.
NEXT STEP
Start with a boundary you can explain.
Choose a focused check, or speak with the team about the workflow you need to improve.