Cowork, Code, and Copilot Studio on one managed runtime | Copilot Studio Updates | October 2026
Read the Portuguese translation →
Author: Microsoft Power Platform · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: Cowork, Code, and Copilot Studio on one managed runtime | Copilot Studio Updates | October 2026 · Channel: Microsoft Power Platform · 03:13 · Watch on YouTube
Topics: AI agents, Task and workflow automation, Software engineering with AI, AI governance and regulation
Summary
Section titled “Summary”Copilot is expanding from a productivity assistant into a creation partner that can help change how companies work. Cowork, Code, Copilot Studio, and other coding experiences can work on the same project and deploy it to a shared managed runtime. This lets more people contribute, while Microsoft provides uptime, compliance, reliability, security, sharing, and administrative controls. The result is a common platform with governance and visibility built in.
Key points
Section titled “Key points”- Cowork can build applications that connect to data and can be shared with users.
- Code in Copilot provides a dedicated creation workspace running on the same engine as Cowork.
- Projects can move from Cowork to Code and then to Copilot Studio.
- Copilot Studio can extend projects with AI workflows and agents.
- The shared runtime is an open standard that coding agents across experiences can interact with.
- Projects can also be accessed through the GitHub app or a developer CLI.
- The managed runtime includes Microsoft’s responsibility for uptime, compliance, and reliability.
- Applications are designed to be secure and shareable, with governance and controls available through the Microsoft Admin Center.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:00 | Copilot as a creation partner | The speaker describes how new experiences and a managed runtime expand Copilot’s role from helping individuals work to helping transform how companies work. |
| 00:31 | A shared workspace for building | Cowork can create applications, and users can continue developing those projects in Code on the same engine. |
| 01:34 | Extending projects across experiences | The same project can be further developed in Copilot Studio, the GitHub app, or the CLI, enabling more people to participate. |
| 02:38 | Built-in governance and control | The speaker explains that managed applications are secure, shareable, and subject to visibility, policies, and controls, all on the common runtime. |
Quotes
Section titled “Quotes”Copilot has expanded from being something that helps me be more productive in my day job to something that actually helps me change the way my company works. — 00:00
Both Cowork and Code deploy to that same new managed runtime that just comes with Copilot. — 01:03
their AI personal assistant is no longer just an assistant, but is a creation partner — 02:07
that visibility, security, governance is built in from day one. — 03:13
Concepts and entities
Section titled “Concepts and entities”Cowork, Code, Copilot Studio, Copilot, managed runtime, GitHub App, CLI, Microsoft Admin Center, Agent 365, Microsoft
Full transcript (original language)
Section titled “Full transcript (original language)”00:00 It is super exciting how we are dramatically expanding what Copilot can do. Not just with new experiences, but now an entire engine under the hood, a managed runtime, that together mean Copilot has expanded from being something that helps me be more productive in my day job to something that actually helps me change the way my company works. And I want to stitch these new pieces together because all of them individually are important, but the way they work together is what is really transformational.
00:31 Now, a couple of weeks ago, we introduced the idea that Cowork, as I’m working in the flow of work, can help me do more than just create a PowerPoint or a document. Now it can build a whole application that runs and connects to data and is shared with my users. But that’s just the starting point. You know, now with Code in Copilot, I have a dedicated creation workspace that runs on exactly the same engine. So I can start something simple in the flow of work, but then come back to it later or bring in another user from my company
01:03 to help me take it further directly in Code. And guess what? Both Cowork and Code deploy to that same new managed runtime that just comes with Copilot. And it’s not the only thing that deploys to it. It’s now an open standard that any coding agent in any experience can interact with. So I can take that project I started in Cowork, and then took further in Code, I can go to Copilot Studio, open up exactly the same project, party on it, add AI workflows,
01:34 add agents, make the scenario more robust. I can then go to the GitHub app or open it up even as a developer in the CLI, address exactly the same thing, all running on the same engine, all part of the same family. And that dramatically expands not just what I can do with Copilot, but who can participate as well. And this really is the basis of how we see Copilot becoming so existential to transforming the way companies work. All of the expertise in our companies exists in the business,
02:07 in the people that are doing these processes every day. Making sure that their AI personal assistant is no longer just an assistant, but is a creation partner over a much more robust toolkit that any developer can infinitely extend is a big unlock for productivity. And guess what? All of it is managed. Managed in the sense that we know it’s just going to work, that Microsoft takes on the responsibility for the uptime, the compliance, the reliability. That we also know it’s going to be secure
02:38 and it’s going to be shareable like a document, no matter how I engage with it or how I start working with it and manageable in the sense that I’ll have the governance and visibility and control. I’ll be able to go to the Microsoft Admin Center and just like monitoring agents in Agent 365, now I can see all of my managed applications here, you know, and be able to set policies and rules and limits over who can do what. So it’s a complete story that’s come together. Everybody can now participate as a maker. All of the surfaces, no matter where you start, deploy to the same stack,
03:13 the same managed runtime, and that visibility, security, governance is built in from day one. We cannot wait to see what you do with this stack next.