A working pilot still needs a workload identity, a data boundary and an operating owner before release. We build the agreed production workload in the customer environment, validate it against acceptance criteria, and hand it over with its monitoring and recovery plan.
Accepted Agent 365 inventory, Foundry readiness findings and Foundry IQ knowledge assets are reused. The quote identifies the additional engineering required to reach production.
Scope and boundaries
Six weeks for one workload with up to three coordinated agents and three data or tool connections, including the agreed model, tool and knowledge integrations, evaluation and production release.
An accepted Foundry IQ knowledge base and readiness assessment are reused. The quote identifies only remaining grounding and production-integration work; ongoing managed operations are separate.
The Challenges You Face
The Pilot Ran As A Person
A pilot built under an individual account inherits everything that account can reach. Moving to production means deciding what the workload itself should be allowed to touch, which is usually a much shorter list.
Nobody Owns It On Monday
A pilot has a builder. A production service needs an owner and an escalation path. Microsoft Entra Agent ID supports agent identities and accountable sponsors. Confirm availability and licensing for the specific capabilities in your rollout.
Agents Already In The Tenant
Employees can create agents through Microsoft Copilot Studio, Microsoft Security Copilot, and Microsoft Foundry. Most organizations have more of them than they think, and no list.
Licensing Moved Under The Rollout
Since 1 July 2026, agent-level discovery and security posture for Microsoft Foundry agents requires a Microsoft Agent 365 license rather than the Defender CSPM plan. Rollouts scoped before that date are frequently costed against the old position.
How the Engagement Runs
-
Scope one workflow
Agree the single workflow, the named business owner, the named technical owner, and what working will mean when it is finished. Written down before anything is built.
-
Establish the boundary
Identity for the workload, permissions it will hold, data it may reach, and what has to be labeled, restricted, or excluded. Reviewed with whoever owns the data rather than assumed.
-
Build to the boundary
Implement inside the tenant against the identity and permission model agreed above, with the approval point in place from the first run rather than added later.
-
Prove it and hand it over
Test against the agreed definition, produce the monitoring and escalation path, and write the handover for whoever inherits it rather than for whoever built it.
Ideal For
A working pilot that has to become a supported service before anyone else can use it
A workflow inside Microsoft 365 that touches content with a handling obligation
An agent built in Microsoft Copilot Studio or Microsoft Foundry that now needs an owner, a boundary, and a support path
An organization with agents already in the tenant and no inventory of them
A security or risk function asked to approve an AI rollout with no basis on which to do it
Full-Spectrum Services
From initial assessment through deployment and ongoing management, our team handles every phase.
Book an AI Implementation SessionWhat You Receive
Key Benefits
One workflow finished and handed over, rather than a strategy document
Identity, permissions, and data boundary settled before launch instead of after an incident
Controls built on Microsoft's own platform, so they are auditable with tools already licensed
A named owner on the customer side who can run the thing without us
A written record a reviewer who was not present can follow
Governed delivery
We define where people approve consequential actions and validate those controls before rollout. A named customer approver reviews the exact production change, test evidence and recovery plan. Where an enforced control is unavailable, the action remains outside unattended execution. An information request or model-triggered review does not by itself prove an enforced approval boundary.
Related resource
AI Workflow Readiness Scorecard
Score one workflow across seven dimensions before you commit budget to automating it.
Preview the AI Workflow Readiness ScorecardStart With One Workflow, Not A Strategy
Book a working session to pick a candidate workflow, name its owners, and establish what would have to be true for it to run in production.