Microsoft Copilot & GitHub Copilot Use the right Copilot for the task, with a source, an output format and a review step. Reviewed 15 November 2026 · Utilising AI Pty Ltd https://www.utilisingai.com/learn/microsoft-copilot Microsoft 365 Copilot supports work such as documents and meetings where enabled. GitHub Copilot is a coding product. Access, licenses, supported features and administrator settings differ; this guide does not activate either service. Independent educational guide. Original examples; documentation-based guidance. Product availability varies. No provider integration or AI request is run by this download. Quick start =========== 1. For office work, open the document or source you want to use in the supported Microsoft app. 2. For coding, open the relevant repository and files in your supported Copilot environment. 3. Ask for one result, review it against the original material, then request a targeted revision. Practical tips ============== Use goal, context, source and expectations Tell Microsoft Copilot what to produce, why it matters, which material to use and how the output should look. A useful business request might name a proposal file, its audience and a word limit instead of asking for a generic summary. https://support.microsoft.com/en-us/microsoft-365-copilot/write-a-great-prompt-in-microsoft-365-copilot Make one precise Word edit Ask Copilot in Word to shorten an introduction, change its tone or reuse a document structure. Identify the source file when work context is needed. Review names, numbers and meaning before sharing the edited document. https://support.microsoft.com/en-us/word/copilot/write-effective-prompts Refine the result in place Once the result is close, ask for a specific improvement such as a shorter opening or a clearer action list. Keep the source and desired outcome in view. Our practical habit is to recheck any facts affected by the revision, rather than rereading only the polished wording. https://support.microsoft.com/en-us/word/copilot/write-effective-prompts Developer notes =============== Give GitHub Copilot relevant code context Name the function or file, describe the goal and provide example input and output. Split a large coding task into smaller changes. For completions in an editor, keep the relevant files open so the available context fits the work. https://docs.github.com/en/copilot/concepts/prompting-and-context/prompt-engineering Store repository conventions once For supported GitHub Copilot surfaces, .github/copilot-instructions.md supplies repository-wide guidance. Path-specific instructions use files below .github/instructions/. Check the support matrix for your editor and feature; instruction support is not identical everywhere. https://docs.github.com/en/copilot/concepts/prompting-and-context/custom-instructions Review generated code as a change proposal Ask for a relevant test and inspect the suggested implementation. Check error handling, unwanted data exposure and existing project conventions. Our review pattern is to require observed test results and a human-readable diff before a production merge. https://docs.github.com/en/copilot/concepts/prompting-and-context/prompt-engineering Original examples to adapt ========================== Proposal → decision brief Using [select or attach proposal file], write a decision brief for the business owner: goal, deliverables, price stated in the source, open questions and next step. Maximum 250 words. Mark missing details as “not provided”. Keep recommendations separate from facts. Use in a supported Microsoft 365 Copilot experience with access to the chosen file. https://support.microsoft.com/en-us/microsoft-365-copilot/write-a-great-prompt-in-microsoft-365-copilot Refine a Word draft Shorten the selected introduction to 100 words for a non-technical reader. Preserve the offer, dates and prices. Flag any sentence whose meaning is unclear instead of inventing a replacement fact. Original example for an existing draft; review the edited text. https://support.microsoft.com/en-us/word/copilot/write-effective-prompts GitHub Copilot project instructions starter # Repository guidance - Runtime and framework: [actual versions]. - Relevant test command: [actual command]. - Follow the existing error-handling pattern in [file]. - Preserve these public interfaces: [list]. - Report tests run and any remaining verification gaps. Save an adapted version as .github/copilot-instructions.md where supported. This is guidance, not an enforced access policy. https://docs.github.com/en/copilot/concepts/prompting-and-context/custom-instructions Check the result ================ - Did the tool actually have access to the selected source? - Were office facts checked, and were coding changes tested? - Have you confirmed the feature exists in your account or editor? Common mistakes =============== - Confusing Microsoft 365 Copilot with GitHub Copilot. - Assuming naming a file grants the tool access to it. - Accepting generated code or document claims without review. Sources ======= Microsoft · Write a great Copilot prompt · Official help https://support.microsoft.com/en-us/microsoft-365-copilot/write-a-great-prompt-in-microsoft-365-copilot Microsoft · Effective prompts in Word · Official help https://support.microsoft.com/en-us/word/copilot/write-effective-prompts GitHub · Copilot prompt engineering · Official developer documentation https://docs.github.com/en/copilot/concepts/prompting-and-context/prompt-engineering GitHub · Copilot custom instructions · Official developer documentation https://docs.github.com/en/copilot/concepts/prompting-and-context/custom-instructions