Copilot Home and Code: choose a document or a small application
Check rollout, tenant permissions and billing first. A document task and a hosted application have different outputs and responsibilities.
In brief
Microsoft’s September announcement separates Home for chat/delegated work from Code for building solutions. Decide whether your actual need is an editable file or a small application before choosing the workflow.
This avoids building an app for a job a maintained spreadsheet can handle, or expecting an app’s hosting and permissions from a document draft.
Choose the smallest useful deliverable
For a one-off budget, an editable workbook with checked formulas may be enough. For a shared tracker, define inputs, owner and who can read or change records. The purpose should determine the format, not the novelty of a mode name.
Check the rollout and cost route
Read the current product notice and administrator controls. Microsoft distinguishes subscription use from usage-billed agentic work in this announcement. Do not assume every Code or long-running task is covered by the ordinary chat allowance.
Verify before team sharing
For a file, inspect formulas, sources and editable structure. For an app, test inputs, accessibility and data permissions in the actual tenant. A sandbox or polished preview is not proof that the final product is correct or appropriately shared.
Before you act
The announcement includes staged Frontier and preview availability, not immediate access for every account. Current tenant, license and usage-billing conditions must be checked.
What to do next
- Define whether the deliverable is a document, workbook or application.
- Check the relevant capability’s current availability and tenant policy.
- Review the artifact, permissions and actual usage before sharing it.
