TL;DR: Microsoft's September 2026 Copilot Studio update lets makers build apps, workflows and agents in one studio. Apps and Copilot Managed Runtime are in public preview, while Foundry IQ grounding and the Review panel are generally available. This changes how solutions get built and how they get billed, because building and running these solutions draws on Copilot Credits. With usage-based billing turning on by default for new Microsoft 365 Copilot Business licenses purchased through partners on December 1, 2026, the time to set guardrails and value measures is now.
For years, solving one business process in the Microsoft stack meant juggling separate tools. A form lived in Power Apps, the approvals ran in Power Automate, and the conversational help came from a separate bot. Each piece had its own maker, its own permissions and its own budget line.
That separation is ending. Copilot Studio now brings the interface people use, the deterministic workflow the business relies on, and the agent that reasons through exceptions into one place. Microsoft frames it as one studio for building the business.
The timing matters. New Microsoft 365 Copilot Business licenses bought directly from Microsoft default to usage-based billing starting October 19, and new licenses purchased through Cloud Solution Provider partners follow on December 1, 2026, with a default limit of 4,000 Copilot Credits per user per month. The same credits fund much of what makers will now build in Copilot Studio. Organizations that decide who builds, what gets measured and what it may cost before that date will scale with confidence. Organizations that wait will be reading the bill to find out what got built.
The September 2026 update, published October 7, adds a new building block and several controls that make agents more predictable in production.
The headline is apps, but the controls deserve equal attention. Hooks, evaluations and the Review panel are what turn a promising prototype into something an IT leader can sign off on. If you are still choosing which harness your agents should run on, our Copilot Studio harness decision guide explains the trade-offs, since apps and hooks both rely on the GitHub Copilot harness.
Because the question your makers ask changes. It used to be which tool should I use? Now it is which building block fits each step of this process?
Microsoft's own example is employee onboarding. An app gives managers and new hires a structured interface. A workflow runs the steps that must happen the same way every time. An agent answers questions, handles exceptions and adapts when circumstances change. One process, three building blocks, one place to build and govern them.
That shift brings three practical consequences for IT leaders.
None of this requires a large program. It requires a handful of clear decisions, made before the defaults make them for you.
Consumption billing is not a reason to slow down. It is a reason to measure. When every run has a cost, every run can also have a value, and that makes the business case easier to prove than a seat license ever was.
Start with a simple equation for each process: value per case equals minutes saved, multiplied by the loaded cost of that time, minus the credits the case consumed. For example, if an intake process saves 20 minutes per request at a loaded cost of $60 an hour, each case returns $20 of time. If the case consumes 150 credits at an assumed rate of one cent per credit, it costs $1.50. Confirm your actual credit rate, then track the numbers that matter.
Two habits make these numbers credible. Capture a baseline before launch, because you cannot prove improvement without one. And review cost and value together each month, so a growing credits line is always read next to the hours it returned. For a fuller measurement framework, see Copilot adoption metrics that prove value.
Watch the governance side of the ledger too. Our analysis of why agent estates are growing faster than controls shows what happens when building scales and oversight does not. The same inventory that keeps you safe is the inventory that proves your return.
No. Power Apps remains available and fully supported. Apps in Copilot Studio give makers a new, conversation-first way to build an app as part of a broader solution that includes workflows and agents. Choose based on the process, the makers involved and your licensing.
Building uses Copilot Credits. According to Microsoft's licensing guide, running an app built in Copilot Studio follows Copilot Credits usage-based billing by default, and it is included for users who hold Power Apps Premium licenses, subject to existing request limits. Check the current licensing guide before you budget, because preview terms can change.
Some are. Foundry IQ integration and the Review panel are generally available. Apps, Copilot Managed Runtime and hooks are in preview, so treat them as pilot material with a clear exit plan rather than the foundation for critical processes today.
A workflow defines the logic to execute. A hook decides when that logic runs during an agent's session, such as at session start, around a tool call or after an error. Use both when a step must happen every time inside an otherwise flexible agent.
2toLead helps organizations turn Copilot Studio capability into governed, measurable outcomes. Our Microsoft MVP team can help you:
Explore more practical guidance in the 2toLead Insights hub, or talk to our team about your Copilot Studio governance plan.
No hype. Just practical, governed AI that actually gets adopted.
Join Our Newsletter
