Microsoft opens Copilot Managed Runtime preview inside Microsoft 365

Microsoft's September 25 Copilot announcement bundled three capabilities: Copilot Home, which lets people create deliverables by chatting with AI to operate Word, Excel and similar tools; Copilot Code, an AI coding agent; and Copilot Autopilot, an AI agent that keeps working around the clock on instructions. Together they made it easier for employees without programming knowledge to build useful work applications in natural language. The obvious follow-on problem is running those applications safely and with governance — which is what Copilot Managed Runtime is for.

The runtime's defining choice is that applications execute inside the same tenant boundary as the user's Microsoft 365, rather than somewhere outside it. Because permissions trace back to Microsoft 365 user IDs and operations run through the Microsoft 365 admin console, publishing, visibility and status checks stay within the corporate perimeter and follow existing internal rights. The article notes that, judging from the documentation, the executed code appears to be intended as JavaScript/TypeScript, although this is described as unconfirmed.

Read together, Microsoft appears to be positioning Copilot as something more than an assistant for tasks and app development — a central service in Microsoft 365 for evolving the whole of work through AI, now that it includes an application runtime with Microsoft 365 governance. Whether that holds depends on how much of the intended app estate actually fits the runtime's expected code and connectors, and on administrators accepting the admin console as the control point.