Copilot Managed Runtime brings governance to AI-built apps
Diesen Beitrag auf Deutsch lesen
Copilot Managed Runtime applies tenant controls, Entra authentication, DLP, connector policies and inventory visibility to Microsoft 365 business apps.
TL;DR
Copilot Managed Runtime is a Microsoft-managed environment for Microsoft 365 line-of-business apps created through Cowork, Copilot Studio, or an SDK and CLI. Apps inherit tenant governance from creation, use Microsoft Entra authentication, appear in the Microsoft 365 admin center, and can be governed with Conditional Access, DLP, connector, sharing, and lifecycle controls.
Original by Ramón Rautenstrauch, on Consultor 365. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Build through the managed runtime so AI-created apps start with organisational identity and policy controls.
- Admins/CoE: Review the Microsoft 365 admin center inventory, usage, health and lifecycle of apps regardless of their creation path.
- Security/Compliance: Configure connector, sharing, Conditional Access and DLP policies carefully; secure defaults do not correct weak configurations.
Frequently asked questions
What do apps built with Copilot Managed Runtime inherit automatically?
They inherit Microsoft Entra authentication and run on Microsoft-hosted execution. Tenant policies apply to them and they appear in the inventory of the Microsoft 365 admin center.
Which controls does the managed runtime support for administrators?
Conditional Access, data loss prevention, connector restrictions, sharing boundaries and lifecycle management. These controls come from the platform, so administrators gain visibility into AI-built apps instead of only trying to prevent them.
Does the managed runtime remove the need for governance design?
No. The article says that governance built in by design does not mean security can be forgotten, and that a poorly configured policy remains a poorly configured policy.