Start with the information your task needs. Use Copilot Chat for a question, draft, or analysis based on public information or material you provide. Choose the licensed work-context experience of Microsoft 365 Copilot when the work depends on your permitted Microsoft 365 files, email, meetings, or chats across supported experiences.
Consider Autopilot when a process needs continued attention, such as watching project updates and preparing follow-ups over several days. Start with a clear process and an accountable owner. Use Copilot Cowork when you mainly need to assign and review a defined task.
Use Copilot Code when you need custom software and can describe its expected behavior. Start with a small task and test the result. Reuse an existing service when it already meets the need.
Start with the work
Choose the work pattern first, then check how the experience is funded. An included chat capability, a per-user license, Copilot Credits, and Azure consumption answer different cost questions. The same product can have more than one charging path depending on the user and scenario.
Use Copilot Cowork when you can describe a result, its boundaries, and how you will review it. Cowork carries out multistep work across apps, files, and connected services. Start with a defined task, such as preparing a project briefing from permitted files, and inspect the result before using it.
Use GitHub Copilot when the job is to write and maintain software with AI assistance. Use Microsoft Foundry when the job is to build and operate an AI-powered application, agent, or model. A development team can use both in the same project.
Treat a shared Copilot app as a maintained team service. Agree access, ownership, support, and budget before colleagues depend on it. Check that the tested app still works after publication.