The New Copilot Super App: Code, Autopilot & What IT Must Prepare

Microsoft’s September 25 announcement presents Copilot as a workspace for creating and delegating work. Home gathers everyday work; Code turns a described outcome into software; Autopilot is presented as a persistent personal agent. The announcement placed Home and Code in Frontier rollout and Autopilot in an expanding private preview. This companion explains published plans and documentation. No tenant tests were performed.

Start with a useful workflow

Choose one recurring task with a named business owner: for example, a supplier report that could become an internal tracker. Write down its users, source data, acceptable actions and success criteria before deciding which product creates it. A preview announcement does not establish availability in your tenant.

Code supports local and cloud development; GitHub integration is optional. Work-account access needs the applicable Microsoft 365 Copilot entitlement, Code enabled, and the documented preview/client requirements. Check the requirements page before rollout.

Treat the app as an operated service

Managed Runtime is Microsoft’s hosting platform for code-created apps. Managed hosting reduces infrastructure work; it does not remove app ownership, data permissions, support, access review or retirement decisions. Track the app and its owner in the admin inventory. Record creation paths separately: Copilot Studio, Cowork and CLI do not share identical defaults or preview gates.

Autopilot also needs an operating owner. Define the objective, permitted actions, approval boundaries, reviewer and stop procedure. Do not extrapolate a private-preview film into a tested list of supported unattended actions.

Separate building from running

Code’s credit consumption depends on the models, context, tool calls and runtime work involved. There is no universal per-app build price in the sources reviewed. Record iteration and creation costs separately from the app’s later use.

The Managed Runtime licensing FAQ documents 0.1 Copilot Credits per API call under credit-based runtime use. An illustrative 10,000 calls therefore equals 1,000 credits for that meter alone. It is not a dollar quote or a complete workload forecast. Power Apps Premium can cover runtime within applicable request limits; other AI services can have separate charges. Included Microsoft 365 Power Apps rights are insufficient for this runtime entitlement. Sharing an app does not grant a license or its underlying data permissions. Running the app does not itself require a Copilot subscription.

For Autopilot, do not invent a separate rate card: the episode did not verify a standalone public per-task price. Recheck the relevant service’s commercial terms before budgeting.

Give IT and finance a joint checklist

Use the attached worksheet to record access groups, Code execution modes, automatic approval choices, repositories and organizational context. Assign app owners and support contacts. Decide which services and groups can consume credits and how limits, alerts and credit requests will be handled. Review the automatic inclusion of new services rather than assuming a policy will remain unchanged as capabilities expand.

This is a planning aid based on Microsoft documentation checked during 19–21 October 2026, not a tested deployment guide. Reconfirm availability, rates and rights before implementation.

Primary sources

• announcement (opens in a new tab)
• runtime-blog (opens in a new tab)
• code-admin (opens in a new tab)
• code-overview (opens in a new tab)
• licensing (opens in a new tab)
• governance (opens in a new tab)
• runtime-admin (opens in a new tab)
• runtime-faq (opens in a new tab)
• credits (opens in a new tab)
• usl-ubb (opens in a new tab)
• code-requirements (opens in a new tab)
• code-start (opens in a new tab)
• credits-guide (opens in a new tab)