Blog
Put the agent inside the Workflo
Copilot and agents create value when they sit inside a named workflow with sources, approvals, and a human owner.
McKinsey's November 2025 State of AI survey found that 62 percent of respondents said their organizations were at least experimenting with AI agents. Only 23 percent were scaling an agentic system anywhere, and no more than 10 percent were scaling agents inside any single business function. Access is widespread. Placement is not.
The useful pattern is specific. The agent sits inside a named Workflo, with sources, approvals, and a human owner. A side chat can draft. Closing a renewal, reallocating field equipment, or approving an exception takes a workflow with a person still on the decision.
Where the platform is pointing
September 2026's Copilot Studio updates point the same way. Makers can build the interface, the deterministic workflow, and the agent together. Foundry IQ knowledge bases are generally available, so an agent can answer from enterprise knowledge and show citations. Use the agent where the step needs judgment. Use a workflow where the step must happen the same way every time.
SHIFT to SCALE builds that loop inside the Microsoft environment you already run.
- Ground answers in tenant content your compliance team already approved
- Keep a person on the decision the output supports
- Log the path so the outcome can be audited
- Measure cycle time and exception rate, alongside prompt volume
Start with one Workflo. Prove the measure moved. Then decide what to scale.